From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 8 20:53:38 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 8089D7D2; Sun, 8 Feb 2015 20:53:38 +0000 (UTC) Received: from mail-yk0-x22e.google.com (mail-yk0-x22e.google.com [IPv6:2607:f8b0:4002:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C50C9C2; Sun, 8 Feb 2015 20:53:38 +0000 (UTC) Received: by mail-yk0-f174.google.com with SMTP id 9so4498651ykp.5; Sun, 08 Feb 2015 12:53:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=GW0PtphFpnHAvOEYvP5+27FwcyjM6aV0ry3ifDP9icE=; b=aDjz1BDlgFqQ/+Lyyvpj2zoXQ/LGOzfEV0RIBWs6hwyW7h0cQBn+LriD05AlexK/k+ 8l7RhIMBo6QrhIw/vqUXkL7K6jwbfgxMxLo/wEivhXR5VteS0GmaCbpvmfqiUQA0sMFV fNS73MiS+TOr1ITlUcgLYftl0t9XN4F6tAMUjTKF/vcAHbuB7DU+f94OR+km8ntHX3Aa THyFTS4+F19b9a8cA4aJ4pCQ6eqFl99DIaOAf/XAhyTasvMw147tIRg3+BrHqF/WbM38 MrfiIy/e1jK3oj2QQiYjOx5RBtY4Lj66gcujoPjBYeMTz/VT35rmFVQg+auPEXfrnenr hsuw== X-Received: by 10.236.191.230 with SMTP id g66mr4814972yhn.29.1423428817359; Sun, 08 Feb 2015 12:53:37 -0800 (PST) MIME-Version: 1.0 Sender: jtubnor@gmail.com Received: by 10.170.60.148 with HTTP; Sun, 8 Feb 2015 12:53:17 -0800 (PST) In-Reply-To: <54D77879.2040903@digiware.nl> References: <54D6B62F.5030003@digiware.nl> <54D6BD46.6000707@freebsd.org> <54D77879.2040903@digiware.nl> From: Jason Tubnor Date: Mon, 9 Feb 2015 07:53:17 +1100 X-Google-Sender-Auth: FXRVOpGjZXX876aoAZbWDrF0o-4 Message-ID: Subject: Re: Running grub-bhyve in the background??? To: Willem Jan Withagen Content-Type: text/plain; charset=UTF-8 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 20:53:38 -0000 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. 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" -- "Roads? Where we're going, we don't need roads" - Dr. Emmett "Doc" Brown