From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:43968) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rrtcg-0000fD-Bf for qemu-devel@nongnu.org; Mon, 30 Jan 2012 10:58:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rrtca-0000O6-EW for qemu-devel@nongnu.org; Mon, 30 Jan 2012 10:58:26 -0500 Received: from mx1.redhat.com ([209.132.183.28]:1084) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rrtca-0000O1-7t for qemu-devel@nongnu.org; Mon, 30 Jan 2012 10:58:20 -0500 Message-ID: <4F26BE11.6060208@redhat.com> Date: Mon, 30 Jan 2012 08:58:09 -0700 From: Eric Blake 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> In-Reply-To: <20120130124453.35fc1894@doriath> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig65D05E22710294C7FB296492" 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: Luiz Capitulino Cc: libvir-list@redhat.com, Michal Privoznik , QEMU Developers , mdroth@linux.vnet.ibm.com This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig65D05E22710294C7FB296492 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 01/30/2012 07:44 AM, Luiz Capitulino wrote: > I think we should do the following then: >=20 > 1. Drop the set-support-level command > 2. Split the guest-suspend command into guest-suspend-ram, guest-suspe= nd-hybrid, > guest-suspend-disk > 3. Libvirt should query for _QEMU_'s 'wakeup' command before issuing > the guest-suspend-ram command >=20 > 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? --=20 Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --------------enig65D05E22710294C7FB296492 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBCAAGBQJPJr4RAAoJEKeha0olJ0NqDnMH/1V0JfBYmJL/P/N+pLb94p2k g2Tld5TbWmAD+0CNN8LkNZEXWsOHZM9ygLXrXUd/84AZTpPX79klwNal2HeayBcQ 5xp5zd+Q1mt0BSkttpzdWWvCAPBI80BMUp+uG+fWRU2KeepQp326/ngJyr99gk2d LGUftlB7Qt+kkIzb2pHwSZ90BXxP4UK9Hs3pumFAAdWg4Q2dWge7mq6G0n/qYnQL 7nAF0JK0jkJZ67nDo/R5rfmHzaxNMPwOegR1J7DCWxo020+AvAnXoFi+O4Zi214L WOhKIR36RjXgideMKlWc7U+cp/xChJuZFggKoC185VH/kk8PfPJkfOy3iLXVeLM= =K8uf -----END PGP SIGNATURE----- --------------enig65D05E22710294C7FB296492--