Windows 10 fails to boot with rdmsr to register 0x3a on vcpu 0 error

[ebarannikov]

Trying to launch Windows 10 VM:

#!/bin/sh

IMG=/Users/euge/Vm/Windows.dmg
BOOTVOLUME=/Users/euge/Downloads/Win10_20H2_Hungarian_x64.iso
FIRMWARE="/Users/euge/Vm/BHYVE_UEFI_20151002.fd"

PATH="build/Release:build:$PATH"

xhyve
-w
-m 4G
-c 1
-s 0:0,hostbridge
-s 3,ahci-cd,$BOOTVOLUME
-s 4,ahci-hd,$IMG
-s 5,e1000
-s 29,fbuf,tcp=127.0.0.1:29000,w=1024,h=768,wait
-s 31,lpc -l com1,stdio
-l bootrom,$FIRMWARE

I can see "Press any button to start from disk..." invitation and then it turns to:
rdmsr to register 0x3a on vcpu 0
Unhandled ps2 keyboard command 0x02

and keeps hanging like this eternally.

Please, help.

UPD: after a while it finally gave up with "Unsupported cmd:b0"

[TiagoJSilva]

I was having the same issue but I was able to solve it with a later version of that UEFI firmware; _20160526.fd has worked for me - at least the installer on the Windows ISO is booting. You'll only see the installer on the VNC session.

[ebarannikov]

I was having the same issue but I was able to solve it with a later version of that UEFI firmware; _20160526.fd has worked for me - at least the installer on the Windows ISO is booting. You'll only see the installer on the VNC session.

@TiagoJSilva thank you for your reply. Could you please also share the link to the working UEFI file, plz? Greatly appreciate your help

[TiagoJSilva]

Where did you get the 20151002.fd? The 20160526.fd was there too (as well as a version with UEFI-CSM that may be useful to install Windows 7, although I haven't tested it).

I don't know why xhyve doesn't have a link to a known good UEFI firmware and asks us to install the bhyve-firmware package on a FreeBSD system and then move the firmware file to a Mac; licensing limitations? (On *BSD?)

Anyway, this seems to be the personal share of an official FreeBSD developer and I hope I won't be banned for linking to it nor force this share to become private: h**ps://people.freebsd.org/~grehan/bhyve_uefi/

This developer might be Peter Grehan, https://github.com/grehan-freebsd

Edit: AFAICT, the 2015 firmware couldn't map the contents of the Windows install ISO in UEFI; the device was there, but the only map was for the disk image that would simulate the system hard disk. I found that out because if you don't hit the "press any key to boot from DVD" in time, the boot proceeds into the EFI Shell and "map -v" won't show a map for the ISO nor "map -r" will map it. Meanwhile, Windows 21H01 install is crashing during the OOBE part of the setup so even this firmware may not be good enough. If you can, get the official bhyve-firmware files.

[ebarannikov]

thanks a million for your input!

[TiagoJSilva]

Just to update, I was able to complete 21H01 installation with the _20160526.fd firmware.

[ebarannikov]

Thanks a lot for the confirmation!