From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: applied: [PATCH-SERIES qemu-server 0/4] cpu config: warn that OVMF might limit phys-bits to 40 without pdpe1gb CPU flag
Date: Tue, 31 Mar 2026 21:01:53 +0200 [thread overview]
Message-ID: <177498371111.272063.5388240658816297313.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260323132857.125747-1-f.ebner@proxmox.com>
On Mon, 23 Mar 2026 14:27:20 +0100, Fiona Ebner wrote:
> OVMF limits phys-bits to 40 if no 1 GiB pages are available. When
> built in debug mode, OVMF logs a debug message about this. But
> otherwise, there is no user-visible log of this happening.
>
> In practice, VMs with a lot of memory or VMs with GPU passthrough with
> a lot of vRAM might not boot when the pdpe1gb CPU flag is not present.
> In particular, this is the case for the built-in x86-64-vX models that
> are based on the qemu64 model as well as the backend default kvm64.
>
> [...]
Applied, thanks!
[1/4] cpu config: split resolve_cpu_flags() function
commit: 59f28b13b36a24af2144f22a4cf2c7eb1baf0b2c
[2/4] move get_host_phys_address_bits() to helpers module
commit: ec595ea63650e3adc8ca4547d19039bdd32b4701
[3/4] cpu config: get cpu options: avoid shadowing $conf variable
commit: ce41ec1fb92e5f42b3ba38c4077d5d33ef37f42e
[4/4] cpu config: warn that OVMF might limit phys-bits to 40 without pdpe1gb CPU flag
commit: 980ee163e67c8b3aae16bd6e6dbb4e1e13d59eba
prev parent reply other threads:[~2026-03-31 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 13:27 Fiona Ebner
2026-03-23 13:27 ` [PATCH qemu-server 1/4] cpu config: split resolve_cpu_flags() function Fiona Ebner
2026-03-23 13:27 ` [PATCH qemu-server 2/4] move get_host_phys_address_bits() to helpers module Fiona Ebner
2026-03-23 13:27 ` [PATCH qemu-server 3/4] cpu config: get cpu options: avoid shadowing $conf variable Fiona Ebner
2026-03-23 13:27 ` [PATCH qemu-server 4/4] cpu config: warn that OVMF might limit phys-bits to 40 without pdpe1gb CPU flag Fiona Ebner
2026-03-31 19:01 ` 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=177498371111.272063.5388240658816297313.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