WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-cim

Re: [Xen-cim] Settings supported for SLES10 SP1

To: "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>
Subject: Re: [Xen-cim] Settings supported for SLES10 SP1
From: Jim Fehlig <jfehlig@xxxxxxxxxx>
Date: Thu, 01 Mar 2007 13:30:21 -0700
Cc: xen-cim@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 01 Mar 2007 12:33:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-cim-request@lists.xensource.com?subject=help>
List-id: xen-cim mailing list <xen-cim.lists.xensource.com>
List-post: <mailto:xen-cim@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=unsubscribe>
References: 94C8C9E8B25F564F95185BDA64AB05F604C9512B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Sender: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.8 (X11/20060911)
Subrahmanian, Raj wrote:
> 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?
>   

Yep.  Added support for specifying vncunused, vncpasswd, etc.  I'm
building new RPMs now and will send off list.

Jim
> 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-cim-bounces@xxxxxxxxxxxxxxxxxxx 
>> [mailto:xen-cim-bounces@xxxxxxxxxxxxxxxxxxx] 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-cim@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-cim
>   

_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim

<Prev in Thread] Current Thread [Next in Thread>