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 std_invokemethod.c(305): Method `MigrateVirtualSystemToHost' returned 7 misc_util.c(72): Connecting to libvirt with uri `xen' misc_util.c(199): URI of connection is: xen:/// misc_util.c(199): URI of connection is: xen:/// device_parsing.c(257): Disk node: disk infostore.c(88): Path is /etc/libvirt/cim/Xen_RHELVM-GUI-1 <snip> Can you suggest us how to get around this? 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: Wednesday, August 05, 2009 10:21 PM To: List for discussion and development of libvirt CIM Cc: Velayudham, Madan Ganesh (STSD / ESS SW) Subject: Re: [Libvirt-cim] MigratevirtualSystemToHost reports "unsupported" Subba Rao, Sandeep M (STSD) wrote:

Hi,

I'm trying to perform a live move of a domU using libvirt-cim, but I'm receiving a CIM_ERR_NOT_SUPPORTED exception. I have attached the request and response xmls.

The same operation when tried through virsh command worked.

Please let me know if I'm missing something here.

Hi Sandeep, I don't see anything obvious in the information you provided. The return error of CIM_ERR_NOT_SUPPORTED is interesting, as both versions of libvirt support the MigrateVirtualSystemToHost() method. I'm wondering if something is happening in the CIMOM before our method even gets called. Can you enable debugging in the libvirt-cim providers and then provide the log output you get? You can enable debugging using the following: export CU_DEBUG="/tmp/libvirt-cim.log" Then restart the CIMOM in the same terminal (to make sure it picks up the environment settings). Thanks!

Thanks for the help.

Regards, Sandeep

The following are the details of the 2 machines.

Source Xen host: RHEL 5.3

The virsh comamnd that worked: virsh migrate --live Copy_Copy_RHEL52VM1 xen:/// xenmigr://15.154.102.20/

Libvirt and libvirt-cim Versions: [root@RHEL53Xen1 xen]# rpm -qa | grep -i libvirt libvirt-0.3.3-14.el5 libvirt-devel-0.3.3-14.el5 libvirt-cim-0.5.1-4.el5 libvirt-python-0.3.3-14.el5

RHEL Version: [root@RHEL53Xen1 xen]# cat /etc/issue Red Hat Enterprise Linux Server release 5.3 (Tikanga) Kernel \r on an \m

Xen Version: [root@RHEL53Xen1 xen]# rpm -qa | grep xen xen-3.0.3-80.el5 xen-libs-3.0.3-80.el5 xen-devel-3.0.3-80.el5 kernel-xen-2.6.18-128.el5

Destination Xen host: RHEL 5.2

Libvirt and libvirt-cim Versions: [root@Rhel52-Xen ~]# rpm -qa | grep libvirt libvirt-cim-0.4-1 libvirt-0.3.3-7.el5 libvirt-python-0.3.3-7.el5

RHEL Version: [root@Rhel52-Xen ~]# cat /etc/issue Red Hat Enterprise Linux Server release 5.2 (Tikanga) Kernel \r on an \m

Xen Version: [root@Rhel52-Xen ~]# rpm -qa | grep xen xen-libs-3.0.3-64.el5 xen-3.0.3-64.el5 kernel-xen-devel-2.6.18-92.el5 kernel-xen-2.6.18-92.el5

------------------------------------------------------------------------

_______________________________________________ Libvirt-cim mailing list Libvirt-cim@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-cim

-- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com

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. <snip> 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 9e5f538c-3658-4e31-9b97-b528d51d063d Virt_VSMigrationService.c(1283): Creating instance: root/virt:Virt_MigrationJob.InstanceID="9e5f538c-3658-4e31-9b97-b528d51d063d" Virt_VSMigrationService.c(783): Creating indication. misc_util.c(72): Connecting to libvirt with uri `xen' misc_util.c(199): URI of connection is: xen:/// Virt_VSMigrationService.c(757): Setting SourceInstance std_indication.c(70): Indications disabled for this provider std_invokemethod.c(305): Method `MigrateVirtualSystemToHost' returned 0 Virt_VSMigrationService.c(1184): Migration Job 9e5f538c-3658-4e31-9b97-b528d51d063d started Virt_VSMigrationService.c(833): MigrationJob ref: root/virt:Virt_MigrationJob.InstanceID="9e5f538c-3658-4e31-9b97-b528d51d063d" Virt_VSMigrationService.c(783): Creating indication. Virt_VSMigrationService.c(806): Setting PreviousInstance Virt_VSMigrationService.c(896): Modifying job 9e5f538c-3658-4e31-9b97-b528d51d063d (4:Running) misc_util.c(72): Connecting to libvirt with uri `xen' misc_util.c(199): URI of connection is: xen:/// Virt_VSMigrationService.c(757): Setting SourceInstance std_indication.c(70): Indications disabled for this provider misc_util.c(72): Connecting to libvirt with uri `xen' Virt_VSMigrationService.c(1118): Remote domain `Copy_Copy_RHEL52VM1' exists Virt_VSMigrationService.c(833): MigrationJob ref: root/virt:Virt_MigrationJob.InstanceID="9e5f538c-3658-4e31-9b97-b528d51d063d" Virt_VSMigrationService.c(783): Creating indication. misc_util.c(72): Connecting to libvirt with uri `xen' misc_util.c(199): URI of connection is: xen:/// Virt_VSMigrationService.c(757): Setting SourceInstance std_indication.c(70): Indications disabled for this provider Virt_VSMigrationService.c(1189): Migration Job 9e5f538c-3658-4e31-9b97-b528d51d063d finished: 1 Virt_VSMigrationService.c(833): MigrationJob ref: root/virt:Virt_MigrationJob.InstanceID="9e5f538c-3658-4e31-9b97-b528d51d063d" Virt_VSMigrationService.c(783): Creating indication. Virt_VSMigrationService.c(806): Setting PreviousInstance Virt_VSMigrationService.c(896): Modifying job 9e5f538c-3658-4e31-9b97-b528d51d063d (7:Remote already has domain `Copy_Copy_RHEL52VM1') <snip> Is repositoryIsDefaultInstanceProvider option enabled by default, should we customize this? 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

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