Using FreeBSD-15.0-BETA3-amd64-BASIC-CLOUDINIT-zfs.qcow2.xz on a Digital Ocean VM, BETA3 hangs after "vtnet1: link state changed to UP" (^T gives no output), whereas BETA2 used to start without issues. The console log does not provide useful information, and it is not possible to access previous lines of console output. The same BETA3 image (but raw format) works fine under bhyve (14.3 host). === psm0: model IntelliMouse Explorer, device ID 4 pcm0: <NVIDIA (0x0091) (HDMI/DP 8ch)> at nid 5 on hdac0 onnid QRMQ000 on isa0 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff pnpid PNP0900 on isa0 atrtimer0: <AT timer> at port 0x40 on isa0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtimer0: non_ISA device will be removed from GENERIC in FreeBSD 15. Timecounters tick every 10.000 msec ugen0.1: <Intel UHCI root HUB> at usbus0 uhub0 on usbus0 uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0 ZFS filesystem version: 5 ZFS storage pool version: features support (5000) random: unblocking device. Trying to mount root from zfs:zroot/ROOT/default []... uhub0: 2 ports with 2 removable, self powered Dual Console: Serial Primary, Video Secondary intsmb0: <Intel PIIX4 SMBUS Interface> irq 9 at device 1.3 on pci0 intsmb0: intr IRQ 9 enabled revision 0 smbus0: <System Management Bus> on intsmb0 lo0: link state changed to UP vtnet0: link state changed to UP vtnet1: link state changed to UP [stops] This should go on with "Starting dhclient" but gets stuck. Not much information so it's just a heads-up.
15.0-BETA4 too hangs in Digital Ocean :(
Commit f999ffdce3813eb946f10999ccffb8275c324469 addresses a problem which could be related. I will make sure it is fixed in 15.0. If you are able to test a custom kernel in the meantime, that would be appreciated.
I could try with FreeBSD-15.0-STABLE-amd64-BASIC-CLOUDINIT-20251106-71bd17b879a7-281079-zfs.qcow2.xz and it's not hanging anymore :)
15.0-BETA5 image still hangs (only ZFS, UFS boots fine)
*** Boots correctly on RC1! *** Oddly enough, the RC1 UFS image shows console output (Starting ssh, etc.) while the ZFS image does not (it goes from kernel output strait to login), but they both end with the same services running.
-RC2 good too, also both images have same console settings and appear the same way, so I'd say it's all good.