From: Jonas Theisen <j.theisen@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [PATCH docs] qm: document potential host cpu type drawback
Date: Tue, 10 Nov 2026 15:21:39 +0100 [thread overview]
Message-ID: <3a03cfcb-8bd1-49f9-a066-ec698edcd71a@proxmox.com> (raw)
In-Reply-To: <20260715130131.397579-1-m.sandoval@proxmox.com>
On 7/15/26 15:01, Maximiliano Sandoval wrote:
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
>
> Notes:
> This happened for example on Kernel 7.0.0 where the vmx-mbec is now enabled.
>
> qm.adoc | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/qm.adoc b/qm.adoc
> index 96ba68b..bca5792 100644
> --- a/qm.adoc
> +++ b/qm.adoc
> @@ -482,6 +482,10 @@ cluster, choose the lowest compatible virtual QEMU CPU type.
>
> NOTE: Live migrations between Intel and AMD host CPUs have no guarantee to work.
>
> +WARNING: The 'host' CPU type can potentially enable new CPU features for the
> +guest when the guest is restarted after a system upgrade. This can result in
> +unexpected consequences.
> +
> See also
> xref:chapter_qm_vcpu_list[List of AMD and Intel CPU Types as Defined in QEMU].
>
Gentle ping.
I personally would like to see this mentioned in the docs, since this
is and will stay a potential problem / hazard to be aware of with
this CPU type.
So consider this:
Reviewed-by: Jonas Theisen <j.theisen@proxmox.com>
prev parent reply other threads:[~2026-11-10 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 13:01 [PATCH docs] qm: document potential host cpu type drawback Maximiliano Sandoval
2026-11-10 14:21 ` Jonas Theisen [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=3a03cfcb-8bd1-49f9-a066-ec698edcd71a@proxmox.com \
--to=j.theisen@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