|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchroniz
On 06/07/2010 11:27, "Joanna Rutkowska" <joanna@xxxxxxxxxxxxxxxxxxxxxx>
wrote:
>> Wouldn't it be much simpler to not introduce any new logic at all and
>> just let Dom0 tools/scripts take care of properly suspending
>> (checkpointing) all (minimally all pv, but I would really think treating
>> different kinds of guests differently here is unnecessary) guests
>> before doing a host suspend, as Jeremy had suggested in an earlier
>> reply?
>>
>
> But wouldn't this require dumping all the VMs memory do disk? Can we use
> xm pause instead, i.e. will it notify VMs properly?
It just requires the guests to be put through a guest-side suspend/resume
cycle. The usual tools-side work of saving to disk etc could be elided. Yes,
it probably makes sense to extend that existing mechanism to include S3 as
well. Just needs someone to do the work. :-)
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchronization, (continued)
- Re: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchronization, Keir Fraser
- Re: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchronization, Joanna Rutkowska
- Re: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchronization, Jan Beulich
- Re: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchronization, Joanna Rutkowska
- Re: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchronization,
Keir Fraser <=
- Re: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchronization, Joanna Rutkowska
- Re: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchronization, Joanna Rutkowska
- RE: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchronization, Dan Magenheimer
- Re: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchronization, Jeremy Fitzhardinge
|
|
|
|
|