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

[Xen-cim] Original libxm and dom0

To: xen-cim@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-cim] Original libxm and dom0
From: Jim Fehlig <jfehlig@xxxxxxxxxx>
Date: Tue, 16 May 2006 17:46:16 -0600
Delivery-date: Tue, 16 May 2006 16:46:36 -0700
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>
Sender: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (X11/20041206)
Did the original libxm return info on dom0? The "shim" libxm does and I found that enumerating instances of Xen_Disk and Xen_NetworkPort crash the cimom when the current domain is dom0 - since there is no vif or vbd info. I have fixed this in both Xen_NetworkPort_Resource.c and Xen_Disk_Resource.c but before committing wanted to know how dom0 was handled previously.

Also, I'm debating on what to tackle next. Capabilities certainly needs some work, as does pools. Gareth - are you working on pools? Ah, and there's the VirtualSystemManagementService - so many choices :-). Suggestions on priorities?

Jim

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

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