]> git.ipfire.org Git - thirdparty/libvirt.git/commit
qemu: Use virtio-pci by default for mach-virt guests
authorAndrea Bolognani <abologna@redhat.com>
Fri, 21 Oct 2016 09:50:15 +0000 (11:50 +0200)
committerAndrea Bolognani <abologna@redhat.com>
Tue, 10 Jan 2017 11:33:53 +0000 (12:33 +0100)
commit1d8454639f40dea25bfa42d5cece65bf25e6ef49
treecf18559f582c44b94638c4102d0c1aed50ff1ced
parenta946ea1a334f601bfa0ad4402113544546948de1
qemu: Use virtio-pci by default for mach-virt guests

virtio-pci is the way forward for aarch64 guests: it's faster
and less alien to people coming from other architectures.
Now that guest support is finally getting there (Fedora 24,
CentOS 7.3, Ubuntu 16.04 and Debian testing all support
virtio-pci out of the box), we'd like to start using it by
default instead of virtio-mmio.

Users and applications can already opt-in by explicitly using

  <address type='pci'/>

inside the relevant elements, but that's kind of cumbersome and
requires all users and management applications to adapt, which
we'd really like to avoid.

What we can do instead is use virtio-mmio only if the guest
already has at least one virtio-mmio device, and use virtio-pci
in all other situations.

That means existing virtio-mmio guests will keep using the old
addressing scheme, and new guests will automatically be created
using virtio-pci instead. Users can still override the default
in either direction.

Existing tests such as aarch64-aavmf-virtio-mmio and
aarch64-virtio-pci-default already cover all possible
scenarios, so no additions to the test suites are necessary.
src/qemu/qemu_domain_address.c
tests/qemuxml2argvdata/qemuxml2argv-aarch64-virt-2.6-virtio-pci-default.args
tests/qemuxml2argvdata/qemuxml2argv-aarch64-virtio-pci-default.args
tests/qemuxml2argvdata/qemuxml2argv-aarch64-virtio-pci-default.xml
tests/qemuxml2argvtest.c
tests/qemuxml2xmloutdata/qemuxml2xmlout-aarch64-virtio-pci-default.xml
tests/qemuxml2xmltest.c