Date: Fri, 20 Sep 2013 23:37:38 -0700 From: Michael Dexter <editor@callfortesting.org> To: freebsd-virtualization@freebsd.org Subject: Re: bhyve bug report: creating a if_bridge on guest freezes guest Message-ID: <523D3EB2.7030900@callfortesting.org> In-Reply-To: <CAGBxaXnerTZO2G2Ubu4%2Bj9DmQFt-YVHUUFqhAqqAkbS_SDWcRw@mail.gmail.com> References: <CAGBxaXnerTZO2G2Ubu4%2Bj9DmQFt-YVHUUFqhAqqAkbS_SDWcRw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/20/13 10:04 PM, Aryeh Friedman wrote: > if I have something like: > > ifconfig bridge0 create > ifconfig bridge0 addm vtnet0 up > > the second ifconfig will just freeze the guest up (host is unaffected) vtnet0 is only visible from within a guest, not on the host. Here are the steps I use: Run once on the host before all guests: ifconfig bridge0 create Run on the host for each guest with different tap# numbers: ifconfig tap5 down ifconfig tap5 destroy ifconfig tap5 create ifconfig bridge0 addm tap5 addm em0 up ifconfig tap5 up em0 is the hardware interface on the host. Note that this will not work with a wireless interface unless you manually set some routes with pf. What is the bug? Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?523D3EB2.7030900>