From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joanna Rutkowska Subject: Re: S3 sleep in dom0 breaks dom0<->domU wallclock synchronization Date: Tue, 06 Jul 2010 12:27:39 +0200 Message-ID: <4C33051B.30109@invisiblethingslab.com> References: <4C32F320.3060103@invisiblethingslab.com> <4C331B600200007800009B4F@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1872915459==" Return-path: In-Reply-To: <4C331B600200007800009B4F@vpn.id2.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: Jeremy Fitzhardinge , "xen-devel@lists.xensource.com" , Konrad Rzeszutek Wilk , Jeremy Fitzhardinge , Keir Fraser , Rafal Wojtczuk List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1872915459== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0096E2972643C1A296A2CA67" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0096E2972643C1A296A2CA67 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 07/06/10 12:02, Jan Beulich wrote: >>>> On 06.07.10 at 11:10, Joanna Rutkowska wrote: >> On 07/06/10 05:52, Keir Fraser wrote: >>> On 05/07/2010 23:50, "Jeremy Fitzhardinge" wrote: >>> >>>>> BTW: wouldn't it be good to actually notify them? Consider e.g. Dom= U >>>>> that has some device assigned to it (say a NIC) -- if we emulated S= 3 >>>>> suspend/resume for this DomU, there is a hope it would properly >>>>> suspend/reinitialize the NIC, wouldn't it? >>>>> =20 >>>> >>>> I guess? That implies some kind of PV S3 suspend and resume event t= o >>>> feed into the dom U's device model. What does 2.6.18-xen do? >>> >>> I don't think our S3 support is very compatible with PV device passth= rough. >>> We support HVM virtual S3, and can S3-sleep HVM guests across real ho= st S3, >>> but we don't have similar for PV guests. >>> >> >> How about implementing something very simple, like a notification via >> xenstore (say, Dom0 would be setting some key)? Interested DomUs could= >> then register a watch, and get notified when the system was resumed fr= om >> S3. This would let them e.g. to call whatever hypercall is used normal= ly >> on DomU boot to sync DomU wallclock, or reinitialize/reconnect the NIC= =2E >=20 > 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 treatin= g > different kinds of guests differently here is unnecessary) guests > before doing a host suspend, as Jeremy had suggested in an earlier > reply? >=20 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? j. --------------enig0096E2972643C1A296A2CA67 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkwzBSAACgkQORdkotfEW84U7ACfbc4lbS9qyjpxm9SE3t1Qw9Kd KwYAoOBXzAaK2mFGRjuVYaZkc3K3hEkO =1+QG -----END PGP SIGNATURE----- --------------enig0096E2972643C1A296A2CA67-- --===============1872915459== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1872915459==--