WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3 --- Revised and resent

To: "Ke, Liping" <liping.ke@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3 --- Revised and resent
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 23 May 2008 11:48:18 +0100
Delivery-date: Fri, 23 May 2008 03:48:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <391BF3CDD2DC0848B40ACB72FA97AD5903667B4B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aci6Rwan30LCwMVNRjCgsXSrb2rzYwAOb9TQAAFWQHAAAIxGwAAAHx6dAACz6YAAAGA27AAfNwegAG4iWxM=
Thread-topic: [Xen-devel] [PATCH 0/4] HVM Virtual S3 --- Revised and resent
User-agent: Microsoft-Entourage/11.4.0.080122
I think all these issues are fixed as of c/s 17713. However, when I s3resume
a Linux guest I find it is unresponsive and the VGA display is corrupted by
re-printing of BIOS start-of-day messages. Perhaps the BIOS is taking an
incorrect path on S3 resume? It would be good if you can look into this now
-- I think the hypervisor issues at least are now resolved and this is
probably something in the higher-level rombios or ioemu logic.

 -- Keir

On 21/5/08 07:31, "Ke, Liping" <liping.ke@xxxxxxxxx> wrote:

> Hi, Keir
> We have some test today, found several small points:
> 1. after cpu_reset, seems we need to call vcpu_initialise to reconstruct vmcs,
> otherwise, the domain could not be resumed back and xen has low response then.
> 2. yes, we may need to find a way to clear that io_port_write, otherwise, save
> will hang. I add back the clear (defer_shutdown =0) to have a test, then it
> works just fine.
> 3. in python, seems it will report
>     a. global name "TRIGGER_S3RESUME" is not defined
>     b. global name "HVM_PARAM_ACPI_S_STATE" is not defined
> 
> After solve those problems, I found it could work fine, even with PV drivers
> installed. I found vif is ok after resume back.
> Will you help us to solve them or need do it by us?
> 
> Thanks a lot for your help!
> Criping
> 
> 
> Keir Fraser wrote:
>> On 20/5/08 16:19, "Ke, Liping" <liping.ke@xxxxxxxxx> wrote:
>> 
>>> OK. Another thing is that
>>> when debugging, we found when s3_sleep, it will generate the
>>> acpi_ioport write operation, it is not cleared so v->defer_shutdown
>>> is set when s3_suspend. Then it will prevent save process to do
>>> domain_shutdown, save process will hang. So we clear defer_shutdown
>>> flag for each vcpu when do s3_suspend.
>>> 
>>> After refactory since we did not clear the flag, I am not sure
>>> whether this problem will exist. I will have a try tomorrow.
>> 
>> Oh yes, I forgot I removed that. It looked a bit aggressive, so if the
>> problem remains then perhaps we can find a nicer way round the
>> problem. 
>> 
>>  -- Keir
> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>