From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 8 21:26:11 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 694965B0; Sun, 8 Feb 2015 21:26:11 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 27F70D5C; Sun, 8 Feb 2015 21:26:10 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id BDD7D16A403; Sun, 8 Feb 2015 22:26:07 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fs7BWGwyjcYq; Sun, 8 Feb 2015 22:25:41 +0100 (CET) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 3935216A401; Sun, 8 Feb 2015 22:25:41 +0100 (CET) Message-ID: <54D7D455.1030508@digiware.nl> Date: Sun, 08 Feb 2015 22:25:41 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Jason Tubnor Subject: Re: Running grub-bhyve in the background??? References: <54D6B62F.5030003@digiware.nl> <54D6BD46.6000707@freebsd.org> <54D77879.2040903@digiware.nl> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org, Allan Jude X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2015 21:26:11 -0000 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 > 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" > > >