Is there any way to get FreeBSD 8.1 working under bhyve? I've read
the FAQ and it says 8.4 upwards, but thought it was worth asking here
just in case it can be done just not in a supported way... :)
Thanks
___
freebsd-virtualization@freebsd.org mailing
Is there any way to get FreeBSD 8.1 working under bhyve? I've read
the FAQ and it says 8.4 upwards, but thought it was worth asking here
just in case it can be done just not in a supported way... :)
You'll need to backport the virtio drivers. There is a port that
advertizes 8.2 as the
I have VMs running on FreeBSD 10.0, for which I made zvols to provide the
block IO device for bhyve. When I boot from the installation ISO, gpart
works inside the VM, but newfs does not, reporting vtbd0 errors. Likewise,
dump does not work inside the VM (failing with too many vtbd0 hard errors),
# grep vm1 /etc/remote
vm1:dv=/dev/nmdm1B:br#9600:pa=none:
# tip vm1
Could not open backing file: No such file or directory
connected
{...I hit ENTER 5 times here...}
[1]Segmentation faultbhyve -c 2 -m 2048M -H -P -A -s
0:0,hostbridge -s 1:0,lpc -s 2:0,virtio-net,tap0 -s
Hi Rudy,
# tip vm1
Could not open backing file: No such file or directory
This is a valid error message from bhyve, and happens when the file
attached to a block device can't be opened.
connected
{...I hit ENTER 5 times here...}
This is probably the delay due to core being dumped.
Hi Aryeh,
You need to destroy the VM before creating new one with same name, so
between bhyve and bhyveload, you should use bhyvectl --destroy --vm=vm
name=t4n1ustl23. This fixed the problem Fatal trap 30: reserved (unknown)
fault while in kernel mode which I was able to reproduce on my
Just to let people know destroying it does work... now I do not need to
test PC on a production host thanks (just saved hours or headache with
this about $2k in money)
On Thu, Feb 20, 2014 at 1:44 AM, Anish Gupta akgu...@gmail.com wrote:
Hi Aryeh,
You need to destroy the VM before
