libvirt/tests/qemuxml2argvdata/pseries-many-buses-1.xml

<domain type='qemu'>
  <name>guest</name>
  <uuid>1ccfd97d-5eb4-478a-bbe6-88d254c16db7</uuid>
  <memory unit='KiB'>524288</memory>
  <vcpu placement='static'>1</vcpu>
  <os>
    <type arch='ppc64' machine='pseries'>hvm</type>
  </os>
  <devices>
    <emulator>/usr/bin/qemu-system-ppc64</emulator>
    <!-- The SCSI controller is plugged into PCI bus 1, but since said bus
         is not present in the configuration libvirt will have to add it -->
    <controller type='scsi' model='virtio-scsi'>
      <address type='pci' bus='1' slot='1'/>
    </controller>
    <controller type='usb' model='none'/>
    <memballoon model='none'/>
  </devices>
</domain>
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>`
			`<vcpu placement='static'>1</vcpu>`
			`<os>`
			`<type arch='ppc64' machine='pseries'>hvm</type>`
			`</os>`
			`<devices>`
			`<emulator>/usr/bin/qemu-system-ppc64</emulator>`
			`<!-- The SCSI controller is plugged into PCI bus 1, but since said bus`
			`is not present in the configuration libvirt will have to add it -->`
			`<controller type='scsi' model='virtio-scsi'>`
			`<address type='pci' bus='1' slot='1'/>`
			`</controller>`
			`<controller type='usb' model='none'/>`
			`<memballoon model='none'/>`
			`</devices>`
			`</domain>`