|
llibxm only returns(ed) data on DomU's created thru it. So no, it does not return info about Dom0. In the context of Xen, Dom0 is really the 'hosting" computer system, so IMHO it should not be treated as a "virtual system"/guest, but rather be exposed via the so-called 'host' CIM instrumentation. So I do not think Dom0 should show up in libvirt when you enumerate the list of current active/inactive virtual systems.
I'm currently working on pools and their capabilities, mostly bringing them up to snuff with the latest MOFs. VirtualSystemManagementService would be an excellent candidate to hit next!
- Gareth
Gareth S. Bestor, PhD.
IBM Linux Technology Center
M/S DES2-01
15300 SW Koll Parkway, Beaverton, OR 97006
503-578-3186, T/L 775-3186, Fax 503-578-3186
Sent by: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
To: xen-cim@xxxxxxxxxxxxxxxxxxx
cc:
Subject: [Xen-cim] Original libxm and dom0
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
_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim
|
Home