Date: Mon, 2 Mar 2020 09:26:07 +0000 From: Matt Churchyard <matt.churchyard@userve.net> To: Andrea Venturoli <ml@netfence.it>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: RE: Cannot run FreeBSD 11 as a vm-bhyve guest under FreeBSD 12 Message-ID: <c97f34f886624d40b8e8ff57016f3a04@SERVER.ad.usd-group.com> In-Reply-To: <0114f8c1-950d-d61c-db63-5ed11fd1ddd4@netfence.it> References: <0114f8c1-950d-d61c-db63-5ed11fd1ddd4@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello.
I'd like to run a FreeBSD 11.3 VM under FreeBSD 12.1.
As I'm already using vm-bhyve to run a Windows guest, I think the best (or =
possibly only) choice is to use bhyve for the FreeBSD guest too.
I've got the following conf file:
> guest=3D"freebsd"
> loader=3D"bhyveload"
> cpu=3D1
> memory=3D512M
> network0_type=3D"virtio-net"
> network0_switch=3D"public"
> disk0_type=3D"virtio-blk"
> disk0_name=3D"disk0"
> disk0_dev=3D"sparse-zvol"
Running "vm install -f f11b FreeBSD-11.3-RELEASE-amd64-disc1.iso", will boo=
t the guest, but it will hang after a while with:
> /boot/kernel/kernel text=3D0x1564b08 data=3D0x145330+0x4cdf30=20
> syms=3D[0x8+0x16daf0+0x8+0x186a43] Booting...
> |
"vm stop" will stop it (through an ACIP shutdown) after a while.
So I tried with UEFI; here's the config file:
> guest=3D"freebsd"
> loader=3D"uefi" =
=20
> cpu=3D1
> memory=3D512M
> network0_type=3D"virtio-net"
> network0_switch=3D"public"
> disk0_type=3D"virtio-blk"
> disk0_name=3D"disk0"
> disk0_dev=3D"sparse-zvol"
> disk1_type=3D"ahci-cd"
> disk1_dev=3D"custom"
> disk1_name=3D"/zroot/vm/.iso/FreeBSD-11.3-RELEASE-amd64-disc1.iso"
> graphics=3D"yes"
> xhci_mouse=3D"yes"
> graphics_listen=3D"192.168.xxx.1"
Starting it with "vm start" and connecting through VNC, it goes through the=
same stages as above, but ends up with a blank screen with a white block c=
ursor in the first column of the first row.
>Any hint on how to get past this?
This is likely caused by an issue in the way vm-bhyve handled stdio, which =
only worked correctly with older builds of bhyve.
I would recommend installing vm-bhyve from ports (you should get version 1.=
4.2), which hopefully will boot using bhyveload with no issues.
Matt
> bye & Thanks
> av.
_______________________________________________
>>freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org=
/mailman/listinfo/freebsd-virtualization
>To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freeb=
sd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c97f34f886624d40b8e8ff57016f3a04>