hyper-v Can't boot FreeBSD on XCP-ng hypervisor, but TrueNAS can.

rempargo

New Member


Messages: 3

We got a server with a AMD Threadripper 3970X and we are using xcp-ng as Hypervisor.

I'm trying to get FreeBSD running, but after numerous attempts, it all hangs on the same issue

Code:
uhid0 on uhub0
uhid0: <QEMU QEMU USB Tablet, class 0/0, rev 2.00/0.00, addr 2> on usbus0


I've tried:
FreeBSD-11.4-RELEASE-amd64-bootonly.iso
FreeBSD-12.0-RELEASE-i386-dvd1.iso (it's i386, I know, it will show the UEFI Interactive Shell v2.2, does not boot at all.)
FreeBSD-12.1-RELEASE-amd64-bootonly.iso
FreeBSD-12.2-RELEASE-amd64-bootonly.iso
FreeBSD-12.2-RELEASE-amd64-disc1.iso
FreeBSD-12.2-RELEASE-amd64-dvd1.iso
FreeBSD-13.0-CURRENT-amd64-20201022-0035a6c7bb7-bootonly.iso

They all hang on the exact same point, any input of the keyboard is ignored, but if I change the .iso of the VM, it will give me

Code:
g_access(961): provider iso9660/12_2_RELEASE_AMD64CD has error 6 set


After this unsuccessful tries, I tried to install TrueNas:
TrueNAS-12.0-RELEASE.iso

Surprisingly, this worked immediately. Anybody knows what's different with the TrueNas image that made it work as VM on XCP-ng? Or why does FreeBSD's just won't fully boot up?
 
OP
rempargo

rempargo

New Member


Messages: 3

I used XCP-ng Center 20.04.00 to create the VM, and the TrueNas had BIOS Boot as Boot mode, and FreeBSD was set on UEFI Boot.

That setting can only be set once while creating the VM, not afterwards, that's why I had a hard time finding this setting.

Quick conclusion: FreeBSD can't boot as VM on XCP-ng when you set the Boot mode as UEFI BOOT, you must use BIOS BOOT
 
Top