From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:59739) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RrutY-0004XS-Du for qemu-devel@nongnu.org; Mon, 30 Jan 2012 12:20:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RrutP-0003ge-Tw for qemu-devel@nongnu.org; Mon, 30 Jan 2012 12:19:56 -0500 Received: from e8.ny.us.ibm.com ([32.97.182.138]:35794) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RrutP-0003fv-RE for qemu-devel@nongnu.org; Mon, 30 Jan 2012 12:19:47 -0500 Received: from /spool/local by e8.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 30 Jan 2012 12:19:45 -0500 Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 3616C6E8B0D for ; Mon, 30 Jan 2012 12:07:18 -0500 (EST) Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q0UH7Hw3217712 for ; Mon, 30 Jan 2012 12:07:17 -0500 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q0UH7Had032363 for ; Mon, 30 Jan 2012 15:07:17 -0200 Message-ID: <4F26CE3E.50801@linux.vnet.ibm.com> Date: Mon, 30 Jan 2012 11:07:10 -0600 From: Michael Roth MIME-Version: 1.0 References: <20120126144632.GM21211@redhat.com> <4F216EAB.2000707@redhat.com> <20120126173533.0079dc98@doriath.home> <4F21DA3D.9020203@codemonkey.ws> <20120130105747.1cba8bbb@doriath> <4F26A130.10000@codemonkey.ws> <20120130124453.35fc1894@doriath> <4F26BE11.6060208@redhat.com> In-Reply-To: <4F26BE11.6060208@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [libvirt] [PATCH RFC 0/4] Allow hibernation on guests List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: libvir-list@redhat.com, Michal Privoznik , QEMU Developers , Luiz Capitulino On 01/30/2012 09:58 AM, Eric Blake wrote: > On 01/30/2012 07:44 AM, Luiz Capitulino wrote: >> I think we should do the following then: >> >> 1. Drop the set-support-level command >> 2. Split the guest-suspend command into guest-suspend-ram, guest-suspend-hybrid, >> guest-suspend-disk >> 3. Libvirt should query for _QEMU_'s 'wakeup' command before issuing >> the guest-suspend-ram command >> >> Michal, Michael, do you agree? > > I'm not Michal, but speaking for libvirt, this definitely sounds like > the way to go. > > Questions: > > Should libvirt also check for 'wakeup' before attempting > guest-suspend-hybrid? > > With guest-suspend-disk, what happens when the suspend completes? Does > this look like a normal case of the guest powering down, which qemu then > passes as an event to libvirt and libvirt then ends the qemu process? > That would mean that the only difference from a normal guest shutdown is > that on the next guest boot the guest's disk image allows to recover > state from disk rather than booting from scratch; either way, a new qemu > process is created to resume the guest, and qemu is doing nothing > different in how it starts the guest (it's just that the guest itself > does something different based on what it stored into the disk images > before shutting down). > > Also, I know there has been talk about a qemu-ga command to resync > clocks after a resume from S3 and/or 'loadvm'; is this command fully in > place yet, and is it another command that libvirt should be checking for > prior to allowing any S3 attempts? > Hi Eric, I'm not aware of a clock re-sync command being worked on.. are we maybe talking about the guest-sync command qemu-ga currently has in place to re-sync the protocol stream after a client-side timeout?