From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Jiang Wang <jiang.wang@bytedance.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-stable@nongnu.org, qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@redhat.com>,
Arseny Krasnov <arseny.krasnov@kaspersky.com>
Subject: Re: [PATCH] vhost-vsock: fix migration issue when seqpacket is supported
Date: Tue, 7 Sep 2021 14:22:24 +0100 [thread overview]
Message-ID: <YTdnkPR+LjNFXaeQ@redhat.com> (raw)
In-Reply-To: <20210907124935.147164-1-sgarzare@redhat.com>
On Tue, Sep 07, 2021 at 02:49:35PM +0200, Stefano Garzarella wrote:
> Commit 1e08fd0a46 ("vhost-vsock: SOCK_SEQPACKET feature bit support")
> enabled the SEQPACKET feature bit.
> This commit is released with QEMU 6.1, so if we try to migrate a VM where
> the host kernel supports SEQPACKET but machine type version is less than
> 6.1, we get the following errors:
>
> Features 0x130000002 unsupported. Allowed features: 0x179000000
> Failed to load virtio-vhost_vsock:virtio
> error while loading state for instance 0x0 of device '0000:00:05.0/virtio-vhost_vsock'
> load of migration failed: Operation not permitted
>
> Let's disable the feature bit for machine types < 6.1, adding a
> `features` field to VHostVSock to simplify the handling of upcoming
> features we will support.
IIUC, this will still leave migration broken for anyone migrating
a >= 6.1 machine type between a kernel that supports SEQPACKET and
a kernel lacking that, or vica-verca.
If a feature is dependant on a host kernel feature we can't turn
that on automatically as part of the machine type, as we need
ABI stability across migration indepdant of kernel version.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-09-07 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 12:49 [PATCH] vhost-vsock: fix migration issue when seqpacket is supported Stefano Garzarella
2021-09-07 13:22 ` Daniel P. Berrangé [this message]
2021-09-07 13:47 ` Stefano Garzarella
2021-09-08 13:41 ` Stefano Garzarella
2021-09-08 13:48 ` Daniel P. Berrangé
2021-09-09 8:47 ` Michael S. Tsirkin
2021-09-09 9:02 ` Daniel P. Berrangé
2021-09-10 6:35 ` Michael S. Tsirkin
2021-09-13 12:51 ` Stefano Garzarella
2021-09-13 13:46 ` Michael S. Tsirkin
2021-09-14 10:42 ` Stefano Garzarella
2021-09-14 11:49 ` Michael S. Tsirkin
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=YTdnkPR+LjNFXaeQ@redhat.com \
--to=berrange@redhat.com \
--cc=arseny.krasnov@kaspersky.com \
--cc=ehabkost@redhat.com \
--cc=jiang.wang@bytedance.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@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).