diff options
author | Stefano Garzarella <sgarzare@redhat.com> | 2020-09-21 14:25:05 +0200 |
---|---|---|
committer | Michael S. Tsirkin <mst@redhat.com> | 2020-09-29 02:15:24 -0400 |
commit | 27eda699f59d430c33fc054a36a17251992e70dc (patch) | |
tree | 48f6e90c5d8c192c75e806827d3b61d98beff7dd /fsdev | |
parent | 6209070503989cf4f28549f228989419d4f0b236 (diff) | |
download | qemu-27eda699f59d430c33fc054a36a17251992e70dc.zip qemu-27eda699f59d430c33fc054a36a17251992e70dc.tar.gz qemu-27eda699f59d430c33fc054a36a17251992e70dc.tar.bz2 |
vhost-user-vsock-pci: force virtio version 1
Commit 9b3a35ec82 ("virtio: verify that legacy support is not
accidentally on") added a safety check that requires to set
'disable-legacy=on' on vhost-user-vsock-pci device:
$ ./qemu-system-x86_64 ... \
-chardev socket,id=char0,reconnect=0,path=/tmp/vhost4.socket \
-device vhost-user-vsock-pci,chardev=char0
qemu-system-x86_64: -device vhost-user-vsock-pci,chardev=char0:
device is modern-only, use disable-legacy=on
virtio-vsock was introduced after the release of VIRTIO 1.0
specifications, so it should be 'modern-only'.
This patch forces virtio version 1 and removes the 'transitional_name'
property, as done for vhost-vsock-pci, removing the need to specify
'disable-legacy=on' on vhost-user-vsock-pci device.
Cc: qemu-stable@nongnu.org
Suggested-by: Cornelia Huck <cohuck@redhat.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
Message-Id: <20200921122506.82515-4-sgarzare@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'fsdev')
0 files changed, 0 insertions, 0 deletions