From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 8 20:39:55 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 66AFFBA1; Sun, 8 Feb 2015 20:39:55 +0000 (UTC) Received: from mail1.yamagi.org (yugo.yamagi.org [212.48.122.103]) (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 2682C80F; Sun, 8 Feb 2015 20:39:53 +0000 (UTC) Received: from p579a7a27.dip0.t-ipconnect.de ([87.154.122.39] helo=kosei.home.yamagi.org.dhcp.yamagi.org) by mail1.yamagi.org with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.85 (FreeBSD)) (envelope-from ) id 1YKY5h-000PrI-KW; Sun, 08 Feb 2015 21:04:26 +0100 Date: Sun, 8 Feb 2015 21:04:19 +0100 From: Yamagi Burmeister To: wjw@digiware.nl Subject: Re: Running grub-bhyve in the background??? Message-Id: <20150208210419.4c503d676018682f63babcc3@yamagi.org> In-Reply-To: <54D77879.2040903@digiware.nl> References: <54D6B62F.5030003@digiware.nl> <54D6BD46.6000707@freebsd.org> <54D77879.2040903@digiware.nl> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.25; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org, allanjude@freebsd.org 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:39:55 -0000 On Sun, 08 Feb 2015 15:53:45 +0100 Willem Jan Withagen wrote: > 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. I hacked around that problem by writing one bit into the nmdm device. Or to say it in code: true > $NMDMB & sleep 0.5 /usr/local/sbin/grub-bhyve -r $BOOT -m $MAP -M $MEMORY -c $NMDMA $NAME & It's not a nice solution but at least it works reliable. Regards, Yamagi -- Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB