Date: Wed, 28 Sep 2016 16:25:14 -0700 From: Paul Vixie <paul@redbarn.org> To: Allan Jude <allanjude@freebsd.org> Cc: The Doctor <doctor@doctor.nl2k.ab.ca>, freebsd-virtualization@freebsd.org Subject: Re: Multiple VM hosting using bhyve Message-ID: <57EC515A.9000306@redbarn.org> In-Reply-To: <705658cd-b73f-003a-884c-3c73bc9e0643@freebsd.org> References: <20160927201118.GC64360@doctor.nl2k.ab.ca> <ff64db03-c468-aa4d-a7b0-7f5999656061@freebsd.org> <20160927210207.GA34361@doctor.nl2k.ab.ca> <a25cb936-d833-4cec-b1e1-ee8940bc2347@freebsd.org> <20160927220029.GA45391@doctor.nl2k.ab.ca> <57EC4D8E.7000005@redbarn.org> <705658cd-b73f-003a-884c-3c73bc9e0643@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Allan Jude wrote: > You might also find the sysctl: > net.link.tap.up_on_open=1 > > useful, as it will re-up the tap devices when bhyve opens them. Else > rebooting a bhyve might end up with the tap interface in a down state. can do. but, that's never happened. can you tell me what "might" means? -- P Vixie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57EC515A.9000306>