From: Markus Frank <m.frank@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH common/qemu-server 0/2] vm start: catch outdated Zen 5 firmware
Date: Mon, 19 Jan 2026 17:36:31 +0100 [thread overview]
Message-ID: <657e1ed2-4f93-4974-8d4d-8fdedbee6d26@proxmox.com> (raw)
In-Reply-To: <20260119160122.177390-1-f.ebner@proxmox.com>
Hi,
On 2026-01-19 17:01, Fiona Ebner wrote:
> NOTE: Needs to still be tested on an actually affected system!
I tested both patches with the kernel 6.17.9 on my affected system (Ryzen 9 9900X, Gigabyte X870 AORUS ELITE WIFI7, Firmware-Version: F8).
Without the patches I get this error with kernel 6.17.9 when using CPU type 'EPYC':
kvm: warning: host doesn't support requested feature: CPUID[eax=07h,ecx=00h].EBX.rdseed [bit 18]
kvm: Host doesn't support requested features
TASK ERROR: start failed: QEMU exited with code 1
With the patches applied I get the same error with more context:
kvm: warning: host doesn't support requested feature: CPUID[eax=07h,ecx=00h].EBX.rdseed [bit 18]
WARN: On Zen 5 systems, the rdseed CPU flag might not be available when the CPU firmware is outdated. See:
https://security-tracker.debian.org/tracker/CVE-2025-62626
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_firmware_cpu
kvm: Host doesn't support requested features
TASK ERROR: start failed: QEMU exited with code 1
Tested-by: Markus Frank <m.frank@proxmox.com>
>
> With the 6.17.9 kernel, the rdseed feature bit is not available for
> some Zen 5 host CPUs anymore unless the firmware is new enough. QEMU
> will complain about the missing feature bit upon VM start. Add some
> context to the QEMU error message if the host is Zen 5 (or 6, same CPU
> family number, but the warning message already states 'Zen 5'
> explicitly and probably the feature bit won't be missing in the first
> place).
>
> pve-common:
>
> Fiona Ebner (1):
> procfs tools: cpuinfo: also return CPU vendor and family
>
> src/PVE/ProcFSTools.pm | 6 ++++++
> 1 file changed, 6 insertions(+)
>
>
> qemu-server:
>
> Fiona Ebner (1):
> vm start: catch outdated Zen 5 firmware
>
> src/PVE/QemuServer.pm | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
>
> Summary over all repositories:
> 2 files changed, 19 insertions(+), 0 deletions(-)
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2026-01-19 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 16:01 Fiona Ebner
2026-01-19 16:01 ` [pve-devel] [PATCH common 1/2] procfs tools: cpuinfo: also return CPU vendor and family Fiona Ebner
2026-01-19 16:01 ` [pve-devel] [PATCH qemu-server 2/2] vm start: catch outdated Zen 5 firmware Fiona Ebner
2026-01-20 16:54 ` [pve-devel] applied: " Thomas Lamprecht
2026-01-19 16:36 ` Markus Frank [this message]
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=657e1ed2-4f93-4974-8d4d-8fdedbee6d26@proxmox.com \
--to=m.frank@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.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