Re: bhyve machine not starting after upgrading

2014-10-30 Thread Peter Grehan 

Hi Andrea,


I had some wonderfully working machines with bhyve with a plain
10.0-p4. I just upgraded to 10.1-RC3 and now the VMs won’t boot
anymore: they get just stuck with unable to load kernel”. After some
trials and errors I think I traced it to user boot getting confused
by a ZFS partition inside the VM.

I did some experiments with set currdev and got the kernel loaded but
then the machine just hangs.

Please give me some advice :-)


 This was reported by Craig Rodrigues a while back - the email thread is at


http://docs.freebsd.org/cgi/mid.cgi?CAG=rPVd5OQ1Gw6q-e94Ffnk_zPxkFvjaR5bpOOjMg7j-9AvSdw

 I never got around to implementing the flag to disable ZFS boot, but 
you may be able to use an alternate workaround. From your manual fix:


OK set currdev=disk0p2:
OK set rootdev=disk0p2:

 Env variables can be set from the bhyveload command line using -e 
env=value. Now, I'm not sure that currdev and rootdev can be set 
that early in the boot, but it's worth a try e.g. add these:


 -e currdev=disk0p2: -e rootdev=disk0p2:

later,

Peter.
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: bhyve machine not starting after upgrading

2014-10-30 Thread Andrea Brancatelli 
 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?
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org