[Libvirt-cim] [PATCH 1 of 6] Update VSSD schemas for FullVirt

# HG changeset patch # User Dan Smith <danms(a)us.ibm.com&gt; # Date 1200587101 28800 # Node ID 65402823a5f10e571e7ed2c61694f1743525006f # Parent 05fa2ceba145e9e93066bd66c74299680bd7d21d Update VSSD schemas for FullVirt This adds a flag to the Xen VSSD to enable full-virt or not, as well as the required boot device information. In the implementation, a "false" or missing value for the flag will indicate paravirt-ness. For KVM, I added the boot device as well, since that's something it will always need. For both, a missing boot device will imply "hd". Changes: - Fixed capitalization of IsFullVirt Signed-off-by: Dan Smith <danms(a)us.ibm.com&gt; diff -r 05fa2ceba145 -r 65402823a5f1 schema/VSSD.mof --- a/schema/VSSD.mof Tue Jan 15 16:24:39 2008 -0800 +++ b/schema/VSSD.mof Thu Jan 17 08:25:01 2008 -0800 @@ -8,8 +8,17 @@ class Xen_VirtualSystemSettingData : CIM class Xen_VirtualSystemSettingData : CIM_VirtualSystemSettingData { + [Description ("Flag to determine whether this guest is fully-virtualized")] + boolean IsFullVirt; + + [Description ("The bootloader and arguments to use when in " + "para-virtualized mode")] string Bootloader; string BootloaderArgs; + + [Description ("The device to boot from when in fully-virtualized mode." + "One of hd,fd,cdrom.")] + string BootDevice; }; @@ -20,4 +29,8 @@ class Xen_VirtualSystemSettingData : CIM ] class KVM_VirtualSystemSettingData : CIM_VirtualSystemSettingData { + + [Description ("The device to boot from. One of hd,fd,cdrom.")] + string BootDevice; + };