[Libvirt-cim] [PATCH] [RFC] Update VSSD schemas for FullVirt

[Dan Smith]

# HG changeset patch
# User Dan Smith <danms at us.ibm.com>
# Date 1200499991 28800
# Node ID 61dcb1a6e2097e8125db046d6aa53bda4bc18a20
# Parent  05fa2ceba145e9e93066bd66c74299680bd7d21d
[RFC] 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".

Comments?  Additions?

Signed-off-by: Dan Smith <danms at us.ibm.com>

diff -r 05fa2ceba145 -r 61dcb1a6e209 schema/VSSD.mof
--- a/schema/VSSD.mof	Tue Jan 15 16:24:39 2008 -0800
+++ b/schema/VSSD.mof	Wed Jan 16 08:13:11 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;
+
 };