Bug 1885646 - After passing through TPM device to Windows guest, user cannot take the ownership of the device from VM console
Summary: After passing through TPM device to Windows guest, user cannot take the owner...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: libtpms
Version: ---
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: 8.3
Assignee: Marc-Andre Lureau
QA Contact: Qinghua Cheng
URL:
Whiteboard:
Depends On:
Blocks: 1897025
TreeView+ depends on / blocked
 
Reported: 2020-10-06 15:30 UTC by Abhishekh Patil
Modified: 2024-03-25 16:39 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-06 01:02:16 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Abhishekh Patil 2020-10-06 15:30:07 UTC
Description of problem:

After passing through TPM device to Windows guest (which is running on RHEL-8.1 KVM hypervisor), user cannot take the ownership of the device from VM console.

Version-Release number of selected component (if applicable):
libvirt-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64

How reproducible:
Can't reproduce


Actual results:

User can see the TPM device inside Windows guest, but cannot access it.

Expected results:

User should be able to access the TPM device from the guest.

Additional info:

Comment 4 Jaroslav Suchanek 2020-11-06 10:49:17 UTC
Moving to qemu-kvm for further investigation. Seems that libvirt is passing the fd correctly. Thanks.

Comment 5 John Ferlan 2020-11-06 13:11:21 UTC
Changing a few things here - this must be an Advanced Virt issue and this isn't a qemu-kvm/general, rather it's a libtpms related issue.  Also the only place where libtpms is supported is in a RHEL-AV environment.

For the submitter - it would be nice to get a better idea of the environment - indicating "RHEL-8.1 KVM hypervisor" and then showing "libvirt-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64" which looks like RHEL AV 8.2.0 - doesn't quite make sense. Additionally, what Windows version is being used on the guest.

In the mean time, I've assigned to Marc-Andre for further thoughts/analysis

Comment 6 CongLi 2020-11-07 01:56:44 UTC
Qinghua,

Can you have a try?

Thanks.

Comment 7 Marc-Andre Lureau 2020-11-07 09:19:31 UTC
It's not a libtpms issue, since the host TPM device is passed-through.

We have a very limited support for TPM passthrough, and we have encountered a number of issues that aren't easy to solve.

I am afraid there isn't much we can do here.


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