[Libvirt-cim] [PATCH 5 of 7] [TEST] Added KVM support to 32_start_reboot.py of CS

[Deepti B Kalakeri]

Kaitlin Rupert wrote:
> Deepti B Kalakeri wrote:
>>
>>
>> Kaitlin Rupert wrote:
>>>> @@ -41,72 +42,63 @@
>>>> from VirtLib import utils
>>>> from CimTest.Globals import do_main, logger
>>>> from CimTest.ReturnCodes import PASS, FAIL, XFAIL_RC
>>>> -from XenKvmLib.test_doms import undefine_test_domain
>>>> -from XenKvmLib.common_util import get_cs_instance
>>>> +from XenKvmLib.test_doms import destroy_and_undefine_domain
>>>> from XenKvmLib.common_util import create_using_definesystem
>>>> from XenKvmLib.common_util import call_request_state_change
>>>> +from XenKvmLib.common_util import poll_for_state_change
>>>> +from XenKvmLib.common_util import create_netpool_conf, 
>>>> destroy_netpool
>>>>
>>>> -sup_types = ['Xen', 'XenFV']
>>>> +sup_types = ['Xen', 'XenFV', 'KVM']
>>>>
>>>> +bug_req_state = "00002"
>>>
>>> Is this still an issue? Dan submitted a patch that should fix this.
>>>
>> For a KVM guest the RequestedStateChange() fails to reboot the VS.
>> Here is the error which occurs when we try to reboot a KVM guest.
>> libvir: error : this function is not supported by the hypervisor: 
>> virDomainReboot
>> error: Failed to reboot domain cs_test_domain
>>
>
>>
>> I had already informed about this particular problem in the previous 
>> mail "Need CS state transition related info."
>>
>
> I think there should be a different bug number for this. Bug 00002 was 
> because the providers were persisting the state properly. This 
> particular issue is because libvirt doesn't support reboot for KVM, 
> and the provider isn't handling the reboot on its own.
Since this was related to RSC() call I thought of using the existing bug 
number and I know this bug no could be misleading.
Also, I was not sure if I could create a new one.
>
> Can you add a different bug number to the wiki and change the bug 
> number in the test?
Yeah sure, I will update the wiki with the new bug number and send a new 
patch.
>
> Thanks!