Guo Lian Yun wrote:
================================================= KVM on Pegasus Test Run Summary for Dec 15 2008 ================================================= Distro: Fedora release 9 (Sulphur) Kernel: 2.6.25.14-108.fc9.x86_64 libvirt: 0.4.4 Hypervisor: QEMU 0.9.1 CIMOM: Pegasus 2.7.0 Libvirt-cim revision: 613 Libvirt-cim changeset: 1fcf330fadf8+ Cimtest revision: 539 Cimtest changeset: d63674216d3f ================================================= FAIL : 2 XFAIL : 2 SKIP : 6 PASS : 129 ----------------- Total : 139 ================================================= FAIL Test Summary: VirtualSystemManagementService - 14_define_sys_disk.py: FAIL
The above tc is failing because of the the missing VirtualDevice field in the DiskRASD passed to DefineSystem(). The net, disk, proc, mem RASD properties passed to the DefineSystem() in this tc are obtained by the association of AC with SettingsDefineCapabilities. With the F9 rpm the VirtualDevice field in the DiskRASD is not set and hence the DefineSystem() throws an error. The tc passes when we include rasd['VirtualDevice'] field to contain appropriate VirtualDevice value 'hda' in case [KVM] of F9 rpm. I have a doubt here, the changes to throw an error on Missing VirtualDevice field was included in the modifications made to the patch with revision 681 "Remove the default implied VirtualDevice on DiskRASD", but the changes included in the F9 rpm are upto 613. Can you let me know upto which changeset does the F9 rpm cover?
VirtualSystemManagementService - 15_mod_system_settings.py: FAIL The tc fails only with the KVM F9 rpm. The value of AutomaticRecoveryAction is set to 2 only for KVM with F9 rpm, otherwise the value is 3 for Xen and KVM with current sources. I am not able to track if this was expected behavior of setting AutomaticRecoveryAction to 2 when the F9 rpm was built and was changed later to be set to 3 for the modifications beyond revision 613. Can you help ?
Thanks and Regards, Deepti.