From: "Denis V. Lunev" <den@openvz.org>
To: svt-core@virtuozzo.com
Cc: andrey.drobyshev@virtuozzo.com, "Denis V. Lunev" <den@openvz.org>
Subject: [PATCH hci-8.0/8.1 0/1] i386: fix 7.4 -> 8.0 migration of AMD guests without svm #VSTOR-154398
Date: Wed, 11 Nov 2026 12:19:15 +0100 [thread overview]
Message-ID: <20261111111917.4012602-1-den@openvz.org> (raw)
hci-upgrade 7.4.0 -> 8.0.0 cannot evacuate a single node with AMD
guests: the 8.0 libvirt refuses every incoming EPYC-type guest with
guest CPU doesn't match specification: extra features: npt,nrip-save
The cause is x-svm-features-compat (e51cdbf863d on hci-8.0, 02f55118bcb
on hci-8.1). It keeps all SVM leaf bits of the CPU model when svm is
off, while QEMU 8.2 on 7.4 drops them. The patch keeps only the bits
given explicitly on the command line, which is all the Vz7 host-model
guests the compat was written for need. It applies to hci-8.1 as is;
there the Fixes: tag should name 02f55118bcb.
QEMU alone is not enough for hci-8.0. Guests started on the stock
8.0.0 QEMU already carry the model defaults in their live libvirt
definition and keep it across virsh qemu-update, so the 8.0 hotfix
also needs the libvirt side, which writes every SVM leaf feature as
disabled in the migration cookie of a guest without svm:
https://bitbucket.org/openvz/libvirt.ovz/pull-requests/398
Both must go into the same 8.0 hotfix, and the hotfix must be installed
before a node is upgraded to 8.1. hci-8.1 needs only this patch.
Tested on a nested cluster built from the product images (VHS 7.5.7,
HCI 7.4.0, 8.0.0, 8.1.0) on real Zen 3 and Zen 5 and emulated Zen 1-4
hosts, with this QEMU and the libvirt PR installed on the 8.0 nodes as
a hotfix over guests started on the stock 8.0 and moved by virsh
qemu-update: named EPYC models, host-model and host-passthrough guests,
machine types vz7.16 to vz10.1, every pair of VHS 7 / 7.4 / 8.0 / 8.1
in both directions. 4498 migrations and 1260 qemu-update runs passed
with no unexpected guest-visible CPU change. What still fails is
outside this fix: 7.4 libvirtd crashes on an incoming vz7
host-passthrough guest (VSTOR-152247, fixed on 8.0 only), and 7.4 ->
stock 8.0 itself. Full RCA and transition matrices are in VSTOR-154398:
https://virtuozzo.atlassian.net/browse/VSTOR-154398
Denis V. Lunev (1):
i386: keep only requested SVM leaf features in x-svm-features-compat
#VSTOR-154398
target/i386/cpu.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
base-commit: 9b6f7670e2712c041867b585a618bd8c3778fdad
--
2.53.0
next reply other threads:[~2026-11-11 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 11:19 Denis V. Lunev [this message]
2026-11-11 11:19 ` [PATCH hci-8.0/8.1 1/1] i386: keep only requested SVM leaf features in x-svm-features-compat #VSTOR-154398 Denis V. Lunev
2026-11-11 14:26 ` Andrey Drobyshev
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=20261111111917.4012602-1-den@openvz.org \
--to=den@openvz.org \
--cc=andrey.drobyshev@virtuozzo.com \
--cc=svt-core@virtuozzo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.