Date: Sun, 08 Feb 2015 22:25:41 +0100 From: Willem Jan Withagen <wjw@digiware.nl> To: Jason Tubnor <jason@tubnor.net> Cc: freebsd-virtualization@freebsd.org, Allan Jude <allanjude@freebsd.org> Subject: Re: Running grub-bhyve in the background??? Message-ID: <54D7D455.1030508@digiware.nl> In-Reply-To: <CACLnyCK011mmJFbA4uhbRrx8DMJo8S3r0ALxEk7h2WCRPdkN8Q@mail.gmail.com> References: <54D6B62F.5030003@digiware.nl> <54D6BD46.6000707@freebsd.org> <54D77879.2040903@digiware.nl> <CACLnyCK011mmJFbA4uhbRrx8DMJo8S3r0ALxEk7h2WCRPdkN8Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8-2-2015 21:53, Jason Tubnor wrote: > For my OpenBSD guests, I just re-direct the grub-bhyve output to > /dev/null while feeding in my step-through configuration for > grub-bhyve. > > If I know how grub-bhyve is going to behave, I don't really need to > see what is happening at that level and just hook bhyve to nmdm. I agree with the later... And connecting stdout of grub-bhyve to /dev/null would probably work as well.... Will give it a shot. --WjW > On 9 February 2015 at 01:53, Willem Jan Withagen <wjw@digiware.nl> > wrote: >> On 8-2-2015 2:35, Allan Jude wrote: >>> On 2015-02-07 20:04, Willem Jan Withagen wrote: >>>> Hi (Peter), >>>> >>>> I'm trying to run grub-bhyve completely automated but when I >>>> run my version of vmrun.sh like ../bin/bhyve-run -f >>>> /usr/local/etc/ezbhyve/Ubuntu1204A/rc.conf & >>>> >>>> Thegrub-bhyve loader waits for me to forground it again, >>>> because it wants to write to the output. Probably this is due >>>> to the use of curses, which only continues if it is actually >>>> connected to the foreground. >>>> >>>> ==== + /usr/local/sbin/grub-bhyve -e -vvv -r hd0,msdos1 -m >>>> ./ubuntu-12.04.map -M 2048M ubuntu-12.04.1 >>>> >>>> [2] + Suspended (tty output) ../bin/bhyve-run -f >>>> /usr/local/etc/ezbhyve/Ubuntu1204A/rc.conf ==== >>>> >>>> Is it possible on the commandline to get grub-bhyve to >>>> continue regardless the backgrounded state? >> >>> In newer versions of the bhyve loader, you can redirect the >>> output to a nmdm (null modem) device, so it can run unattended >> >> bhyveloader does work like this. And even if there is nobody to >> listen to the loader, things to continue. It just takes 10 sec. >> >> But once in a while I have trouble getting grub-bhyve to act the >> same. If I connect it to a nmdm-device it just waits for me to >> connect. And if I do not specify a device, it is nog possible to >> run it in the background. >> >> A inbetween sulution at the moment is to run grub-bhyve -c >> /dev/null. That continues, dus does not offer the possibility to >> interfere in the boot process. At least not for my ubuntu-12.04 >> VMs. >> >> So a flag with grub-bhyve to not require a forground process, or >> even better: ignore flowcontrol on the -c device, would be nice. >> >> --WjW _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To >> unsubscribe, send any mail to >> "freebsd-virtualization-unsubscribe@freebsd.org" > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54D7D455.1030508>