From: Fabiano Rosas <farosas@suse.de>
To: Fiona Ebner <f.ebner@proxmox.com>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, wangyanan55@huawei.com,
philmd@linaro.org, marcel.apfelbaum@gmail.com,
eduardo@habkost.net, jasowang@redhat.com,
yuri.benditovich@daynix.com, andrew@daynix.com,
peterx@redhat.com, t.lamprecht@proxmox.com
Subject: Re: [PATCH] hw/core/machine: move compatibility flags for VirtIO-net USO to machine 8.1
Date: Mon, 20 May 2024 19:22:57 -0300 [thread overview]
Message-ID: <87h6esjf7i.fsf@suse.de> (raw)
In-Reply-To: <20240517075336.104091-1-f.ebner@proxmox.com>
Fiona Ebner <f.ebner@proxmox.com> writes:
> Migration from an 8.2 or 9.0 binary to an 8.1 binary with machine
> version 8.1 can fail with:
>
>> kvm: Features 0x1c0010130afffa7 unsupported. Allowed features: 0x10179bfffe7
>> kvm: Failed to load virtio-net:virtio
>> kvm: error while loading state for instance 0x0 of device '0000:00:12.0/virtio-net'
>> kvm: load of migration failed: Operation not permitted
>
> The series
>
> 53da8b5a99 virtio-net: Add support for USO features
> 9da1684954 virtio-net: Add USO flags to vhost support.
> f03e0cf63b tap: Add check for USO features
> 2ab0ec3121 tap: Add USO support to tap device.
>
> only landed in QEMU 8.2, so the compatibility flags should be part of
> machine version 8.1.
>
> Moving the flags unfortunately breaks forward migration with machine
> version 8.1 from a binary without this patch to a binary with this
> patch.
>
> Fixes: 53da8b5a99 ("virtio-net: Add support for USO features")
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
I'll get to it eventually, but is this another one where just having
-device virtio-net in the command line when testing cross-version
migration would already have caught the issue?
next prev parent reply other threads:[~2024-05-20 22:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 7:53 [PATCH] hw/core/machine: move compatibility flags for VirtIO-net USO to machine 8.1 Fiona Ebner
2024-05-20 22:22 ` Fabiano Rosas [this message]
2024-05-21 2:49 ` Jason Wang
2024-05-21 10:22 ` Fiona Ebner
2024-05-21 13:00 ` Fabiano Rosas
2024-05-21 2:12 ` Jason Wang
2024-05-21 22:23 ` Peter Xu
2024-05-22 22:02 ` Fabiano Rosas
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=87h6esjf7i.fsf@suse.de \
--to=farosas@suse.de \
--cc=andrew@daynix.com \
--cc=eduardo@habkost.net \
--cc=f.ebner@proxmox.com \
--cc=jasowang@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=t.lamprecht@proxmox.com \
--cc=wangyanan55@huawei.com \
--cc=yuri.benditovich@daynix.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).