xen-cim
[Xen-cim] LTC provider working on SLES10/openwbem
FYI,
I have managed to get one of the LTC providers (Xen_ComputerSystem)
working on SLES using openwbem cimom, the xm shim, and libvirt. The
following changes were made:
libvirt
- changed xend_parse_sexp_desc() to not fail if kernel not found. sexp
from xend does not contain kernel for domain 0.
Provider
- In Xen_HostedDisk.[mof | c], changed class Linux_LogicalDisk to
CIM_LogicalDisk as I don't have access to sblim package containing
Linux_LogicalDisk
- In Xen_HostedMemory.[mof | c], changed class Linux_CacheMemory to
CIM_Memory as I don't have access to sblim package containing
Linux_CacheMemory
- In Xen_ComputerSystem.mof, added provider qualifier to specify
implementation library. I will have to figure out how to register the
providers in openwbem. The sblim-cmpi-base package for SLES contains
the provider qualifier for each class definition, so apparently there is
no better solution. I will have to talk to the openwbem group about
adding a better registration mechanism.
- Changes to Makefile.am for building the xm shim and linking it with
the providers.
Don't think I want to spend too much time getting the other providers
working since the code should be changed to reflect current SVPC model.
As I see it, the next task is to modify the current Xen model to reflect
the SVPC model and then adjust the code accordingly. An item for
tomorrow's discussion?
Regards,
Jim
_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-cim] LTC provider working on SLES10/openwbem,
Jim Fehlig <=
|
|
|