Re: [PATCH 0/4] HVM Virtual S3

[Keir Fraser <keir.fraser@eu.citrix.com>]

'xm [un]pause' already has a meaning, and I don't think the meaning should
be overloaded for HVM guests. That's asking for trouble. I'd rather we went
with the 'xm trigger' approach, making it look like a lid opening and
closing.

Apart from that, this approach of doing most of the work on the suspend side
is definitely the right thing to do. Then 'xm trigger lid-open' (or whatever
you call it) will be really not much more complicated than domain_unpause().

 -- Keir

On 9/5/08 10:58, "Ke, Liping" <liping.ke@intel.com> wrote:

>> That is good idea. Basically we will combine suspend/resume into one
>> logic. And use "xm unpause" for resume. We will look into more.
>> 
> Hi, Ke and Ian
> Today I am trying this idea, I found combining S3
> sus/resume+domain_pause, and then
> use domain_unpause letting domain back works fine.
> 
> Yet when I am trying xm save after pausing domain, I found if a domain
> not running, 
> Xm save will reject the save request.
> So I want to know whether domain running is a must  for xm save
> operation?