bhyve on reboot loses tap(4) configuration

Marcelo Araujo araujobsdport at gmail.com
Mon Oct 15 16:11:06 UTC 2018


Em ter, 16 de out de 2018 às 00:06, Bjoern A. Zeeb <
bzeeb-lists at lists.zabbadoz.net> escreveu:

> Hi,
>
> I tried to use bhyve with the tap(4)/vtnet(4) solution as documented in
> the handbook (tap needs autoopen).
> However, I am using no bridge(4) interface but a “point-to-point”
> configuration.
>
> Example:
> guest configures vtnet0 to 192.0.2.2/24
> host configures tap0 to 192.0.2.1/24
>
> When rebooting the guest inside the bhyve, it seems bhyve loses the
> outside tap0 configuration.  I assume that is because the tap0 interface
> is closed and re-opened on the “warm restart”.
>
> Apart from using devd and possibly tracking tap interfaces to come up
> and track things there, is there are better solution for not having to
> reconfigure the host interface on every guest reboot?
>

Not sure if I understood well your case, but have you tried to set this
sysctl: net.link.tap.up_on_open?

Best,

-- 

-- 
Marcelo Araujo            (__)araujo at FreeBSD.org
\\\'',)http://www.FreeBSD.org <http://www.freebsd.org/>   \/  \ ^
Power To Server.         .\. /_)


More information about the freebsd-virtualization mailing list