[Libvirt-cim] Re: XenFV on Pegasus Test Run Summary for Sep 11 2008

Deepti B Kalakeri wrote: The above tc will pass if we revert back to the changes done using "[PATCH 4 of 6] [TEST] Make network related changes to VSMS tests". This test case when run in the batch mode shows the following XML in the debug messages. <domain type='xen'> <name>rstest_domain</name> <uuid>c1c33282-ffed-4092-85b3-85a3404f7f1a</uuid> <os> <type>hvm</type> <loader>/usr/lib/xen/boot/hvmloader</loader> <boot dev='hd'/> </os> <currentMemory>262144</currentMemory> <memory>262144</memory> <vcpu>1</vcpu> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <features> <pae/> <acpi/> <apic/> </features> <clock offset='utc'/> <devices> * <disk type='file' device='disk'> <driver name='file'/> <source file='/tmp/default-kvm-dimage.2ND'/> <target dev='hda'/> </disk> <disk type='file' device='disk'> <driver name='file'/> <source file='/tmp/default-kvm-dimage.2ND'/> <target dev='xvdb'/> </disk>* <interface type='bridge'> <mac address='00:16:3e:5d:c7:9e'/> <source bridge='testbridge'/> <script path='vif-bridge'/> </interface> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='5900'/> </devices> </domain> If we see above we can find two disk information in the devices section, well the first disk information is valid and belongs to the rstest_domain which is created before modfications. But I am not sure of how the following disk information is getting added to the devices section. *<disk type='file' device='disk'> <driver name='file'/> <source file='/tmp/default-kvm-dimage.2ND'/> <target dev='xvdb'/> </disk>* I tried looking into if the previous test case added this info, but it did not seem like. I tried to give some delay before and after the ModifyResourceSetting() call, to see it is caching issue, but it did not help either. Can you help to go about this problem? Thanks and Regards, Deepti.