External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-11-05 04:41:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
4de5d01a4e
libvirt/tests/qemuxml2xmloutdata/pseries-many-devices.xml

126 lines
5.9 KiB
XML
Raw Normal View History

tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
<domain type='qemu'>
<name>guest</name>
<uuid>1ccfd97d-5eb4-478a-bbe6-88d254c16db7</uuid>
<memory unit='KiB'>524288</memory>
<currentMemory unit='KiB'>524288</currentMemory>
<vcpu placement='static'>1</vcpu>
<os>
<type arch='ppc64' machine='pseries'>hvm</type>
<boot dev='hd'/>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/bin/qemu-system-ppc64</emulator>
<controller type='scsi' index='0' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='1' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='2' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='3' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='4' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='5' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='6' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='7' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='8' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='9' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='10' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='11' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='12' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x0d' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='13' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x0e' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='14' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x0f' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='15' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x10' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='16' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x11' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='17' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x12' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='18' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x13' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='19' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x14' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='20' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x15' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='21' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x16' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='22' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x17' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='23' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x18' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='24' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x19' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='25' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x1a' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='26' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='27' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x1c' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='28' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x1d' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='29' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='30' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='scsi' index='31' model='virtio-scsi'>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<controller type='usb' index='0' model='none'/>
<controller type='pci' index='0' model='pci-root'>
<model name='spapr-pci-host-bridge'/>
<target index='0'/>
</controller>
qemu: Use PHBs when extending the guest PCI topology When looking for slots suitable for a PCI device, libvirt might need to add an extra PCI controller: for pSeries guests, we want that extra controller to be a PHB (pci-root) rather than a PCI bridge. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-29 15:18:35 +00:00
<controller type='pci' index='1' model='pci-root'>
<model name='spapr-pci-host-bridge'/>
<target index='1'/>
tests: Add baseline tests for automatic PHB usage These tests demonstrate that, while it's now possible for the user to create PHB explicitly and manually assign devices to them, libvirt still defaults to extending the guest PCI topology using PCI bridges and making suboptimal device placement choices. The next few commits will improve on these behaviors and the tests outputs will automatically be updated to reflect this. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org>
2017-05-26 16:33:36 +00:00
</controller>
<memballoon model='none'/>
<panic model='pseries'/>
</devices>
</domain>
Reference in New Issue Copy Permalink