From owner-freebsd-virtualization@FreeBSD.ORG Thu Oct 30 23:35:37 2014 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 627B7854 for ; Thu, 30 Oct 2014 23:35:37 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 22F94274 for ; Thu, 30 Oct 2014 23:35:36 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTP id 76EB0123AB; Fri, 31 Oct 2014 09:35:34 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local (c-67-161-27-37.hsd1.ca.comcast.net [67.161.27.37]) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id BZI42815 (AUTH peterg@ptree32.com.au); Fri, 31 Oct 2014 09:35:33 +1000 Message-ID: <5452CB43.8000602@freebsd.org> Date: Thu, 30 Oct 2014 16:35:31 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Andrea Brancatelli Subject: Re: bhyve machine not starting after upgrading References: <5452B8D4. 4070204@freebsd.org> <7931E297-104B-4BCA-BA08-D425DE7D85A7@schema31.it> <62FFE74F-E824-4159-A953-2080D40535A1@schema31.it> In-Reply-To: <62FFE74F-E824-4159-A953-2080D40535A1@schema31.it> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@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: Thu, 30 Oct 2014 23:35:37 -0000 Hi Andrea, > Mmmm Peter, the -e seems to be totally ignored. Ok, looks like the ZFS probe code will override those :( > Type '?' for a list of commands, 'help' for more detailed help. > OK show > LINES=24 > boot_serial=1 > console=userboot > currdev=zfs:repository: > interpret=OK > loaddev=zfs:repository: > prompt=${interpret} > rootdev=disk0p2 > smbios.bios.vendor=BHYVE > OK How about if you set loaddev to disk0p2, and see if that allows a boot ? Another solution, though not pretty, is to build a version of userboot that doesn't have ZFS enabled. Modify sys/boot/userboot/userboot/Makefile and remove the MK_ZFS section, and copy userboot.so from the build to /boot/userboot.so and the host. This should give you back the behaviour from 10.0. later, Peter.