On 12/7/24 17:38, mike tancsa wrote:
On 12/7/2024 4:37 PM, Thomas Laus wrote:
I dont have anything unusual in my config. I am running just a few days
ahead of 14.2, but I dont think that makes a difference
kldstat
Id Refs Address Size Name
1 47 0xffffffff80200000 1f3d9c0 kernel
2 1 0xffffffff8213f000 5da658 zfs.ko
3 1 0xffffffff8271a000 36c8 coretemp.ko
4 2 0xffffffff8271e000 8dae8 pf.ko
5 1 0xffffffff827ac000 77d8 cryptodev.ko
6 1 0xffffffff827b4000 3c58 pflog.ko
7 1 0xffffffff83c20000 3390 acpi_wmi.ko
8 1 0xffffffff83c24000 4250 ichsmb.ko
9 1 0xffffffff83c29000 2178 smbus.ko
10 1 0xffffffff83c2c000 7798 if_bridge.ko
11 1 0xffffffff83c34000 60e0 bridgestp.ko
12 1 0xffffffff83c3b000 33c0 uchcom.ko
13 1 0xffffffff83c3f000 4e10 ucom.ko
14 1 0xffffffff83e00000 33e438 vmm.ko
15 1 0xffffffff83c44000 4850 nullfs.ko
Starting up a vm works as before for me
vmrun.sh -t tap0 -d /baseimage/14-1VM-p6.raw -E vm0
Launching virtual machine "vm0" ...
fbuf frame buffer base: 0x2be256a00000 [sz 16777216]
3h
3h
3h
BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x3,0x0)
BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x3,0x0)
Consoles: EFI console
Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p2:
FreeBSD/amd64 EFI loader, Revision 1.1
Command line arguments: loader.efi
Image base: 0x1e27a000
EFI version: 2.70
EFI Firmware: BHYVE (rev 1.00)
Console: efi (0x20001000)
Load Path: \EFI\BOOT\BOOTX64.EFI
Load Device: PciRoot(0x0)/Pci(0x3,0x0)/HD(2,GPT,E140336F-1F4D-11EF-
AE18-002590EC5BF2,0x17B,0x10418)
BootCurrent: 0001
BootOrder: 0000 0001[*] 0002 0003 0004
BootInfo Path: PciRoot(0x0)/Pci(0x3,0x0)
Ignoring Boot0001: Only one DP found
Trying ESP: PciRoot(0x0)/Pci(0x3,0x0)/HD(2,GPT,E140336F-1F4D-11EF-
AE18-002590EC5BF2,0x17B,0x10418)
Setting currdev to disk0p2:
Trying: PciRoot(0x0)/Pci(0x3,0x0)/HD(1,GPT,E1403365-1F4D-11EF-
AE18-002590EC5BF2,0x22,0x159)
Setting currdev to disk0p1:
Trying: PciRoot(0x0)/Pci(0x3,0x0)/HD(3,GPT,E1403374-1F4D-11EF-
AE18-002590EC5BF2,0x10593,0x200000)
Setting currdev to disk0p3:
Trying: PciRoot(0x0)/Pci(0x3,0x0)/HD(4,GPT,E1403378-1F4D-11EF-
AE18-002590EC5BF2,0x210593,0x11FFF6D)
Setting currdev to zfs:zroot/ROOT/default:--
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)
Tom
---
Public Keys:
PGP KeyID = 0x5F22FDC1
GnuPG KeyID = 0x620836CF
