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="freebsd" > loader="bhyveload" > cpu=1 > memory=512M > network0_type="virtio-net" > network0_switch="public" > disk0_type="virtio-blk" > disk0_name="disk0" > disk0_dev="sparse-zvol" Running "vm install -f f11b FreeBSD-11.3-RELEASE-amd64-disc1.iso", will boot the guest, but it will hang after a while with: > /boot/kernel/kernel text=0x1564b08 data=0x145330+0x4cdf30 > syms=[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="freebsd" > loader="uefi" > cpu=1 > memory=512M > network0_type="virtio-net" > network0_switch="public" > disk0_type="virtio-blk" > disk0_name="disk0" > disk0_dev="sparse-zvol" > disk1_type="ahci-cd" > disk1_dev="custom" > disk1_name="/zroot/vm/.iso/FreeBSD-11.3-RELEASE-amd64-disc1.iso" > graphics="yes" > xhci_mouse="yes" > graphics_listen="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 cursor 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@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c97f34f886624d40b8e8ff57016f3a04>