[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [PATCH V14 1/3] docs: vm generation id device's description

From: Igor Mammedov
Subject: [Qemu-devel] [PATCH V14 1/3] docs: vm generation id device's description
Date: Tue, 3 Mar 2015 17:18:13 +0100

From: Gal Hammer <address@hidden>

Signed-off-by: Gal Hammer <address@hidden>
Signed-off-by: Igor Mammedov <address@hidden>
 - ammend doc since no more MMIO occupied by vmgenid
   device and device became PCIDevice
 docs/specs/vmgenid.txt | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)
 create mode 100644 docs/specs/vmgenid.txt

diff --git a/docs/specs/vmgenid.txt b/docs/specs/vmgenid.txt
new file mode 100644
index 0000000..718850a
--- /dev/null
+++ b/docs/specs/vmgenid.txt
@@ -0,0 +1,36 @@
+Copyright (C) 2014 Red Hat, Inc.
+This work is licensed under the terms of the GNU GPL, version 2 or later.
+See the COPYING file in the top-level directory.
+The VM generation ID (vmgenid) device is an emulated device which
+exposes a 128-bit, cryptographically random, integer value identifier.
+This allows management applications (e.g. libvirt) to notify the guest
+operating system when the virtual machine is executed with a different
+configuration (e.g. snapshot execution or creation from a template).
+This is specified on the web at: http://go.microsoft.com/fwlink/?LinkId=260709
+The vmgenid device is a PCI device with the following ACPI ID: "QEMU0003".
+The device has a "vmgenid.uuid" property, which can be set using
+the command line argument or the QMP interface.
+For example:
+QEMU  -device vmgenid,id=FOO,uuid="324e6eaf-d1d1-4bf6-bf41-b9bb6c91fb87"
+Or to change uuid in runtime use:
+ qom-set "/machine/peripheral/FOO.uuid" "124e6eaf-d1d1-4bf6-bf41-b9bb6c91fb87"
+According to the specification, any change to the GUID executes an
+ACPI notification. The vmgenid device triggers the \_GPE._E00 handler
+which executes the ACPI Notify operation.
+Although not specified in Microsoft's document, it is assumed that the
+device is expected to use the little-endian system.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]