Date: Thu, 30 Oct 2014 16:35:31 -0700 From: Peter Grehan <grehan@freebsd.org> To: Andrea Brancatelli <abrancatelli@schema31.it> Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve machine not starting after upgrading Message-ID: <5452CB43.8000602@freebsd.org> In-Reply-To: <62FFE74F-E824-4159-A953-2080D40535A1@schema31.it> References: <D136FCF3-2BAB-4F9D-B109-792F69BFB47A@schema31.it> <5452B8D4. 4070204@freebsd.org> <7931E297-104B-4BCA-BA08-D425DE7D85A7@schema31.it> <62FFE74F-E824-4159-A953-2080D40535A1@schema31.it>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5452CB43.8000602>