Date: Thu, 07 May 2020 08:43:18 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 246168] Ubuntu 20.04 KVM / QEMU Failure with nested FreeBSD bhyve Message-ID: <bug-246168-27103-9aTwLoGnKo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-246168-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-246168-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246168 --- Comment #8 from Peter Grehan <grehan@FreeBSD.org> --- I was able to get this working fine, and the cause of the problem is clear looking back at the posted logs. <<START LAYER 2 GUEST START>> # ls FreeBSD-11.2-RELEASE-amd64-bootonly.iso FreeBSD-12.1-RELEASE-amd64-dvd1.iso= =20=20=20=20 bee-hd1-01.img # /usr/sbin/bhyve -c 2 -m 2048 -H -A -s 0:0,hostbridge -s 1:0,lpc -s 2:0,e1000,tap0 -s 3:0,ahci-hd,bee-hd1-01.img -l com1,stdio -s 5:0,ahci-cd,./FreeBSD-12.1-RELEASE-amd64-dvd1.iso bee bhyve has to be started with either a UEFI ROM image, or using a separate loader (bhyveload/grub-bhyve). This wasn't done in this case, which will re= sult in registers partly set to power-on state, which will result in a triple-fa= ult or some other error. This can be seen in the register dump from KVM, where all the GP registers = are zero including the RIP. The fix to run a FreeBSD guest is to use bhyveload before running bhyve. For the example given, this would be # /usr/sbin/bhyveload -m 2048 -d ./FreeBSD-12.1-RELEASE-amd64-dvd1.iso bee ... and then run the bhyve command. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246168-27103-9aTwLoGnKo>