You should probably use uefi loader instead of bhyveload(8) one.Is this one?
Code:loader="bhyveload" cpu=1 memory=1024M network0_type="virtio-net" network0_switch="public" disk0_type="virtio-blk" disk0_name="disk0.img" uuid="61da34de-2ba3-42b8-ab7f-d6096cb0f9cd" network0_mac="58:9c:fc:03:51:90"
loader="uefi"
uefi_vars="yes"
graphics="yes"
graphics_res="1920x1080"
graphics_post="5900"
xhci_mouse="yes"
vm start <ubuntu2604-vm-name>
vncviewer 127.0.0.1:5900
BdsDxe: failed to load Boot001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x4,0x0): Not found
BdsDxe: No bootable option or device was found
BdsDxe: Press any key to enter the Boot Manager Menu
Oh, yeah I remember I had something very similar with my Ubuntu 26.04 VM. Take a look at this issue, this is where I found a solution for myself, I believe it should work for you as well.after input vncviewer 127.0.0.1:5900, I got a screen
can't continue, what to do next?Code:BdsDxe: failed to load Boot001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x4,0x0): Not found BdsDxe: No bootable option or device was found BdsDxe: Press any key to enter the Boot Manager Menu
Probably Ubuntu choose a non-standard name for its UEFI loader (the .efi file in the EFI partition), and since UEFI variables support was not enabled (the uefi_vars="yes" entry in your VM config file) the UEFI firmware is looking for a loader with a standard name.after input vncviewer 127.0.0.1:5900, I got a screen
can't continue, what to do next?Code:BdsDxe: failed to load Boot001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x4,0x0): Not found BdsDxe: No bootable option or device was found BdsDxe: Press any key to enter the Boot Manager Menu
# =====================================================================
# ubuntu
# =====================================================================
loader="uefi"
cpu="4"
memory="4G"
network0_type="virtio-net"
network0_switch="public"
# =====================================================================
# Switch from file image to sparse Zvol block storage
# =====================================================================
disk0_type="nvme"
disk0_name="disk0"
disk0_dev="sparse-zvol"
# =====================================================================
# System context lines
# =====================================================================
utctime="yes"
virt_random="yes"
graphics="yes"
xhci_mouse="yes"
graphics_res="1920x1080"
uefi_vars="yes"
Yes, you cannot use a bridge(4) to tie a VM to your wireless interface. You will have to do NAT.Any solutions?
There is the official documentation: https://github.com/freebsd/vm-bhyve/wiki/NAT-ConfigurationHow to do that?