On 7/13/21 4:33 PM, Stephen Morris wrote:
I have a question about TPM hardware.
Fedora 34 running as an image in a Vmware Player VM on a Windows 10 host
reports that I don't have a TPM chip, and with Windows 10 running in a
Virtualbox (both these VM' are the free versions of the VM's) VM on the
same Windows 10 host when I try to update the image to Windows 11 it
says the environment does not meet the install requirements. Vmware
Player doesn't support UEFI but Virtualbox does and is active in the VM
images. If I try upgrade the native Windows 10 host Windows 11 says it
can install on my hardware. The Bios indicates that I have activated
fTPM in my AMD Rizen cpu which Windows 11 seems to be finding, are the
VM's suppressing the TPM functionality because I need to buy the
commercial versions that allow a TPM to be added to the VM's as a
device, or is Windows 11 and Fedora 34 not looking for the hardware the
right way when running in a VM?
The OS in the VM can't see any of the hardware on the host system unless
the VM specifically passes it through. Normally, all "hardware" in the
VM is virtual. qemu has an option to add a TPM by either creating a
virtual one or passing the hardware one through. I have no idea about
vmware or virtualbox.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
