From: David Hildenbrand <david@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>, qemu-devel@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>, Qinghua Cheng <qcheng@redhat.com>,
Qian Cai <caiqian@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
qemu-stable@nongnu.org, Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH 0/3] vhost-vsock: force virtio version 1
Date: Wed, 19 Aug 2020 13:06:55 +0200 [thread overview]
Message-ID: <0b33b4b9-f1d1-759e-649d-899400b286c1@redhat.com> (raw)
In-Reply-To: <20200819105156.54163-1-sgarzare@redhat.com>
On 19.08.20 12:51, Stefano Garzarella wrote:
> Recenlty changes in QEMU 5.1 requires to set 'disable-legacy=3Don'
> on vhost-vsock-pci and vhost-user-vsock-pci devices:
>
> $ ./qemu-system-x86_64 ... -device vhost-vsock-pci,guest-cid=3D5
> qemu-system-x86_64: -device vhost-vsock-pci,guest-cid=3D5:
> device is modern-only, use disable-legacy=3Don
Something seemed to messed up your encoding (= vs. =3D). The patches
look fine, though. (did you copy and paste this from somewhere?)
>
> As discussed with Cornelia [1], this series force virtio version 1
> to vhost-vsock-pci, vhost-user-vsock-pci, and vhost-vsock-ccw devices.
>
> virtio-vsock was introduced after the release of VIRTIO 1.0 specifications,
> so it should be 'modern-only'.
> In addition Cornelia verified that forcing a legacy mode on vhost-vsock-pci
> device using x86-64 host and s390x guest, so with different endianness,
> produces strange behaviours.
>
> About migration, QEMU 5.1 already requires that the source and destination
> specify 'disable-legacy=3Don', otherwise the migration fails in this way:
> qemu-system-x86_64: get_pci_config_device: Bad config data: i=3D0x2 read:=
> 12 device: 53 cmask: ff wmask: 0 w1cmask:0
> qemu-system-x86_64: Failed to load PCIDevice:config
> qemu-system-x86_64: Failed to load virtio-vhost_vsock:virtio
> qemu-system-x86_64: error while loading state for instance 0x0 of device =
> '0000:00:03.0/virtio-vhost_vsock'
> qemu-system-x86_64: load of migration failed: Invalid argument
>
> With this series applied there is the same requirements. Alternatively
> we have to detach and re-attach the device manually.
>
> Thanks,
> Stefano
>
> [1] https://lists.nongnu.org/archive/html/qemu-devel/2020-08/msg02515.html
>
> Stefano Garzarella (3):
> vhost-vsock-pci: force virtio version 1
> vhost-user-vsock-pci: force virtio version 1
> vhost-vsock-ccw: force virtio version 1
>
> hw/s390x/vhost-vsock-ccw.c | 2 ++
> hw/virtio/vhost-user-vsock-pci.c | 2 +-
> hw/virtio/vhost-vsock-pci.c | 2 +-
> 3 files changed, 4 insertions(+), 2 deletions(-)
>
> --=20
^ also here
> 2.26.2
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-08-19 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 10:51 [PATCH 0/3] vhost-vsock: force virtio version 1 Stefano Garzarella
2020-08-19 10:51 ` [PATCH 1/3] vhost-vsock-pci: " Stefano Garzarella
2020-08-19 11:55 ` Cornelia Huck
2020-08-19 12:09 ` Stefano Garzarella
2020-08-19 12:28 ` Cornelia Huck
2020-08-19 10:51 ` [PATCH 2/3] vhost-user-vsock-pci: " Stefano Garzarella
2020-08-19 11:57 ` Cornelia Huck
2020-08-19 10:51 ` [PATCH 3/3] vhost-vsock-ccw: " Stefano Garzarella
2020-08-19 12:01 ` Cornelia Huck
2020-08-19 11:06 ` David Hildenbrand [this message]
2020-08-19 11:21 ` [PATCH 0/3] vhost-vsock: " Stefano Garzarella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0b33b4b9-f1d1-759e-649d-899400b286c1@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=caiqian@redhat.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qcheng@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=rth@twiddle.net \
--cc=sgarzare@redhat.com \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).