From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35304) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWrWh-000639-R2 for qemu-devel@nongnu.org; Tue, 01 Sep 2015 15:47:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZWrWe-0005eI-Gs for qemu-devel@nongnu.org; Tue, 01 Sep 2015 15:47:27 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39980) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWrWe-0005e0-8s for qemu-devel@nongnu.org; Tue, 01 Sep 2015 15:47:24 -0400 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id CDCB6A4544 for ; Tue, 1 Sep 2015 19:47:23 +0000 (UTC) References: <1440793108-25061-1-git-send-email-lersek@redhat.com> From: Eric Blake Message-ID: <55E600C5.9030505@redhat.com> Date: Tue, 1 Sep 2015 13:47:17 -0600 MIME-Version: 1.0 In-Reply-To: <1440793108-25061-1-git-send-email-lersek@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cErjnVwOFCKSASQJIu7rpoi4sochjIkOB" Subject: Re: [Qemu-devel] [RFC] docs: describe QEMU's VMGenID design List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek , qemu-devel@nongnu.org Cc: Gal Hammer , Paolo Bonzini , Igor Mammedov , "Michael S. Tsirkin" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --cErjnVwOFCKSASQJIu7rpoi4sochjIkOB Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 08/28/2015 02:18 PM, Laszlo Ersek wrote: > Cc: Paolo Bonzini > Cc: Gal Hammer > Cc: Igor Mammedov > Cc: "Michael S. Tsirkin" > Signed-off-by: Laszlo Ersek > --- >=20 > Notes: > This is based on the super long private email discussion we had two= > months ago, plus on the IRL discussion between Michael and myself @= the > KVM Forum 2015. >=20 > docs/specs/vmgenid.txt | 343 +++++++++++++++++++++++++++++++++++++++++= ++++++++ > 1 file changed, 343 insertions(+) > create mode 100644 docs/specs/vmgenid.txt >=20 Grammar review; I may miss some technical details. > diff --git a/docs/specs/vmgenid.txt b/docs/specs/vmgenid.txt > new file mode 100644 > index 0000000..d4bf132 > --- /dev/null > +++ b/docs/specs/vmgenid.txt > @@ -0,0 +1,343 @@ > +Virtual Machine Generation ID Device > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Is it worth a preamble giving a specific copyright/license for this file? Without one, it inherits the default GPLv2+ from the top-level, and there are some people (although I'm not one) that worry that an independent implementation of a GPL'd spec must itself be GPL (that is, specifically choosing a looser license for the spec may make it more amenable to the OVMF folks). > + > +The Microsoft specification entitled "Virtual Machine Generation ID", > +maintained at , defin= es an ACPI > +feature that allows the guest OSPM to recognize when it has been retur= ned "to > +an earlier point in time", eg. by restoral from snapshot, or by incomi= ng s/eg./e.g./ s/restoral/restoring/ > +migration. Quoting the spec, [I'm not sure that incoming migration is necessarily returning to an earlier point in time; although I can certainly see that being the case when repeatedly doing incoming migration from the same file] > + > + The virtual machine generation ID is a feature whereby the virtual= machines s/machines/machine's/ [oh wait, you're quoting Microsoft's poor grammar] > + BIOS will expose a new ID. This is a 128-bit, cryptographically ra= ndom > + integer value identifier that will be different every time the vir= tual > + machine executes from a different configuration file-such as execu= ting from > + a recovered snapshot, or executing after restoring from backup. [.= =2E.] > + > +The document you are reading now extracts the requirements set forth b= y the > +VMGenID spec for hypervisors that intend to provide the feature, and d= escribes > +QEMU's implementation. The design below targets both SeaBIOS and OVMF = as > +compatible guest firmwares, without any changes to either of them. > + Otherwise, I didn't spot any obvious wording problems. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --cErjnVwOFCKSASQJIu7rpoi4sochjIkOB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJV5gDFAAoJEKeha0olJ0NqXikIAIqPZepQzYk4CQm0GPFy+r+4 J3PeELMectb2xrxIVeonpCEfYhF6/QOMJ+r82wF/WE9HEqS0qQjQmzdOZG9No8VL yRekJZG6p1v74eARpzsxPz0pRY+xijPGLCfbNdZT87RzNGtLEpeNLlfuBYuAopSQ x+xFL7V4DF6XFkwpiFqKAn0pTECJ3YZTIW6EXo2TgzXGbWjCWw0Dkie45Z8YJc5m 5UbhgOeR0ZsnCxutNRD+PawydP0/ZGQqzzQnjaOcgOvgWIZK2cejQKr6MPIx1GUB M70UtdVZ6RVzQFTTUKnQTacJ01mEVGORxzPHKYbycUqrM2CyK/nMD9yt5JbE+Hc= =SawW -----END PGP SIGNATURE----- --cErjnVwOFCKSASQJIu7rpoi4sochjIkOB--