Date: Sat, 9 Jan 2016 17:58:28 -0600 From: "barasingha" <barasingha@crossedbar.com> To: <freebsd-virtualization@freebsd.org> Subject: RE: bhyve won't let go Message-ID: <000d01d14b39$a3e46b50$ebad41f0$@com> In-Reply-To: <5691662B.30006@freebsd.org> References: <000001d14b17$478b0840$d6a118c0$@com> <5691662B.30006@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Problem solved. Thanks. Barasingha -----Original Message----- From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freebsd-virtualization@freebsd.org] On Behalf Of Allan Jude Sent: Saturday, January 09, 2016 1:58 PM To: freebsd-virtualization@freebsd.org Subject: Re: bhyve won't let go On 2016-01-09 14:52, barasingha wrote: > I am running 10.2 Release. > > > > I am running pfsense as a guest of bhyve. Using passthru, pfsense is > given > 2 nics. I wish to run the vm headless. > > > > I have written a rc script and can use the script to manually control > the vm or enable it to run at bootup. > > > > The problem is that I can't get both the guest and host to run at > boot. If vm is enabled, bootup hangs once bhyve is called. In this > scenario I can ssh into pfsense but not into the host. If I halt the > vm the host will finally continue to boot. > > > > When controlled manually the same thing happens, however I can then > open another shell to provide host control. > > > > sample: > > bhyveload -m 4G -c /dev/nmdm0A -d /directory/to/boot/disk name > > bhyve -c 2 -m 4G -A -H -P \ > > -s 0,hostbridge \ > > -s 1,lpc \ > > -s n,others \ > > -l com1, /dev/nmdm0A \ > > name > > > > Any ideas? I think I have a problem in /etc/ttys on either the host or vm. > > > > Thanks, > > Barasingha > > > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" > The bhyve command doesn't exit until the VM shuts down. Have your rc script that runs at startup, run vmrun or whatever you are doing via 'daemon' or something, so it goes into the background. -- Allan Jude
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000d01d14b39$a3e46b50$ebad41f0$>