Kaitlin Rupert wrote:
>> VirtualSystemManagementService - 06_addresource.py: FAIL
> <domain type='kvm'>
> <uuid>e9bc806e-1c65-11dd-b5f9-001a646394d4</uuid>
> <name>rstest_domain</name>
> <on_poweroff>destroy</on_poweroff>
> <on_crash>destroy</on_crash>
> <os>
> <type>hvm</type>
> <boot dev='hd'/>
> </os>
> <currentMemory>131072</currentMemory>
> <memory>131072</memory>
> <vcpu>1</vcpu><devices>
> <interface type='bridge'>
> <mac address='11:22:33:aa:bb:cc'/>
> <script path='vif-bridge'/>
> </interface>
> <disk type='file' device='disk'>
> <source file='/tmp/default-kvm-dimage'/>
> <target dev='hda'/>
> </disk>
> </devices>
> </domain>
>
> misc_util.c(72): Connecting to libvirt with uri `qemu:///system'
> libvir: QEMU error : internal error No <source> 'dev' attribute
> specified with <interface type='bridge'/>
> Virt_VirtualSystemManagementService.c(595): Failed to define domain
> from XML
> std_invokemethod.c(305): Method `AddResourceSettings' returned 1
>
> The tc Failed to create the domain bcs of the missing <source
> bridge='testbridge'/> tag in the xml.
> With the <source bridge='testbridge'/> in the xml file we can create
> the kvm guest successfully.
Can you check to see if this needs to be fixed in xvml.py.
The test case support
the KVM guest to be created with bridge type
interface by default, but the provider code does not support KVM with
for bridge and supports only network interface type.
Hence this problem. I can modify the vxml.py to use network type by
default for KVM.
>
>> VirtualSystemSettingDataComponent - 04_vssdc_rev_errs.py
> Segmentation fault.
>>