Re: [libvirt] [PATCH RFC 0/8] qemu: allow disabling certain virtio revisions

2016-08-04 Thread Laine Stump
On 08/04/2016 11:11 AM, Andrea Bolognani wrote: On Mon, 2016-08-01 at 10:02 -0400, Laine Stump wrote: 2) To assure that the actual device presented to the guest doesn't change in the future when defaults are changed, we may want to autofill "version" even when none is specified. (We would of

Re: [libvirt] [PATCH RFC 0/8] qemu: allow disabling certain virtio revisions

2016-08-04 Thread Andrea Bolognani
On Mon, 2016-08-01 at 10:02 -0400, Laine Stump wrote: > 2) To assure that the actual device presented to the guest doesn't > change in the future when defaults are changed, we may want to autofill > "version" even when none is specified. (We would of course be stuck with > the unfortunate problem

Re: [libvirt] [PATCH RFC 0/8] qemu: allow disabling certain virtio revisions

2016-08-01 Thread Laine Stump
On 07/29/2016 09:37 AM, Ján Tomko wrote: For https://bugzilla.redhat.com/show_bug.cgi?id=1227354 some users might want to adjust the QEMU defaults and disable either virtio 0.9 or virtio 1.0 (spelled out as disable-legacy and disable-modern on qemu command line). This series uses a separate

[libvirt] [PATCH RFC 0/8] qemu: allow disabling certain virtio revisions

2016-07-29 Thread Ján Tomko
For https://bugzilla.redhat.com/show_bug.cgi?id=1227354 some users might want to adjust the QEMU defaults and disable either virtio 0.9 or virtio 1.0 (spelled out as disable-legacy and disable-modern on qemu command line). This series uses a separate element right under the relevant device