-
Stefano Garzarella authored
Commit 9b3a35ec ("virtio: verify that legacy support is not accidentally on") added a check that returns an error if legacy support is on, but the device does not support legacy. Unfortunately some devices were wrongly declared legacy capable even if they were not (e.g vhost-vsock). To avoid migration issues, we add a virtio-device property (x-disable-legacy-check) to skip the legacy error, printing a warning instead, for machine types < 5.1. Cc: qemu-stable@nongnu.org Fixes: 9b3a35ec ("virtio: verify that legacy support is not accidentally on") Suggested-by:
Dr. David Alan Gilbert <dgilbert@redhat.com>
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-2-sgarzare@redhat.com>
Reviewed-by:
Michael S. Tsirkin <mst@redhat.com>
Signed-off-by:
Michael S. Tsirkin <mst@redhat.com>Stefano Garzarella authoredCommit 9b3a35ec ("virtio: verify that legacy support is not accidentally on") added a check that returns an error if legacy support is on, but the device does not support legacy. Unfortunately some devices were wrongly declared legacy capable even if they were not (e.g vhost-vsock). To avoid migration issues, we add a virtio-device property (x-disable-legacy-check) to skip the legacy error, printing a warning instead, for machine types < 5.1. Cc: qemu-stable@nongnu.org Fixes: 9b3a35ec ("virtio: verify that legacy support is not accidentally on") Suggested-by:
Dr. David Alan Gilbert <dgilbert@redhat.com>
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-2-sgarzare@redhat.com>
Reviewed-by:
Michael S. Tsirkin <mst@redhat.com>
Signed-off-by:
Michael S. Tsirkin <mst@redhat.com>
Loading