[Bug 247636] Ubuntu 18.04 & 20.04 guest kernel panic on boot with 12.1 bhyve + graphical UEFI
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Jun 29 13:52:14 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247636
Bug ID: 247636
Summary: Ubuntu 18.04 & 20.04 guest kernel panic on boot with
12.1 bhyve + graphical UEFI
Product: Base System
Version: 12.1-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: bhyve
Assignee: virtualization at FreeBSD.org
Reporter: drum at graphica.com.au
Created attachment 216037
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216037&action=edit
Screen shot of kernel panic
BUG:
Setup: Nested virtualisation with: Layer 0 - Ubuntu 20.0 KVM, Layer 1 - FreeBSD
12.1 with bhyve and UEFI, Layer 2 - Ubuntu 18.04 & 20.04 Guest VM
Observered Behaviour:
Starting both Ubuntu 20.04 & 18.04 (Server & Desktop CD-ROMs) VM with bhyve on
FreeBSD 12.1 results in VM crashing with kernel panic.
(see attachment for UEFI VNC screen shot)
Expected Behaviour:
Ubuntu CD Install Boot to allow installation onto HD image.
DIAGNOSTICS:
I have done extensive testing of nested virtualisation:
Layer 0 - Ubuntu 20.04 with QEMU / KVM / libvirt
Layer 1 - FreeBSD 12.1 with OVMF Guest running bhyve hypervisor
Layer 2 - Guest Testing:
Layer 2 - FreeBSD 12.1 with UEFI rom + serial console - WORKS
Layer 2 - FreeBSD 12.1 with UEFI rom + graphical boot - WORKS
Layer 2 - Ubuntu 20.04 Server & Desktop with UEFI rom + graphical boot - FAILS
Layer 2 - Ubuntu 18.04 Server & Desktop with UEFI rom + graphical boot = FAILS
Bhyve command line:
# bhyve -c2 -m 2048 -H -A -s 0:0,hostbridge -s 1:0,lpc -s 2:0,e1000,tap0 -s
3:0,ahci-hd,./VM_DSK.img -s 4:0,ahci-cd,./ubuntu-18.04.4-live-server-amd64.iso
-s 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s 30,xhci,tablet -l com1,stdio
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd VM_NAME
I have documented my testing extensively here:
https://tips.graphica.com.au/freebsd-virtualisation-with-bhyve/
My configuration included work around to disable "virtual interrupt delivery"
as this was required to get FreeBSD nested guest to boot successfully.
See bug report here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246168
Happy to do other testing as required.
Thank you for any tips/advise/help/
Regards,
John Hartley.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-virtualization
mailing list