virt-manager/tests/data/cli/compare/virt-install-ppc64-machdefault-f20.xml

<domain type="qemu">
  <name>fedora20-ppc64</name>
  <uuid>00000000-1111-2222-3333-444444444444</uuid>
  <metadata>
    <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
      <libosinfo:os id="http://fedoraproject.org/fedora/20"/>
    </libosinfo:libosinfo>
  </metadata>
  <memory>65536</memory>
  <currentMemory>65536</currentMemory>
  <vcpu>2</vcpu>
  <os>
    <type arch="ppc64" machine="pseries">hvm</type>
    <boot dev="network"/>
  </os>
  <clock offset="utc"/>
  <devices>
    <emulator>/usr/bin/qemu-system-ppc64</emulator>
    <disk type="file" device="disk">
      <driver name="qemu" type="qcow2"/>
      <source file="/pool-dir/testvol1.img"/>
      <target dev="vda" bus="virtio"/>
    </disk>
    <controller type="usb" model="qemu-xhci" ports="15"/>
    <console type="pty"/>
    <channel type="unix">
      <source mode="bind"/>
      <target type="virtio" name="org.qemu.guest_agent.0"/>
    </channel>
    <input type="tablet" bus="usb"/>
    <input type="keyboard" bus="usb"/>
    <graphics type="vnc" port="-1"/>
    <video>
      <model type="vga"/>
    </video>
    <memballoon model="virtio"/>
    <rng model="virtio">
      <backend model="random">/dev/urandom</backend>
    </rng>
  </devices>
</domain>
Use -M virt as default machine for arm/aarch64 Centralize the default machine logic in caps and use it consistently 2014-09-24 00:05:48 +04:00			`<domain type="qemu">`
virt-install: Generate default --name This uses the same logic as virt-manager. The name is mostly derived from --os-variant naming, but we have fallback defaults too. Print the name to stdout so users are informed about what we are doing. 2019-06-11 18:54:02 +03:00			`<name>fedora20-ppc64</name>`
Use -M virt as default machine for arm/aarch64 Centralize the default machine logic in caps and use it consistently 2014-09-24 00:05:48 +04:00			`<uuid>00000000-1111-2222-3333-444444444444</uuid>`
guest: Encode the cli --os-variant in the XML And add some testdriver examples of it 2018-09-13 22:11:22 +03:00			`<metadata>`
			`<libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">`
			`<libosinfo:os id="http://fedoraproject.org/fedora/20"/>`
			`</libosinfo:libosinfo>`
			`</metadata>`
Use -M virt as default machine for arm/aarch64 Centralize the default machine logic in caps and use it consistently 2014-09-24 00:05:48 +04:00			`<memory>65536</memory>`
			`<currentMemory>65536</currentMemory>`
osdict: Don't limit qemu TCG to vcpus=1 Modern qemu has multithread TCG support for all the arches we support, so don't limit things 2019-05-11 23:50:52 +03:00			`<vcpu>2</vcpu>`
Use -M virt as default machine for arm/aarch64 Centralize the default machine logic in caps and use it consistently 2014-09-24 00:05:48 +04:00			`<os>`
			`<type arch="ppc64" machine="pseries">hvm</type>`
			`<boot dev="network"/>`
			`</os>`
			`<clock offset="utc"/>`
			`<devices>`
			`<emulator>/usr/bin/qemu-system-ppc64</emulator>`
			`<disk type="file" device="disk">`
			`<driver name="qemu" type="qcow2"/>`
