all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH common/qemu-server 0/2] vm start: catch outdated Zen 5 firmware
Date: Mon, 19 Jan 2026 17:01:02 +0100	[thread overview]
Message-ID: <20260119160122.177390-1-f.ebner@proxmox.com> (raw)

NOTE: Needs to still be tested on an actually affected system!

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(-)

-- 
Generated by git-murpp 0.5.0


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


             reply	other threads:[~2026-01-19 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 16:01 Fiona Ebner [this message]
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-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=20260119160122.177390-1-f.ebner@proxmox.com \
    --to=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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal