From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server 2/2] vm start: catch outdated Zen 5 firmware
Date: Tue, 20 Jan 2026 17:54:20 +0100 [thread overview]
Message-ID: <176892804962.1468922.15321758308438836352.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260119160122.177390-3-f.ebner@proxmox.com>
On Mon, 19 Jan 2026 17:01:04 +0100, Fiona Ebner wrote:
> With the 6.17.9 kernel, the 'rdseed' feature 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).
>
> [...]
Applied, thanks!
[2/2] vm start: catch outdated Zen 5 firmware
commit: cde8891799a8c408a4b8f845197a0d1caeaebfe4
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2026-01-20 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 16:01 [pve-devel] [PATCH common/qemu-server 0/2] " 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 ` Thomas Lamprecht [this message]
2026-01-19 16:36 ` [pve-devel] [PATCH common/qemu-server 0/2] " Markus Frank
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=176892804962.1468922.15321758308438836352.b4-ty@proxmox.com \
--to=t.lamprecht@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