From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Joanna Rutkowska <joanna@invisiblethingslab.com>,
Jan Beulich <JBeulich@novell.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Rafal Wojtczuk <rafal@invisiblethingslab.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: S3 sleep in dom0 breaks dom0<->domU wallclock synchronization
Date: Tue, 6 Jul 2010 13:50:29 +0100 [thread overview]
Message-ID: <C858E525.197BC%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C33051B.30109@invisiblethingslab.com>
On 06/07/2010 11:27, "Joanna Rutkowska" <joanna@invisiblethingslab.com>
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
next prev parent reply other threads:[~2010-07-06 12:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 3:04 S3 sleep in dom0 breaks dom0<->domU wallclock synchronization Rafal Wojtczuk
2010-07-01 14:50 ` Keir Fraser
2010-07-01 14:51 ` Keir Fraser
2010-07-01 15:18 ` Joanna Rutkowska
2010-07-01 16:12 ` Keir Fraser
2010-07-05 19:18 ` Jeremy Fitzhardinge
2010-07-05 19:26 ` Keir Fraser
2010-07-05 22:43 ` Joanna Rutkowska
2010-07-05 22:50 ` Jeremy Fitzhardinge
2010-07-05 23:03 ` Joanna Rutkowska
2010-07-05 23:19 ` Jeremy Fitzhardinge
2010-07-06 9:12 ` Joanna Rutkowska
2010-07-06 16:17 ` Jeremy Fitzhardinge
2010-07-06 3:52 ` Keir Fraser
2010-07-06 9:10 ` Joanna Rutkowska
2010-07-06 10:02 ` Jan Beulich
2010-07-06 10:27 ` Joanna Rutkowska
2010-07-06 12:50 ` Keir Fraser [this message]
2010-07-06 14:09 ` Joanna Rutkowska
2010-07-08 14:06 ` Joanna Rutkowska
2010-07-06 14:53 ` Dan Magenheimer
2010-07-06 16:24 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C858E525.197BC%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=Jeremy.Fitzhardinge@citrix.com \
--cc=jeremy@goop.org \
--cc=joanna@invisiblethingslab.com \
--cc=konrad.wilk@oracle.com \
--cc=rafal@invisiblethingslab.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).