From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server] cpu config: nested-virt: always recommend a CPU model similar to the host
Date: Wed, 19 Nov 2025 12:23:50 +0100 [thread overview]
Message-ID: <176355142775.2620253.16565668942222866938.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251119100144.33035-1-f.ebner@proxmox.com>
On Wed, 19 Nov 2025 10:59:58 +0100, Fiona Ebner wrote:
> Not only for Windows, nested virtualization with just x86-64-v2-AES
> and the nested-virt flag does not work on Linux either. While
> virtualization support is detected, actually starting a nested VM with
> such a configuration fails. For example, a Proxmox VE/PBS file-restore
> VM on my test system fails with the following (adding the apic and
> x2apic flags on top wouldn't make a difference):
>
> [...]
Applied, thanks!
[1/1] cpu config: nested-virt: always recommend a CPU model similar to the host
commit: 0fd8eb7db092087c6b0b17cbbcaab880276f60c1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-11-19 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 9:59 Fiona Ebner
2025-11-19 11:23 ` Thomas Lamprecht [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=176355142775.2620253.16565668942222866938.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