Deepti B Kalakeri wrote:
Velayudham, Madan Ganesh (STSD / ESS SW) wrote:
Hi Kaitlin,
Thanks for your suggestion.
Our RHEL 5.3 did not have either cimserver_[planned|current].conf file. Hence we enabled the flag repositoryIsDefaultInstanceProvider, now the migrateVirtualSystem call succeeds. Thank you.
Glad to hear it's working =)
Is repositoryIsDefaultInstanceProvider option enabled by default, should we customize this?
During the libivrt-cim install, we should be sure to set this flag, or else our providers don't function properly. However, it's possible for another provider set (or some other package) to overwrite the change me make. So it's difficult to ensure that this option is set properly. We should at least add a note to our README that indicates this should be set.
This would not be enabled by default. If desired you can automate it or enable it manually. For configuration information and the flags necessary for libvirt-cim you can refer to http://wiki.libvirt.org/page/Cimtest
Thanks and Regards, Madan (_MaGa_) Madan Ganesh Velayudham Office: +91 80 2516 5333
-----Original Message----- From: Kaitlin Rupert [mailto:kaitlin@linux.vnet.ibm.com] Sent: Thursday, August 06, 2009 4:38 AM To: Velayudham, Madan Ganesh (STSD / ESS SW) Cc: List for discussion and development of libvirt CIM; Subba Rao, Sandeep M (STSD) Subject: Re: [Libvirt-cim] MigratevirtualSystemToHost reports "unsupported"
Velayudham, Madan Ganesh (STSD / ESS SW) wrote:
Hi Kaitlin,
Thanks for the troubleshooting tip.
We retried the invocation and the same result appeared. The following snippet related to migrateVirtualSystemToHost was found in the /tmp/libvirt-cim.log file.
<snip> device_parsing.c(257): Disk node: disk infostore.c(88): Path is /etc/libvirt/cim/Xen_Copy_Copy_RHEL52VM1 std_invokemethod.c(279): Method `MigrateVirtualSystemToHost' execution attempted std_invokemethod.c(230): Method parameter `ComputerSystem' validated type 0x1100 std_invokemethod.c(230): Method parameter `DestinationHost' validated type 0x1600 std_invokemethod.c(215): No optional parameter supplied for `MigrationSettingData' std_invokemethod.c(230): Method parameter `MigrationSettingData' validated type 0x1000 std_invokemethod.c(303): Executing handler for method `MigrateVirtualSystemToHost' misc_util.c(72): Connecting to libvirt with uri `xen' Virt_VSMigrationService.c(102): Using default values for MigrationSettingData param Virt_VSMigrationService.c(1351): Prepared migration job f64be851-e44a-4d3c-b4a8-bce814ceffe1 Virt_VSMigrationService.c(1283): Creating instance: root/virt:Virt_MigrationJob.InstanceID="f64be851-e44a-4d3c-b4a8-bce814ceffe1"
Virt_VSMigrationService.c(1287): Failed to create job instance: 7
We're doing a callback to the CIMOM here, asking the CIMOM to create an instance of Virt_MigrationJob for us. The CIMOM is responding saying that our request is unsupported.
Can you check the following setting:
# cat /etc/Pegasus/cimserver_planned.conf | grep repositoryIsDefaultInstanceProvider
or
# cat /etc/Pegasus/cimserver_current.conf | grep repositoryIsDefaultInstanceProvider
You should see this set to: repositoryIsDefaultInstanceProvider=true
If it's not, can you try running the following command:
cimconfig -s repositoryIsDefaultInstanceProvider=true -p
Then be sure to restart the CIMOM so it picks up the changes. This tells Pegasus that we would like it to enable it's default provider for generating instances.
Let me know if this doesn't resolve the issue.
-- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com