Re: Need CS state transition related info.
Deepti B Kalakeri wrote:
Hi,
I have following query regarding the CS provider state transition.
1)
The following tc 32_start_reboot.py, which tries to use DefineSystem() to first define the VS and then change the state from Start to Reboot, fails for KVM with the following error.
ComputerSystem - 32_start_reboot.py: FAIL ERROR - Exception: (1, u'CIM_ERR_FAILED: Domain Operation Failed') ERROR - Unable to Reboot dom test_domain using RequestedStateChange() InvokeMethod(RequestStateChange): CIM_ERR_FAILED: Domain Operation Failed
tc cannot be used to support KVM, because of the following debug statement
*Virt_ComputerSystem.c(807): Reboot domain libvir: error : this function is not supported by the hypervisor: virDomainReboot* * *Is my analysis correct?
What version of libvirt is this with? For KVM, we are more concerned with newer version of libvirt. So this might be something we can get fixed in libvirt. The previous version of the libvirt was 0.4.2. I updated the libvirt yesterday on my machine to 0.4.4. I still see the same error. Virt_ComputerSystem.c(807): Reboot domain
Kaitlin Rupert wrote: libvir: error : this function is not supported by the hypervisor: virDomainReboot
2) According to the state transition diagram in the DMTF VSP doc (Pg: 20) implies that a state transition from *Suspend* to *Active(through reboot) *is valid, but our provider returns an *exception. *What is the correct state transition to be considered? We can use 33_suspend_reboot.py tc to verify the same.
This sounds like a bug.Can you capture the exception you're seeing and send it to the external mailing list? I haven't had a chance today to look into it.
Here is the provider exception that is thrown when the VS state is changed from suspend to reboot. ERROR - DETAILS IS (1, u'CIM_ERR_FAILED: Domain not running') InvokeMethod(RequestStateChange): CIM_ERR_FAILED: Domain not running Thanks and Regards, Deepti.
Thanks!
1)
The following tc 32_start_reboot.py, which tries to use DefineSystem() to first define the VS and then change the state from Start to Reboot, fails for KVM with the following error.
ComputerSystem - 32_start_reboot.py: FAIL ERROR - Exception: (1, u'CIM_ERR_FAILED: Domain Operation Failed') ERROR - Unable to Reboot dom test_domain using RequestedStateChange() InvokeMethod(RequestStateChange): CIM_ERR_FAILED: Domain Operation Failed
tc cannot be used to support KVM, because of the following debug statement
*Virt_ComputerSystem.c(807): Reboot domain libvir: error : this function is not supported by the hypervisor: virDomainReboot* * *Is my analysis correct?
What version of libvirt is this with? For KVM, we are more concerned with newer version of libvirt. So this might be something we can get fixed in libvirt. The previous version of the libvirt was 0.4.2. I updated the libvirt yesterday on my machine to 0.4.4. I still see the same error. Virt_ComputerSystem.c(807): Reboot domain libvir: error : this function is not supported by the hypervisor: virDomainReboot
I was unable to catch up with the libvirt folks about this issue. However, we can handle this with the providers (instead of using the libvirt API call directly). I'd consider this test an XFAIL in the KVM case.
2) According to the state transition diagram in the DMTF VSP doc (Pg: 20) implies that a state transition from *Suspend* to *Active(through reboot) *is valid, but our provider returns an *exception. *What is the correct state transition to be considered? We can use 33_suspend_reboot.py tc to verify the same.
This sounds like a bug.Can you capture the exception you're seeing and send it to the external mailing list? I haven't had a chance today to look into it.
Here is the provider exception that is thrown when the VS state is changed from suspend to reboot.
ERROR - DETAILS IS (1, u'CIM_ERR_FAILED: Domain not running') InvokeMethod(RequestStateChange): CIM_ERR_FAILED: Domain not running
This is an issue I addressed in a patch I sent out last week. I need to make some modifications to that patch still. So this one is a provider bug. -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com
participants (2)
-
Deepti B Kalakeri -
Kaitlin Rupert