From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: S3 sleep in dom0 breaks dom0<->domU wallclock synchronization Date: Tue, 6 Jul 2010 04:52:45 +0100 Message-ID: References: <4C3261C8.4000808@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C3261C8.4000808@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge , Joanna Rutkowska Cc: "xen-devel@lists.xensource.com" , Jeremy Fitzhardinge , Rafal Wojtczuk , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 05/07/2010 23:50, "Jeremy Fitzhardinge" wrote: >> BTW: wouldn't it be good to actually notify them? Consider e.g. DomU >> that has some device assigned to it (say a NIC) -- if we emulated S3 >> suspend/resume for this DomU, there is a hope it would properly >> suspend/reinitialize the NIC, wouldn't it? >> > > I guess? That implies some kind of PV S3 suspend and resume event to > 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 passthrough. We support HVM virtual S3, and can S3-sleep HVM guests across real host S3, but we don't have similar for PV guests. -- Keir