[Libvirt-cim] CimTest Report for KVM on F9 23-07-2008

[Deepti B Kalakeri]

Dan Smith wrote:
> DK> ComputerSystem - 40_RSC_start.py: XFAIL Bug: 00001
> DK> ERROR   - Exception: (1, u'CIM_ERR_FAILED: Invalid state transition')
> DK> ERROR   - Exception: RequestedStateChange() could not be used to start domain: 'test_domain'
> DK> InvokeMethod(RequestStateChange): CIM_ERR_FAILED: Invalid state transition
> DK> Bug:<00001>
>
> What is this?  Certainly RequestStateChange() is not broken on KVM,
> right?  And if it is, it definitely shouldn't be an XFAIL.
>
>   
The above tc

*On Xen*   : the test case passes

*On KVM*   : the test case XFAIL's with below reason.
ComputerSystem - 40_RSC_start.py: XFAIL Bug: 00001
ERROR   - Exception: (1, u'CIM_ERR_FAILED: Domain Operation Failed')
ERROR   - Exception: RequestedStateChange() could not be used to start 
domain: '40_test_domain'
InvokeMethod(RequestStateChange): CIM_ERR_FAILED: Domain Operation Failed
Bug:<00001>

The XML from the debug statement is as follows:
<domain type='kvm'>
<uuid>a01c02b7-c8a0-4a49-9c90-0a35e19865da</uuid>
<name>40_test_domain</name>
<on_poweroff>destroy</on_poweroff>
<on_crash>destroy</on_crash>
<os>
  <type>hvm</type>
  <boot dev='hd'/>
</os>
<currentMemory>0</currentMemory>
<memory>0</memory>
<vcpu>1</vcpu>
<devices>
<interface type='network'>
  <mac address='11:22:33:aa:bb:cc'/>
  <source network='default-net55'/>
</interface>
<disk type='file' device='disk'>
  <source file='/tmp/default-kvm-dimage'/>
  <target dev='hda'/>
</disk>
<graphics type='vnc' port='-1'/>
</devices>
</domain>

1)
The XML config file is *just enough* to *define *the guest but not start 
it.
I manually tried to define the guest with the above XML and I was able 
to define it, but when I tried to start the defined guest it failed with 
the following error:

*virsh start 40_test_domain*
libvir: QEMU error : internal error QEMU quit during console startup
error: Failed to start domain 40_test_domain

The only problem with the above XML file is the *Memory and 
currentMemory *being set to* 0.
*I then assigned *1024* in place of *0* for *Memory and currentMemory 
*and I was able to define and start the domain.
I was able to start the domain only when both the values *Memory and 
currentMemory *were not equal to *0*.

The *Memory and currentMemory *being 0 is not a problem in case of Xen 
and XenFV.
I tried checking the difference and the limitation for this field on 
libvirt.org, but was not much successful.

2)
I found one more peculiar problem, even though I was able to 
successfully define KVM domain either using tc or manually, or started 
the KVM guest using the virsh, I was not find any info using the virsh 
-c qemu:///system list --all. Can this be a problem with my machine ? I 
was able to use virsh for other guests though.


*On XenFV* : the test case fails with following error.

ComputerSystem - 40_RSC_start.py: XFAIL Bug: 00002
ERROR   - EnabledState should be 2 not 0
ERROR   - Exception: Attributes were not set as expected for domain: 
'test_domain'
Bug:<00002>

I tried inserting delay in the test case between the 
call_request_state_change() and check_attributes(), and the test case 
Passed :).

PS : The machine had the following network pool
*virsh net-list
Name                 State      Autostart
-----------------------------------------
default-net          active     no      *

Thanks and Regards,
Deepti.
> ------------------------------------------------------------------------
>
> _______________________________________________
> Libvirt-cim mailing list
> Libvirt-cim at redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-cim