Hi Kaitlin,
Hope you are doing fine.
We need a clarification regarding the CIM_ConcereteJob support part of
Xen_ComputerSystem.RequestStateChange() method to start or stop a Virtual Machine. After
we invoke the method, we were expecting a return value of 4096 (Operation Scheduled) with
the reference to Job to track the status.
Instead we are noticing that the method returns 0 - indicating success, however the
Virtual machine does not stop because of memory or other errors.
Can you clarify whether this is a known issue in libvirt-CIM? Also recommend how to track
the invoked job?
The OS is an RHEL 5.4 and the libvirt and xen versions are as follows:
[root@RHEL54 ~]# cat /etc/issue
Red Hat Enterprise Linux Server release 5.4 Beta (Tikanga)
Kernel \r on an \m
[root@RHEL54 ~]# uname -a
Linux RHEL54 2.6.18-160.el5xen #1 SMP Mon Jul 27 18:01:58 EDT 2009 i686 i686 i386
GNU/Linux
[root@RHEL54 ~]# rpm -qa | grep libvirt
libvirt-0.6.3-17.el5
libvirt-cim-0.5.5-2.el5
libvirt-python-0.6.3-17.el5
[root@RHEL54 ~]# rpm -qa | grep xen
kernel-xen-devel-2.6.18-160.el5
kernel-xen-2.6.18-160.el5
xen-3.0.3-92.el5
xen-libs-3.0.3-92.el5
[root@RHEL54 ~]# rpm -qa | grep sblim
sblim-cmpi-base-1.5.5-34.el5
[root@RHEL54 ~]#
We also need clarification for live migration. We notice that Xen_ComputerSystem instance
for the Virtual machine which is live migrated is being reported on the source and target
host. Can you clarify us how to determine the actual host where the VM is associated? We
were hoping that HostedDependency association will be helpful, but did not work.
Appreciate any help in this regard.
Sandeep