Hi there
Interesting -- however does the TPM support work if you've either disabled in BIOS the TPM or your CPU / MOBO doesn't have it. The KVM solution doesn't rely on there actually being a physical TPM module. I'll try a HYPER-V GEN 2 solution on a spare INTEL laptop (disabling the TPM in the BIOS) to try and replicate creating a VM on a machine that doesn't have TPM.
I don't need to do anything with the VM but just see if Windows "recognises" the virtual TPM hardware. It's one thing adding support in the VM config but another to get the Windows VM to recognise it. !! For instance if I disable TPM and don't run the TPM emulator then the Windows VM doesn't recognise the TPM device,
If HYPER-V has a built in "TPM" emulator that's an interesting solution for primary Windows users of course
Maybe
@Kari - any ideas on "Virtual TPM emulation on a VM with HYPER-V" if the Host either doesn't have TPM or it's been disabled.
I'll have a go later today with this -- not much else going on currently --and anything to get out of a "trip to the Supermarket" on a Sat afternoon. !!!!
Another query for the Windows cognoscenti. What's Windows 11 currently doing with TPM - looking at the activity log - doesn't seem to be doing anything with it - it recognises that it exists - but again I'm only using the leaked iso - the next in line official ones might be more informative.
Cheers
jimbo
Hello jimbo45,
Glad to hear about the quest -- I haven't tested it with the TPM disabled as I have bitlocker enabled and disabling it would rain fire on me -- but I'd give it a high probability that it does work since it is virtual hardware.
Please post back once you have tried it, I'm curious!
You would need Windows 10 Pro, Education or above for this to work as the Home version does not have full Hyper-V support.
In case you have any of these higher editions, just type "features" into the start menu and choose "Turn Windows features on or off". Make sure to choose the old control panel option as this one had not been fully ported into the new pc settings app. There is a manage optional features that is already in the new pc settings app and start menu offers that too, but you can't set it up from there / make sure not to use that.
Once you're in "Turn Windows features on or off" just enable the Hyper-V role. Then reboot and type hyper-v into start menu. From the you can either launch the Hyper-V control panel or use the quick-create hyper-v vm to create one right away.
Remember, turning on Hyper-V would instantly disable ANY 3rd party virtualization apps running on that PC, such as virtualbox or vmware or android emulator. It will also disable other virtualization apps such AV Kaspersky's or Avast's virtual sandbox environment. To be more precise it wouldn't actually disable them but prevent their engine from utilizing your hardware's virtualization engine (intel VT-x or AMD-V) as Hyper-V requires sole access.
If you require these 3rd party apps to work then you might be able to route some of them through Hyper-V, just like you did with QEMU using KVM. For this to work, you would need to also enable this role: "Windows Hypervisor Platform"
In fact, VMWare can use Hyper-V engine and Virtualbox just gained support too. These apps should not be necessary as Hyper-V can run VMs on it's own, but I'm writing just in case you have old VMs in these apps that you want to keep using.
You can also consider enabling additional roles alongside Hyper-V too, such as Virtual Machine Platform which is actually, support for WSL2, enabling you to run terminal console Linux distros such as Ubuntu downloaded from the Microsoft Store app with native speed and native linux filesystem. The Windows Subsystem for Linux role which you can also find in this menu is actually the older version of WSL, WSL1. You can enable both of them and you can switch between them. The main difference is that WSL1 does not use Hyper-V and is slower but useful if you cannot/dont want to enable Hyper-V for the aforementioned reasons.
Happy testing!
www.elevenforum.com
