Re: bhyve's VM loose network connectivity after a reboot

2014-08-21 Thread Olivier Cochard-Labbé
On Thu, Aug 21, 2014 at 5:26 PM, Peter Grehan  wrote:

> Hi Olivier,
>
>  Do you have the net.link.tap.up_on_open sysctl set to 1 ? (didn't see
> that in the BSDRP-lab-bhyve.sh script, if that's the one you're using)
>
>
> Yes I was using the BSDRP-lab-bhyve.sh script and correctly setting
net.link.tap.up_on_open fix my problem: Thanks !

Olivier
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: bhyve's VM loose network connectivity after a reboot

2014-08-21 Thread Peter Grehan

Hi Olivier,


I'm using bhyve from a 11.0-CURRENT (r270177) host and I meet a problem
after a VM (guest using fbsd -current too) is rebooted: This VM loose
network connectivity once rebooted.
vtnet interface seems OK from the VM, like the tap interface on the host:
tap status correctly display the new bhyve PID number in its "Opened by"
section.

But this VM didn't send packet anymore: a "tcpdump -i tap-interface" from
the host didn't show any packet after a reboot.

Is there something special to do in the "while [ 1 ]" loop of my script,
other than simply restarting bhyve for fixing this issue ?


 Do you have the net.link.tap.up_on_open sysctl set to 1 ? (didn't see 
that in the BSDRP-lab-bhyve.sh script, if that's the one you're using)


later,

Peter.

___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"