tests: testdriver: Rename default-pool -> pool-dir And move the path to not be rooted in /dev, which doesn't make sense for a directory pool, and triggers some special /dev handling in virtinst that we don't want in the common testing path. Signed-off-by: Cole Robinson <crobinso@redhat.com> 2022-02-27 21:00:56 +03:00			`<source file="/pool-dir/testvol1.img"/>`
virtinst: Use virtio bus type for disks on pSeries machines pSeries doesn't support ide and so was changed to use the scsi. virtio works better on pSeries with better performance outcomes. Change the default to virtio for disks Signed-off-by: Shivaprasad G Bhat <sbhat@linux.vnet.ibm.com> 2016-04-21 11:00:34 +03:00			`<target dev="vda" bus="virtio"/>`
Use -M virt as default machine for arm/aarch64 Centralize the default machine logic in caps and use it consistently 2014-09-24 00:05:48 +04:00			`</disk>`
controller: don't set default controller index Libvirt is able to figure this out and it will make usage of the CLI options more user-friendly. For example if users wants to add a new pcie-root-port to existing VM they have to figure out the latest controller index and call it like this: virt-xml \ --add-device \ --controller pci,model=pcie-root-port,index=$nextIndex \ $VM After this change it will be simply: virt-xml \ --add-device \ --controller pci,model=pcie-root-port \ $VM Signed-off-by: Pavel Hrdina <phrdina@redhat.com> Reviewed-by: Cole Robinson <crobinso@redhat.com> 2019-12-03 14:35:25 +03:00			`<controller type="usb" model="qemu-xhci" ports="15"/>`
Use -M virt as default machine for arm/aarch64 Centralize the default machine logic in caps and use it consistently 2014-09-24 00:05:48 +04:00			`<console type="pty"/>`
			`<channel type="unix">`
			`<source mode="bind"/>`
			`<target type="virtio" name="org.qemu.guest_agent.0"/>`
			`</channel>`
guest: Add USB input devices to pSeries guests with graphics libvirt already does this for us, sort of: it will automatically add a USB keyboard and mouse to ppc64 guests with graphics; in addition, these devices are impossible to remove. Unfortunately this results in a pretty poor experience for the user, since the relative pointing device makes interacting with the GUI an exercise in frustration. As of commit 186bb479d0f4, libvirt will still add the USB keyboard automatically but will skip the USB mouse if a USB tablet is already present, so by explicitly including USB input devices in the generated XML we can create guests that are actually usable. We can do this unconditionally, without having to worry about what version of libvirt we're running against: if it's new enough we'll take advantage of the fix, and if not then the resulting guest will not be any more broken than it would have been before. https://bugzilla.redhat.com/show_bug.cgi?id=1683609 Signed-off-by: Andrea Bolognani <abologna@redhat.com> 2019-03-20 18:52:33 +03:00			`<input type="tablet" bus="usb"/>`
			`<input type="keyboard" bus="usb"/>`
tests: consolidate some arch compare tests Signed-off-by: Cole Robinson <crobinso@redhat.com> 2022-02-20 19:28:22 +03:00			`<graphics type="vnc" port="-1"/>`
Use -M virt as default machine for arm/aarch64 Centralize the default machine logic in caps and use it consistently 2014-09-24 00:05:48 +04:00			`<video>`
			`<model type="vga"/>`
			`</video>`
guest: Add memory balloon by default libvirt already does this for pretty much all QEMU guests, but ARM virt guests for example don't get a memory balloon by default at that level of the stack. virt-manager is in a good position to make sure defaults are consistent across architectures, and there's no downside in having the device in the XML passed to libvirt anyway. Signed-off-by: Andrea Bolognani <abologna@redhat.com> 2019-06-13 13:55:10 +03:00			`<memballoon model="virtio"/>`
guest: Enable default virtio-rng for pseries and machvirt arm guys confirmed virtio-rng should be fine. pseries guys didn't but I think it will be okay 2017-06-28 22:11:05 +03:00			`<rng model="virtio">`
			`<backend model="random">/dev/urandom</backend>`
			`</rng>`
Use -M virt as default machine for arm/aarch64 Centralize the default machine logic in caps and use it consistently 2014-09-24 00:05:48 +04:00			`</devices>`
			`</domain>`