bhyve on reboot loses tap(4) configuration
Bjoern A. Zeeb
bzeeb-lists at lists.zabbadoz.net
Mon Oct 15 16:14:09 UTC 2018
On 15 Oct 2018, at 16:10, Marcelo Araujo wrote:
> Em ter, 16 de out de 2018 às 00:06, Bjoern A. Zeeb <
> bzeeb-lists at lists.zabbadoz.net> escreveu:
>> I tried to use bhyve with the tap(4)/vtnet(4) solution as documented
>> the handbook (tap needs autoopen).
>> However, I am using no bridge(4) interface but a “point-to-point”
>> 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
>> 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
>> reconfigure the host interface on every guest reboot?
> Not sure if I understood well your case, but have you tried to set
> sysctl: net.link.tap.up_on_open?
That only ensures that effectively “an ifconfig tap<n> up” gets
The problem, as I assume is, if you close /dev/tap and re-open /dev/tap
it seems the configuration (interface addresses) seem to be cleaned up
More information about the freebsd-virtualization