2 messages in com.xensource.lists.xen-cimRE: [Xen-cim] Settings supported for ...| From | Sent On | Attachments |
|---|---|---|
| Jim Fehlig | 22 Feb 2007 19:34 | .mof |
| Subrahmanian, Raj | 01 Mar 2007 12:03 |
| Subject: | RE: [Xen-cim] Settings supported for SLES10 SP1![]() |
|---|---|
| From: | Subrahmanian, Raj (raj....@unisys.com) |
| Date: | 03/01/2007 12:03:04 PM |
| List: | com.xensource.lists.xen-cim |
Jim, The tip of the os-cmpi-xen.hg tree won't compile with the headers that you had sent us. Specifically, there is no member called other_config. Did you backport something in?
When we try to create a vm with the earlier changeset, there is a null-pointer exception, I think it's because of the console class stuff being null.
Raj
-----Original Message----- From: xen-...@lists.xensource.com [mailto:xen-...@lists.xensource.com] On Behalf Of Jim Fehlig Sent: Thursday, February 22, 2007 10:35 PM To: xen-cIM Subject: [Xen-cim] Settings supported for SLES10 SP1
For SLES10 SP1 I would like to support some additional settings in Xen_ComputerSystemSettingData. Attached is an updated mof. Notice I removed some of the existing settings (most were commented anyway) such as DHCP, Gateway, etc. These are very Linux specific and are just appended to kernel args in xend anyway so they can be specified in KernelOptions if needed. What do you think about the enums for On[Poweroff|Reboot|Crash]? They are enums in Xen API and the values were taken from the spec.
I think the Xen_Console and Xen_ConsoleSettingData classes Raj sent earlier should suffice. Absence of an instance of Xen_ConsoleSettingData on DefineSystem implies 'nographic', otherwise protocol property will handle VNC, SDL, or text. We'll take the defaults for all other VNC related settings found in a legacy config file. I think the defaults are reasonable anyway, e.g. use the first unused port >= 5900. Explicitly specifying a port seems problematic in the event you move the guest to another host and the specified port is already in use. Perhaps vncpasswd needs some thought. It could be supported via the ConsoleConfigInfo property on Xen_ConsoleSettingData. There is a corresponding dumping ground field on the Console class in Xen API.
I think the important thing for console is being able to determine how to connect to the guest once it is launched. The URI property should contain the port to connect with a viewer when Xen_Console or Xen_ConsoleSettingData is queried on a running guest.
BTW, any suggestions from SVPC on the console issue? Was there an opportunity to discuss it on today's call?
Raj - one thing you could help me with is implementation of ModifySystemSettings on class Xen_VirtualSystemManagementService. This extrinsic is used to modify properties of Xen_ComputerSystemSettingData. Probably not a lot in there that we want to support modifying, but I could see users wanting to change the On[Poweroff|Reboot|Crash] behavior, KernelOptions and perhaps even Kernel and RAMDisk. I don't think we want to support modifying Bootloader, BootloaderOptions, acpi, apic, pae, or localtime. Anyway, take a look at Xen_VirtualSystemManagementService.c and search for ModifySystemSettings. It currently returns CMPI_RC_ERR_NOT_SUPPORTED.
Regards, Jim
_______________________________________________ Xen-cim mailing list Xen-...@lists.xensource.com http://lists.xensource.com/xen-cim





.mof