47 lines
1.7 KiB
Diff
47 lines
1.7 KiB
Diff
From 859c43b1eb81cfdcb5f481b571e2c387860f8a27 Mon Sep 17 00:00:00 2001
|
|
From: "Richard W.M. Jones" <rjones@redhat.com>
|
|
Date: Tue, 13 Jan 2026 12:33:11 +0000
|
|
Subject: [PATCH] docs/virt-v2v.pod: Document Windows vTPM and BitLocker
|
|
Recovery
|
|
|
|
Reported-by: Ming Xie
|
|
Fixes: https://issues.redhat.com/browse/RHEL-103915
|
|
---
|
|
docs/virt-v2v.pod | 23 +++++++++++++++++++++++
|
|
1 file changed, 23 insertions(+)
|
|
|
|
diff --git a/docs/virt-v2v.pod b/docs/virt-v2v.pod
|
|
index a3cacb82..f751f4e7 100644
|
|
--- a/docs/virt-v2v.pod
|
|
+++ b/docs/virt-v2v.pod
|
|
@@ -1600,6 +1600,29 @@ L<https://issues.redhat.com/browse/RHEL-70840>
|
|
and
|
|
L<https://windowstechpro.com/how-to-enable-bitlocker-on-windows-11/>
|
|
|
|
+=head2 Windows: "Enter the recovery key for this drive"
|
|
+
|
|
+After conversion, you may be presented with a Windows boot screen showing:
|
|
+
|
|
+ BitLocker recovery
|
|
+ Enter the recovery key for this drive
|
|
+ [|___________________]
|
|
+
|
|
+(See screenshot on L<https://issues.redhat.com/browse/RHEL-103915>)
|
|
+
|
|
+This happens when the Windows BitLocker disk encryption key is
|
|
+contained in the VMware Virtual Trusted Platform Module (vTPM). The
|
|
+vTPM is working I<exactly as designed>. It is preventing the
|
|
+encrypted disk from being moved from one machine to another by storing
|
|
+the encryption key in trusted storage on the source. By design, we
|
|
+cannot access or move this key to the target.
|
|
+
|
|
+To start the VM you will need to enter the BitLocker recovery key.
|
|
+This will also register the disk against the new vTPM on the target,
|
|
+so it should only be necessary to do this once.
|
|
+
|
|
+For help finding the recovery key: L<https://aka.ms/recoverykeyfaq>
|
|
+
|
|
=head2 Networks and bridges
|
|
|
|
Guests are usually connected to one or more networks, and when
|