Re: Bhyve and Rocky Linux startup error

From: Frank Leonhardt <freebsd-doc_at_fjl.co.uk>
Date: Fri, 15 Aug 2025 13:23:11 UTC
On 15/08/2025 13:16, Frank Leonhardt wrote:
> Hi All,
>
> I'm not a fan of byhve or virtualisation in general, and not a fan of 
> Linux, but they've come together in my life and I'm trying to run 
> Rocky (the successor to CentOS) under FreeBSD.
>
> When I kick it off I get the following:
> ---------------
> BdsDxe: starting Boot0001 "UEFI BHYVE SATA DVD ROM 
> BHYVE-DE5C-3F46-0368" from PciRoot(0x0)/Pci(0x3,0x0)/Sata(0x0,0xFFFF,0x0)
> !!!! X64 Exception Type - 06(#UD - Invalid Opcode)  CPU Apic ID - 0000000
>
> < snip register dump>
>
>
> FXSAVE_STATE - 000000003FF421D0
> !!!! Find image based on IP(0x3D9E61F0) (No PDB) 
> (ImageBase=000000003D9D3000, EntryPoint=000000003D9D4000) !!!!
>
> ---------------
>
> It remains running and I have to kill it on another terminal.
>
> This is on FreeBSD 14.2-RELEASE, amd64 generic kernel.
>
> I configure the environment with:
>
> kldload nmdm
> kldload vmm
> ifconfig tap0 create
> sysctl net.link.tap.up_on_open=1
> ifconfig bridge0 create
> ifconfig bridge0 name bge0bridge
> ifconfig bge0bridge addm bge0 tap0
> ifconfig bge0bridge up
>
> bhyve -c 1 -m 1G -w -H \
> -s 0,hostbridge \
> -s 3,ahci-cd,Rocky-10.0-x86_64-dvd1.iso \
> -s 4,virtio-blk,/home/fjl/rockyvm.hdd \
> -s 5,virtio-net,tap0 \
> -s 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait \
> -s 30,xhci,tablet \
> -s 31,lpc -l com1,stdio \
> -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
> rockyvm
>
> All the files exist (rockyvm.hdd  is 16G of nulls) although I note the 
> uefi firmware is no longer maintained. I can connect to it using a VNC 
> client and watch it crash.
>
> Any ideas? May be simple, may be complicated. I just don't know with 
> bhyve.
>
> Thanks, Frank.
>
>
Further - if I use a Debian 13 ISO and change nothing else, it seems to 
work. I suspect the CD-ROM image being funny but don't know enough about 
why. I tried more than one Rocky ISO file.

(Methinks I may have got the networking wrong, but that's another question).

Thanks, Frank.