2130473 – Bitlocker has encryption issue with fresh installed Win10 guest

This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2130473 - Bitlocker has encryption issue with fresh installed Win10 guest

Summary: Bitlocker has encryption issue with fresh installed Win10 guest

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Enterprise Linux 9
Classification:	Red Hat
Component:	libtpms
Sub Component:
Version:	9.1
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Marek Kedzierski
QA Contact:	Qinghua Cheng
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2022-09-28 09:06 UTC by Qinghua Cheng
Modified:	2023-09-20 05:42 UTC (History)
CC List:	6 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2023-09-20 05:42:56 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)
Screenshot from event log with TPM error (385.63 KB, image/jpeg) 2022-10-11 08:11 UTC, Marek Kedzierski	no flags	Details
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	RHEL-5326	0	None	Migrated	None	2023-09-20 05:39:45 UTC
Red Hat Issue Tracker	RHELPLAN-135121	0	None	None	None	2022-09-28 09:08:21 UTC

Description Qinghua Cheng 2022-09-28 09:06:27 UTC

This bug was initially created as a copy of Bug #1877721

I am copying this bug because:

This bug is still reproducible on rhel 9.2, with fresh installed windows 10 guest.

Description of problem:
Bitlocker doesn't start to do encryption with fresh installed Win10 guest. But a reboot of the guest, bitlocker can start encryption.

Version-Release number of selected component (if applicable):
RHEL 8.3
Kernel: 4.18.0-234.el8.x86_64
qemu-kvm: qemu-kvm-5.1.0-2.module+el8.3.0+7652+b30e6901.x86_64
edk2: edk2-ovmf-20200602gitca407c7246bf-3.el8.noarch
libptms: libtpms-0.7.2-1.20200527git7325acb477.module+el8.3.0+7068+4e1b8df5.x86_64
swtpm: swtpm-0.3.0-1.20200218git74ae43b.module+el8.3.0+7648+42900458.x86_64

How reproducible:

Steps to Reproduce:
1. Install a win10 guest (q35 + OVMF)
2. Attach vtpm device to win10 guest
3. Inside guest vm run commands:

bdehdcfg -target c: shrink -newdriveletter s: -size 606 -quiet
manage-bde -on c:

reboot system as required.

4. Re-login guest vm after reboot, run command:
manage-bde -status

Actual results:
Encryption is not started
Pop up dialog with Bitlocker could not be enabled. (see attachment)

manage-bde -status

Disk volumes that can be protected with
BitLocker Drive Encryption:
Volume C: [Windows]
[OS Volume]

Size: 29.62 GB
BitLocker Version: None
Conversion Status: Fully Decrypted
Percentage Encrypted: 0.0%
Encryption Method: None
Protection Status: Protection Off
Lock Status: Unlocked
Identification Field: None
Key Protectors: None Found

Expected results:

Bitlocker can encrypt win10 guest without issue.

Additional info:

This issue only happens with refresh installed win10 guest. When reboot the guest vm again, and repeat the test steps, bitlocker can start disk encryption.

Comment 1 Marc-Andre Lureau 2022-09-29 08:09:42 UTC

In https://bugzilla.redhat.com/show_bug.cgi?id=1877721#c7, you tested successfully with a more recent version of libtpms & swtpm.

Have you checked with latest rhel9 build? (I think they are libtpms-0.9.1-2.20211126git1ff6fe1f43.el9 & swtpm-0.7.0-3.20211109gitb79fd91.el9)

In any case, my remarks/questions in Bug #1877721 are still valid, I am not sure this is a vtpm issue.

thanks

Comment 2 Qinghua Cheng 2022-09-29 10:05:36 UTC

Hi Marc-Andre,

I just tested on rhel 9.2 with Win11(22h2) guest:

libtpms-0.9.1-2.20211126git1ff6fe1f43.el9.x86_64
swtpm-0.7.0-3.20211109gitb79fd91.el9.x86_64
kernel: 5.14.0-168.el9.x86_64
qemu-kvm: qemu-kvm-7.1.0-1.el9.x86_64

Win11 guest can also reproduce this issue. 

Thanks. 



(In reply to Marc-Andre Lureau from comment #1)
> In https://bugzilla.redhat.com/show_bug.cgi?id=1877721#c7, you tested
> successfully with a more recent version of libtpms & swtpm.
> 
> Have you checked with latest rhel9 build? (I think they are
> libtpms-0.9.1-2.20211126git1ff6fe1f43.el9 &
> swtpm-0.7.0-3.20211109gitb79fd91.el9)
> 
> In any case, my remarks/questions in Bug #1877721 are still valid, I am not
> sure this is a vtpm issue.
> 
> thanks

Comment 3 John Ferlan 2022-10-04 20:49:32 UTC

Marek - any chance we can get someone from the Virt Windows SST to weigh in on this case? It's odd the 2nd reboot "fixes" things magically. 

Maybe even a direct connect with Microsoft?  Are there any debugging tools that could be employed to rule out QEMU / libptms / swtpm?

thanks

Comment 8 Qinghua Cheng 2022-10-08 08:04:12 UTC

Hi Marek,

Thanks for taking a look of this bz. Please find the attached logs for detailed information. If you need more information, please let me know.

Thanks,
Qinghua

Comment 10 Marek Kedzierski 2022-10-11 08:11:00 UTC

Created attachment 1917225 [details]
Screenshot from event log with TPM error

Comment 13 RHEL Program Management 2023-09-20 05:37:49 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 14 RHEL Program Management 2023-09-20 05:42:56 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Note You need to log in before you can comment on or make changes to this bug.