On 13/09/2021 04:43, Sam Varshavchik wrote:
Ulf Volmer writes:
> On 12.09.21 19:21, Sam Varshavchik wrote:
>> If you're running a qemu VM with a Windows 10 guest (in F34) and you
successfully enabled TPM emulation, I'd like to compare notes with you.
>>
>> I used virt-manager to enable TPM 2.0, both TIS and CRB types:
>>
>> <tpm model="tpm-tis">
>> <backend type="emulator" version="2.0"/>
>> <alias name="tpm0"/>
>> </tpm>
>>
>> and
>>
>> <tpm model="tpm-crb">
>> <backend type="emulator" version="2.0"/>
>> <alias name="tpm0"/>
>> </tpm>
>>
>> My fully activated/licensed Windows 10 VM (21H1) refuses to recognize TPM.
"Security Processor Troubleshooting" reports:
>>
>> "Your device does not support this feature."
>>
>> I've read multiple reports that this should work, so I must be missing
something. Looking at a working qemu configuration in /etc/libvirt/qemu is the only thing
I can think of.
>
> I have a virtual 21H1 and the TPM2 device is shown in the device manager and also in
the security settings (with vendor IBM). But I'm currently not using this feature on
windows.
>
> My libvirt settings are:
>
> <tpm model='tpm-crb'>
> <backend type='emulator' version='2.0'/>
> </tpm>
Well, that's what I showed what I had, above, except for the alias setting, which I
can't imagine making any difference, but I'll try manually removing that.
FWIW, I could not get TPM emulation working with qemu Win10 guests. However, it worked
just fine with Win11.
--
I had a very rare reaction to the Moderna vaccine. It landed me in the hospital for 25
days..
Hard to get back into the swing of things.