shaba/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-26 03:21:44 +03:00
Code Releases Activity
6ff69e936e
libvirt/tests/qemuxml2argvdata/pci-bridge.xml

179 lines
5.3 KiB
XML
Raw Normal View History

qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<domain type='qemu'>
<name>fdr-br</name>
<uuid>3ec6cbe1-b5a2-4515-b800-31a61855df41</uuid>
<memory unit='KiB'>2097152</memory>
<currentMemory unit='KiB'>2097152</currentMemory>
<vcpu placement='static' cpuset='0-1'>2</vcpu>
<os>
<type arch='x86_64' machine='pc-1.2'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
tests: unify qemu binary paths for all qemu related tests Our test data used a lot of different qemu binary paths and some of them were based on downstream systems. Note that there is one file where I had to add "accel=kvm" because the qemuargv2xml code parses "/usr/bin/kvm" as virt type="kvm". Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2017-04-06 19:19:48 +03:00
<emulator>/usr/bin/qemu-system-x86_64</emulator>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/var/iso/f18kde.iso'/>
<target dev='hdc' bus='ide'/>
<readonly/>
<address type='drive' controller='0' bus='1' target='0' unit='0'/>
</disk>
<controller type='usb' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<controller type='ide' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
</controller>
<controller type='pci' index='0' model='pci-root'/>
<controller type='pci' index='1' model='pci-bridge'/>
<controller type='pci' index='2' model='pci-bridge'/>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:f1:95:51'/>
<model type='rtl8139'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:5c:c6:1a'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:39:97:ac'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:45:28:cb'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:ee:b9:a8'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:a9:f7:17'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:df:2b:f3'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:78:94:b4'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:6b:9b:06'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:17:df:bc'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:3b:d0:51'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:8d:2d:17'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:a7:66:af'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:54:ab:d7'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:1f:99:90'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:c8:43:87'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:df:22:b2'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:d2:9a:47'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:86:05:e2'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:8c:1c:c2'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:48:58:92'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:99:e5:bf'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:b1:8c:25'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:60:e0:d0'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:37:00:6a'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:c7:c8:ad'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:4e:a7:cf'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:00:79:69'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:47:00:6f'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:2a:8c:8b'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:ec:d5:e3'/>
<model type='e1000'/>
</interface>
tests: Sync tests between qemuxml2argv and qemuxml2xml In some cases, only one of the two transformations was checked; in other cases, the capabilities set differed.
2017-02-23 20:47:36 +03:00
<interface type='user'>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<mac address='52:54:00:7e:6e:c8'/>
<model type='e1000'/>
</interface>
<input type='mouse' bus='ps2'/>
conf: Add keyboard input device type There is no keyboard support currently in libvirt. For some platforms (PPC64 QEMU) this makes graphics unusable, since the keyboard is not implicit and it can't be added via libvirt. Signed-off-by: Li Zhang <zhlcindy@linux.vnet.ibm.com> Signed-off-by: Ján Tomko <jtomko@redhat.com>
2014-02-17 14:17:53 +04:00
<input type='keyboard' bus='ps2'/>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<graphics type='vnc' port='-1' autoport='yes' listen='127.0.0.1' keymap='en-us'>
<listen type='address' address='127.0.0.1'/>
</graphics>
<video>
video: cleanup usage of vram attribute and update documentation The vram attribute was introduced to set the video memory but it is usable only for few hypervisors excluding QEMU/KVM and the old XEN driver. Only in case of QEMU the vram was used for QXL. This patch updates the documentation to reflect current code in libvirt and also changes the cases when we will set the default vram attribute. It also fixes existing strange default value for VGA devices 9MB to 16MB because the video ram should be rounded to power of two. The change of default value could affect migrations but I found out that QEMU always round the video ram to power of two internally so it's safe to change the default value to the next closest power of two and also silently correct every domain XML definition. And it's also safe because we don't pass the value to QEMU. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1076098 Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2014-11-24 13:58:53 +03:00
<model type='cirrus' vram='16384' heads='1'/>
qemu: auto-add bridges and allow using them Add a "dry run" address allocation to figure out how many bridges will be needed for all the devices without explicit addresses. Auto-add just enough bridges to put all the devices on, or up to the bridge with the largest specified index.
2013-04-19 14:38:53 +04:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</memballoon>
</devices>
</domain>
Copy Permalink