Re: [Libvirt-cim] Re: XenFV on Pegasus Test Run Summary for Oct 20 2008
> =================================================
> FAIL Test Summary:
> ComputerSystem - 03_defineVS.py: FAIL
> ElementSettingData - 01_forward.py: FAIL
> HostSystem - 02_hostsystem_to_rasd.py: FAIL
> HostSystem - 04_hs_to_EAPF.py: FAIL
> LogicalDisk - 01_disk.py: FAIL
All the above passed when run manually.
These look like they are failing due to the libvirt caching issue.
Calling cim_define() instead of define() will probably fix the issue.
> VirtualSystemManagementService - 09_procrasd_persist.py: FAIL
>
This one failed as the virsh schedinfo is returning 0 for cap value,
while the test case is expecting a limit value of 256.
virsh schedinfo rstest_domain
Scheduler : credit
weight : 256
cap : 0
Should we replace the use of virsh and use GetInstance on ProcRASD to
verify the values?
Yes, this test should be using the values from the ProcRASD to verify.
The ProcRASD instance and virsh should report the same value, so
changing this most likely won't fix the test failure. However, it would
be a good change to make.
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com