From owner-freebsd-virtualization@freebsd.org Sun Nov 12 10:45:12 2017 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B4C2E6EC5E for ; Sun, 12 Nov 2017 10:45:12 +0000 (UTC) (envelope-from me@cschwarz.com) Received: from orion.uberspace.de (orion.uberspace.de [95.143.172.79]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DFB1B63A6F for ; Sun, 12 Nov 2017 10:45:10 +0000 (UTC) (envelope-from me@cschwarz.com) Received: (qmail 32287 invoked from network); 12 Nov 2017 10:45:07 -0000 Received: from localhost (HELO csarch) (127.0.0.1) by orion.uberspace.de with SMTP; 12 Nov 2017 10:45:07 -0000 Message-ID: <1510483505.13439.16.camel@cschwarz.com> Subject: Re: grub-bhyve: support overriding just --root flag From: Christian Schwarz To: freebsd-virtualization@freebsd.org Date: Sun, 12 Nov 2017 11:45:05 +0100 In-Reply-To: <161c3f27-41fd-ada6-4edb-b8d2b3c1dc48@freebsd.org> References: <1510414698.13439.8.camel@cschwarz.com> <161c3f27-41fd-ada6-4edb-b8d2b3c1dc48@freebsd.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 12 Nov 2017 10:45:12 -0000 Hi Alan, > Does libvirt support using the bhyve UEFI-CSM firmware instead? That > would let the VM boot using the native grub installed inside the VM, and > avoid this issue entirely. It also makes starting a bhyve a single > command instead of 2. Thanks for the tip, I just converted the disk to GPT and now use UEFI directly. The only problem I encountered with the UEFI firmware is that it will always prefer the virtualized cdrom over hdd or, more generally, one cannot define a boot order. This gist contains a working minimal UEFI-only libvirt domain: https://gist.github.com/problame/79a94ae05f5b17e11c3b5bc2fe5910c8 If you have any idea how to set the boot order via bhyve command line flags I would be "happy" to patch libvirt to support this feature. Otherwise, I hope this helps anyone reading this in the future, Christian