RE: https://mastodon.bsd.cafe/@grahamperrin/116155254526138460

FreeBSD-CURRENT testing with real hardware blocked by <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293663>,

293663 – main (CURRENT) 20260302 5d9b185c33ae snapshot can not boot with UEFI

#FreeBSD #CURRENT #bug

@grahamperrin Thanks for the warning. I am trying to migrate my FreeBSD VMs from Hyper-V to KVM just now and am having big problems with NetworkManager after catching the libvirt breakage with modern FreeBSD and dealing with it.

@bms48 what's the breakage?

#libvirt #FreeBSD

@grahamperrin You have to import it as a BIOS using VM initially because virt-manager won't let you back out of EFI secure boot otherwise, then change it to EFI without in the <os> block. Also, SCSI. You need to import as the root disk as VirtIO then change to SCSI and add a SCSI controller manually, and all before you commit to the import in the GUI. After boot, rename hn0 to vtnet0 in /etc/rc.conf.
@grahamperrin That's not the breakage. The blocker right now is getting a bridge config for the VMs that works under NetworkManager, persists correctly, and lets my Ethernet port continue to work for the host via DHCP.
@bms48 whoa. That's only with FreeBSD as a host, yes?
@grahamperrin Ubuntu host, FreeBSD guest (mixture of CURRENT and STABLE; the VMs I actively commit from).
@grahamperrin Sorted. New strategy: use systemd-networkd config for wired and bridges,
and NetworkManager for Wi-Fi. That side-stepped nmcli completely,
but meant having to use systemd-networkd for wired Ethernet and bridges.
This turned out to be the winning move. Selective GenAI prompting
got me a working configuration quite quickly; /etc/systemd/network
needed to be populated with various files

@bms48 any overlap with UEFI-specific boot bug 293663?

<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293663>

293663 – main (CURRENT) 20260302 5d9b185c33ae snapshot can not boot with UEFI

@grahamperrin I doubt that it does directly as the build delta for the -CURRENT VM (which was the first to get migrated, the other one is 15.0-RELEASEA-p4 which is outstanding) may date from early last week, but I am tracking the EFI issue in case it affects fresh builds.