From owner-freebsd-virtualization@freebsd.org Sun Aug 26 05:55:04 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF80A10120E5 for ; Sun, 26 Aug 2018 05:55:04 +0000 (UTC) (envelope-from vixie@fsi.io) Received: from mail.fsi.io (mail.fsi.io [104.244.13.176]) (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 74A1F72725; Sun, 26 Aug 2018 05:55:04 +0000 (UTC) (envelope-from vixie@fsi.io) X-Virus-Scanned: amavisd-new at fsi.io Sender: vixie@fsi.io Received: from linux-9daj.localnet (dhcp-181.access.lah1.vix.su [24.104.150.181]) (Authenticated sender: vixie) by mail.fsi.io (Postfix) with ESMTPSA id 0EB8D609BF; Sun, 26 Aug 2018 05:54:48 +0000 (UTC) From: Paul Vixie To: freebsd-virtualization@freebsd.org Subject: Re: Query regarding tutorials (Please have a quick read of me!) Date: Sun, 26 Aug 2018 05:54:47 +0000 Message-ID: <5449454.ijkHvH96lN@linux-9daj> Organization: Farsight Security, Inc. In-Reply-To: References: <6699362.kGnQbBhLUH@linux-9daj> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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, 26 Aug 2018 05:55:05 -0000 On Sunday, August 26, 2018 2:46:42 AM UTC Allan Jude wrote: > On 2018-08-25 13:45, Paul Vixie wrote: > > ... i remain > > mystified by the behaviour of grub-bhyve, which usually fails (no > > meaningful error message) and seems like won't run from /etc/rc.local > > (must be run from a shell.) so, one of my bhyve servers can't restart > > automatically, and i don't know why. ... > What does the invocation look like? grub-bhyve -r $defdev -m $vm.map -M $pm -c /dev/$sc $vm \ > ${vm}.output 2>&1 \ || { echo "grub-bhyve failed" >&2; exit 1; } > Does this work: > printf "\n" | grub-bhyve ...your-stuff-here... i'll give it a try. testing this particular path requires a reboot, and the system is otherwise running in production... so give me a day or two. > > As an alternative, you can now use the UEFI_CSM firmware for bhyve, and > it'll boot from the boot blocks inside the VM, like xen/kvm/qemu/virtualbox this sounds far preferable! is there an example or other documentation? -- Vixie