Anybody know why the CPU virtualisation features are disabled if booting from power off into Windows (running under boot camp), but if you boot to MacOS first (as far as the login screen is enough), then reboot, hold down the option key and boot into windows they are enabled?
This is repeatable and happens every time.
Thanks
Windows, Windows 10
This depends on the year/model of your Mac.
Also, see Turn off Hyper-V to use Windows 10 on your Mac - Apple Support. Be careful.
Boot directly into Windows and run msinfo32 check the Hyper-V settings.
From the macOS side, in Terminal, post the output of
sysctl -a | grep machdep.cpu.features
On the Windows side, take a look at https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v .
On the Mac side, it shows VMX as an available CPU feature - I believe that is the virtualisation function.
In Windows, it entirely depends on whether it's been booted straight into Windows, or into MacOS and then rebooted. If it's the latter then Hyper-V works as intended, and VMs will start. If it's booted straight into Windows then virtualisation is not enabled and VMs will not run. The virtualisation features status (i.e. whether they are enabled or not) can also be seen on the CPU section of Task Manager.
Thanks
It boots into Windows OK in either case - but I'm wanting the virtualisation features to run Hyper-V . This does run fine provided the computer has been booted into MacOS first then rebooted, so that the virtualisation features are available. If it's booted straight to Windows, then Hyper-V throws up the expected error about virtualisation features not being available.
On a Windows machine the features are either on or off, usually selected via a tickbox in the BIOS/UEFI, but Macs don't have an equaivalent to this, and the behaviour where you have to boot into MacOS first before they appear as enabled in Windows is rather strange.
As regards the model, it's a 2015 12" Macbook, running Catalina and Windows 10.
Virtualisation under boot camp