Deepti B Kalakeri wrote:
Kaitlin Rupert wrote:
I took a look at this test, and you're right - the reason it's failing is because DestroySystem() is also undefined the guest. So the answer here is to modify the test so that it doesn't call undefine(). Also, make sure the guest isn't in the inactive domain list either.
Not sure why you want to XFAIL the test, as DestroySystem() is doing what is expected.
I thought DestroySystem() is equivalent to "virsh destroy" command which would just destroy a running domain which was defined and started.
Nope, DestroySystem() does a "virsh destroy" and "virsh undefine". If you look at the System Virtualization Profile (DSP1042) under the heading " 8.2.2 CIM_VirtualSystemManagementService.DestroySystem( ) Method (Conditional)", DestroySystem() is defined as:
"The execution of the DestroySystem( ) method shall effect the destruction of the referenced virtual system and all related virtual system configurations, including snapshots." Oh! yeah I read this today. Its been long time I read the DSP1042. Thanks for the clarifications. Updated patch on its way.
No problem =) Thanks for updating the patch! -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com