On Sun, Dec 08, 2024 at 08:50:59AM -0500, Thomas Laus wrote: > > I may have missed defining my issue. I thought that it was related to the > creation of the tap device. It looks like a problem is with virtio-net not > getting loaded during the VM boot process on FreeDSD-14.2-RELEASE. > > vm-bhyve log from startup on FreeBSD-14.1-RELEASE > > Dec 06 17:18:55: [bhyve devices: -s 0,hostbridge -s 31,lpc -s > 4:0,virtio-blk,/virtual/openbsd/disk0.img -s > 5:0,virtio-net,tap0,mac=58:9c:fc:09:93:65 -s 6:0,passthru,3/0/0] > Dec 06 17:18:55: [bhyve console: -l com1,/dev/nmdm-openbsd.1A] > Dec 06 17:18:55: starting bhyve (run 1) > > vm-bhyve log from startup on FreeBSD-14.2-RELEASE > > Dec 07 13:57:55: [bhyve devices: -s 0,hostbridge -s 31,lpc -s > 4:0,virtio-blk,/virtual/openbsd/disk0.img -s 6:0,passthru,3/0/0] > Dec 07 13:57:55: [bhyve console: -l com1,/dev/nmdm-openbsd.1A] > Dec 07 13:57:55: starting bhyve (run 1)
Did you run the same version of vm-bhyve on FreeBSD-14.1-RELEASE? https://github.com/churchers/vm-bhyve/issues/570
