Hi, Kaitlin and Toshifumi
Fedora 10 tog-pegasus uses CIM Schema 2.13.1(CIM2131).
(from env_var_Linux.status)
I think it should be upgraded to CIM Schema 2.17.1 or later.
Since CIM Schema supports Virtualization after 2.17.1.
Is this idea is correct?
If this idea is correct, you need to build from upstream openpegasus
or upgrade CIM Schema to 217 on F10 package.
Thanks
Atsushi SAKAI
Toshifumi Fujimura <fujimura.toshifumi(a)np.css.fujitsu.com> wrote:
Dear Kaitlin.
After my investigation, I pass "make postinstall" by using attached patch.
I think these definition in the .mof files are insuffcient.
How do you think?
Regards.
Toshifumi Fujimura.
> Dear Kaitlin.
>
> Thanks for your suggestion and adding wiki page.
> This wiki is very useful.
>
> After restarting Pegasus, I can't find the class
"CIM_KVMRedirectionSAP".
>
> And from my investigation, I found two points.
> (1)The class "CIM_KVMRedirectionSAP"'s superclass isn't defined in
any
> .mof files in Libvirt-CIM.
> (2)But other registered classes may have superclass.
>
> For example, the class "CIM_VirtualSystemMigrationCapabilities" has
> superclass "CIM_Capabilities".
> And that is defined in "schema/VSMigrationCapabilities.mof" file.
> (The log shows below)
>
> I think some package need to add.
> What should I do any more?
>
> Works for me.
>
> ===============================
> [root@localhost libvirt-cim]# grep -rn CIM_KVM *
> Binary file base_schema/cimv216Experimental-MOFs.zip matches
> schema/KVMRedirectionSAP.mof:4:class Xen_KVMRedirectionSAP :
> CIM_KVMRedirectionSAP
> schema/KVMRedirectionSAP.mof:9:class KVM_KVMRedirectionSAP :
> CIM_KVMRedirectionSAP
> schema/KVMRedirectionSAP.mof:14:class LXC_KVMRedirectionSAP :
> CIM_KVMRedirectionSAP
>
> [root@localhost ~]# wbemcli ecn
http://user:pass@localhost/root/virt |
> grep Virt
> localhost:5988/root/virt:CIM_VirtualSystemMigrationSettingData
> localhost:5988/root/virt:KVM_VirtualSystemMigrationCapabilities
> localhost:5988/root/virt:Xen_VirtualSystemMigrationCapabilities
> localhost:5988/root/virt:CIM_VirtualSystemMigrationCapabilities
> localhost:5988/root/virt:LXC_VirtualSystemMigrationSettingData
> localhost:5988/root/virt:LXC_VirtualSystemMigrationCapabilities
> localhost:5988/root/virt:KVM_VirtualSystemMigrationSettingData
> localhost:5988/root/virt:Xen_VirtualSystemSettingData
> localhost:5988/root/virt:CIM_VirtualSystemSettingData
> localhost:5988/root/virt:KVM_VirtualSystemSettingData
> localhost:5988/root/virt:LXC_VirtualSystemSettingData
> localhost:5988/root/virt:Xen_VirtualSystemMigrationSettingData
> ===============================
>
> (in schema/VSMigrationCapabilities.mof)
> ===============================
> class CIM_VirtualSystemMigrationCapabilities : CIM_Capabilities {
>
> uint16 DestinationHostFormatsSupported[];
>
> uint16 SynchronousMethodsSupported[];
>
> uint16 AsynchronousMethodsSupported[];
>
> };
> ===============================
>
> -- Toshifumi Fujimura.
>
>> Toshifumi Fujimura wrote:
>>> Thanks Mr or Ms Deepti B Kalakeri and Mr or Ms Kaitlin Rupert.
>>> I tryed to regist CIM schema for Libvirt-CIM as your advice.
>>>
>>> On "make postinstall",I met this error message.
>>>
>>>
=======================================================================================
>>>
>>> Registering providers with active cimserver
>>> Parsing error: parse error: Error adding class Xen_KVMRedirectionSAP
>>> to the repository:
>>> CIM_ERR_INVALID_SUPERCLASS: CIM_KVMRedirectionSAP
>>> make: *** [postinstall] Error 250
>>>
=======================================================================================
>>>
>>>
>>> I think the superclasses
>>> "CIM_KVMRedirectionSAP","CIM_ERR_INVALID_SUPERCLASS"
don't exist in
>>> my cimserver.
>>> How can I add those classes?
>>>
>>> Works for me.
>>> Toshifumi Fujimura.
>>
>> Can you try the following:
>>
>> Restart Pegasus
>>
>> After restarting Pegasus, try: wbemcli ecn
>>
http://user:pass@localhost/root/virt | grep CIM_KVMRedirectionSAP
>>
>> This should return a record like the following:
>>
>> localhost:5988/root/virt:CIM_KVMRedirectionSAP
>>
>> After that is done, you can do:
>>
>> sudo make preuninstall
>> sudo make postinstall
>>
>> Running "sudo make preuninstall" should have put the proper classes
>> in place. However, sometimes Pegasus needs to be restarted after
>> "sudo make preinstall".
>>
>>
>> If the wbemcli command doesn't return any records, you can do the
>> following:
>>
>> sudo make preuninstall
>> sudo make preinstall
>>
>> restart Pegasus
>>
>> sudo make postinstall
>>
>>
>> I hope this helps!
>
>
--
Toshifumi Fujimura.