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 13:50:29 +0100 Message-ID: References: <4C33051B.30109@invisiblethingslab.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C33051B.30109@invisiblethingslab.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: Joanna Rutkowska , Jan Beulich Cc: Jeremy Fitzhardinge , Jeremy Fitzhardinge , "xen-devel@lists.xensource.com" , Rafal Wojtczuk , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 06/07/2010 11:27, "Joanna Rutkowska" 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