NetBSD 9.0 RC1 installer crash immediately during boot

[Bodie]

Hi,

downloaded NetBSD-9.0_RC1-amd64.iso from  https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/images/

Host is Windows 10 on Lenovo ThinkPad T590 Guest is NetBSD 64b with 2 vCPU, 8GB RAM, without disk, LiveCD over IDE and USB flash disk via USB filter (to which I want to install) -  https://shop.westerndigital.com/products/usb-flash-drives/sandisk-ultra-fit-usb-3-1#SDCZ430-128G-A46 (128GB version)

NetBSD starts to boot loader with 3 options how to boot. Hitting default boot normally and it immediately crash and screen on background is just black.

See attached files for details once allowed to upload.

[Bodie]

Log of NetBSD guest

[Bodie]

screenshot right after crash

[Bodie]

Tested now with assigned virtual disk (IDE, SATA, NVME) and problem is the same so not related to USB disk at least.

[Bodie]

Related thread on NetBSD mailing list  https://mail-index.netbsd.org/current-users/2019/12/11/msg037187.html suggested to check:

CPUID values are ... = guest (host):

IBRS_IBPB - IA32_SPEC_CTRL.IBRS and IA32_PRED_CMD.IBPB  = 0 (1)
STIBP - Supports IA32_SPEC_CTRL.STIBP                   = 0 (1)
SSBD - Supports IA32_SPEC_CTRL.SSBD                     = 0 (1)

so the NetBSD guest is told the cpu doesn't support IA32_SPEC_CTRL (0x48), but still the guest tries to read it:

00:00:11.518912 IEM: rdmsr(0x48) -> #GP(0)
00:00:11.518920 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'

But same values are set in NetBSD 8.1 STABLE amd64 on same host/VirtualBox combo and that one boots and runs just fine.

[socratis]

Try the following:

VBoxManage modifyvm "NetBSD" --spec-ctrl on

It should solve your crash...

[Bodie]

Replying to socratis:

Try the following:

VBoxManage modifyvm "NetBSD" --spec-ctrl on

It should solve your crash...

I can confirm that with this setting it is possible to install this version. And it boots in to system after install.

BTW project reported that current from 13.12.2019 (9.99.23) was booting just fine, but I do not know details about the host.

[vushakov]

Can you try a test build (r135456 or later).

[aeichner]

No response and there was a fix for 6.1.2, closing. Please reopen if this is still an issue with the latest VirtualBox 6.1 release.