Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 8 Dec 2024 08:50:59 -0500
From:      Thomas Laus <lausts@acm.org>
To:        mike tancsa <mike@sentex.net>, freebsd-virtualization@freebsd.org
Subject:   Re: Tap device problem on FreeBSD 14.2-RELEASE
Message-ID:  <801e6324-0825-4758-ad51-ea777c2834a1@acm.org>
In-Reply-To: <ce7cf86e-5da2-4cc4-a099-f807c43ec3eb@sentex.net>
References:  <0fc1d487-b254-4c64-9db1-a982169924e4@acm.org> <ce7cf86e-5da2-4cc4-a099-f807c43ec3eb@sentex.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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=
=20
> ahead of 14.2, but I dont think that makes a difference
>=20
>=20
>  =C2=A0kldstat
> Id Refs Address=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Size Name
>  =C2=A01=C2=A0=C2=A0 47 0xffffffff80200000=C2=A0 1f3d9c0 kernel
>  =C2=A02=C2=A0=C2=A0=C2=A0 1 0xffffffff8213f000=C2=A0=C2=A0 5da658 zfs.=
ko
>  =C2=A03=C2=A0=C2=A0=C2=A0 1 0xffffffff8271a000=C2=A0=C2=A0=C2=A0=C2=A0=
 36c8 coretemp.ko
>  =C2=A04=C2=A0=C2=A0=C2=A0 2 0xffffffff8271e000=C2=A0=C2=A0=C2=A0 8dae8=
 pf.ko
>  =C2=A05=C2=A0=C2=A0=C2=A0 1 0xffffffff827ac000=C2=A0=C2=A0=C2=A0=C2=A0=
 77d8 cryptodev.ko
>  =C2=A06=C2=A0=C2=A0=C2=A0 1 0xffffffff827b4000=C2=A0=C2=A0=C2=A0=C2=A0=
 3c58 pflog.ko
>  =C2=A07=C2=A0=C2=A0=C2=A0 1 0xffffffff83c20000=C2=A0=C2=A0=C2=A0=C2=A0=
 3390 acpi_wmi.ko
>  =C2=A08=C2=A0=C2=A0=C2=A0 1 0xffffffff83c24000=C2=A0=C2=A0=C2=A0=C2=A0=
 4250 ichsmb.ko
>  =C2=A09=C2=A0=C2=A0=C2=A0 1 0xffffffff83c29000=C2=A0=C2=A0=C2=A0=C2=A0=
 2178 smbus.ko
> 10=C2=A0=C2=A0=C2=A0 1 0xffffffff83c2c000=C2=A0=C2=A0=C2=A0=C2=A0 7798 =
if_bridge.ko
> 11=C2=A0=C2=A0=C2=A0 1 0xffffffff83c34000=C2=A0=C2=A0=C2=A0=C2=A0 60e0 =
bridgestp.ko
> 12=C2=A0=C2=A0=C2=A0 1 0xffffffff83c3b000=C2=A0=C2=A0=C2=A0=C2=A0 33c0 =
uchcom.ko
> 13=C2=A0=C2=A0=C2=A0 1 0xffffffff83c3f000=C2=A0=C2=A0=C2=A0=C2=A0 4e10 =
ucom.ko
> 14=C2=A0=C2=A0=C2=A0 1 0xffffffff83e00000=C2=A0=C2=A0 33e438 vmm.ko
> 15=C2=A0=C2=A0=C2=A0 1 0xffffffff83c44000=C2=A0=C2=A0=C2=A0=C2=A0 4850 =
nullfs.ko
>=20
>=20
> Starting up a vm works as before for me
>=20
>  =C2=A0vmrun.sh -t tap0 -d /baseimage/14-1VM-p6.raw -E=C2=A0 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,0=
x0)
> BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x3,=
0x0)
> Consoles: EFI console
>  =C2=A0=C2=A0=C2=A0 Reading loader env vars from /efi/freebsd/loader.en=
v
> Setting currdev to disk0p2:
> FreeBSD/amd64 EFI loader, Revision 1.1
>=20
>  =C2=A0=C2=A0 Command line arguments: loader.efi
>  =C2=A0=C2=A0 Image base: 0x1e27a000
>  =C2=A0=C2=A0 EFI version: 2.70
>  =C2=A0=C2=A0 EFI Firmware: BHYVE (rev 1.00)
>  =C2=A0=C2=A0 Console: efi (0x20001000)
>  =C2=A0=C2=A0 Load Path: \EFI\BOOT\BOOTX64.EFI
>  =C2=A0=C2=A0 Load Device: PciRoot(0x0)/Pci(0x3,0x0)/HD(2,GPT,E140336F-=
1F4D-11EF-=20
> AE18-002590EC5BF2,0x17B,0x10418)
>  =C2=A0=C2=A0 BootCurrent: 0001
>  =C2=A0=C2=A0 BootOrder: 0000 0001[*] 0002 0003 0004
>  =C2=A0=C2=A0 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-=20
> AE18-002590EC5BF2,0x17B,0x10418)
> Setting currdev to disk0p2:
> Trying: PciRoot(0x0)/Pci(0x3,0x0)/HD(1,GPT,E1403365-1F4D-11EF-=20
> AE18-002590EC5BF2,0x22,0x159)
> Setting currdev to disk0p1:
> Trying: PciRoot(0x0)/Pci(0x3,0x0)/HD(3,GPT,E1403374-1F4D-11EF-=20
> AE18-002590EC5BF2,0x10593,0x200000)
> Setting currdev to disk0p3:
> Trying: PciRoot(0x0)/Pci(0x3,0x0)/HD(4,GPT,E1403378-1F4D-11EF-=20
> AE18-002590EC5BF2,0x210593,0x11FFF6D)
> Setting currdev to zfs:zroot/ROOT/default:--=20

I may have missed defining my issue.  I thought that it was related to=20
the creation of the tap device.  It looks like a problem is with=20
virtio-net not getting loaded during the VM boot process on=20
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=20
4:0,virtio-blk,/virtual/openbsd/disk0.img -s=20
5:0,virtio-net,tap0,mac=3D58: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=20
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 =3D 0x5F22FDC1
GnuPG KeyID =3D 0x620836CF



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?801e6324-0825-4758-ad51-ea777c2834a1>