[Libvirt-cim] Re: XenFV on Pegasus Test Run Summary for Oct 20 2008
Deepti B Kalakeri
deeptik at linux.vnet.ibm.com
Mon Oct 20 07:46:39 UTC 2008
Deepti B Kalakeri wrote:
> =================================================
> XenFV on Pegasus Test Run Summary for Oct 20 2008
> =================================================
> Distro: Red Hat Enterprise Linux Server release 5.2 (Tikanga)
> Kernel: 2.6.18-92.el5xen
> libvirt: 0.3.3
> Hypervisor: Xen 3.1.0
> CIMOM: Pegasus 2.7.0
> Libvirt-cim revision: 720
> Libvirt-cim changeset: 0f39ab1ee830
> =================================================
> FAIL : 6
> XFAIL : 0
> SKIP : 4
> PASS : 126
> -----------------
> Total : 136
> =================================================
> 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.
> 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?
Thanks and Regards,
Deepti.
More information about the Libvirt-cim
mailing list