From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH qemu-server 1/2] start vm: check efi vars: clarify when to run the commands for BitLocker
Date: Wed, 18 Mar 2026 10:32:58 +0100 [thread overview]
Message-ID: <20260318093307.31645-2-f.ebner@proxmox.com> (raw)
In-Reply-To: <20260318093307.31645-1-f.ebner@proxmox.com>
In the UI and in the docs, it is already mentioned that disabling the
protectors needs to happen before enrollment. Also mention it for the
informational message during VM start.
Suggested-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
src/PVE/QemuServer.pm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/PVE/QemuServer.pm b/src/PVE/QemuServer.pm
index 09e7a19b..33be0b36 100644
--- a/src/PVE/QemuServer.pm
+++ b/src/PVE/QemuServer.pm
@@ -5416,6 +5416,8 @@ my sub check_efi_vars {
print "For Windows with BitLocker, run the following command inside Powershell:\n";
print " manage-bde -protectors -disable <drive>\n";
print "for each drive with BitLocker (for example, <drive> could be 'C:').\n";
+ print "This is required for each drive with BitLocker before proceeding with enrollment.\n";
+ print "Otherwise, you will be prompted for the BitLocker recovery key on the next boot.\n";
}
return;
--
2.47.3
next prev parent reply other threads:[~2026-03-18 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 9:32 [PATCH-SERIES qemu-server/docs 0/2] efi enroll: small improvements to documentation Fiona Ebner
2026-03-18 9:32 ` Fiona Ebner [this message]
2026-03-18 9:32 ` [PATCH docs 2/2] qm: bios/uefi: certificate expiration: mention steps for BitLocker earlier Fiona Ebner
2026-03-18 10:25 ` [PATCH-SERIES qemu-server/docs 0/2] efi enroll: small improvements to documentation Maximiliano Sandoval
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=20260318093307.31645-2-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox