Date: Fri, 31 Oct 2014 01:05:07 +0100 From: Andrea Brancatelli <abrancatelli@schema31.it> To: Peter Grehan <grehan@freebsd.org> Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve machine not starting after upgrading Message-ID: <3C8C9082-8C66-4B52-8763-DCD3A9ACE408@schema31.it> In-Reply-To: <5452CB43.8000602@freebsd.org> 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> <5452CB43.8000602@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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 ?
“loaddev" seems to be a read only property… :(
> 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.
OK, I had no sources to compile so I did a very bad thing and I know I’ll go in hell for this but…
I copied userboot.so from another FreeBSD 10.0 machine and substituted /boot/userboot.so from the host. Restarted the VM and it worked like a charm.
You’re going to fix this before 10.1 final, RIGHT?? :-)
Do you think this modification may result in a non-booting host machine?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C8C9082-8C66-4B52-8763-DCD3A9ACE408>