On Mon, May 03, 2021 at 10:46:34PM +0200, Juraj Lutter wrote: > Hi, > > my bhyve command line (on 13.0-RELEASE) is: > > /usr/sbin/bhyve -c 2 -m 4G -H -A -P -u -s 0:0,hostbridge -s 1:0,lpc -s > 2:0,virtio-net,tap100 -s 3:0,virtio-net,priv0 -s > 4:0,virtio-blk,/dev/zvol/zroot/data/minio/host0/root -l com1,/dev/nmdm100B mr > > the result is: > > device emulation initialization error: File exists > > It works when using original interface name (tap105 in this case). > > priv0 is renamed tap: > priv0: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=80000<LINKSTATE> > ether 58:9c:fc:10:2b:0b > groups: tap > media: Ethernet autoselect > status: no carrier > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > > Am I doing something inadequate, is this an expected behavior or is this a > kind of a bug?
Unfortunately, bhyve doesn't support renamed tap devices. You'll need to keep the original tapN name. What you might want to experiment with is setting a description for the tap device. For example: ifconfig tapN description "private vNIC" Thanks, -- Shawn Webb Cofounder / Security Engineer HardenedBSD https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc
signature.asc
Description: PGP signature
