affects 1050030 src:xen quit I'm seeing a similar situation, though instead using FreeBSD/x86 in the VM.
For FreeBSD the bootloader appears to operate normally, but something fails quickly after loading the kernel: Loading kernel... /boot/kernel/kernel text=0x18aa98 text=0xdfd150 text=0x675154 data=0x140 data=0x1c38e8+0x43b718 0x8+0x18fe70+0x8+0x1ae449/ Loading configured modules... /boot/entropy size=0x1000 /etc/hostid size=0x25 staging 0xe3e00000 (not copying) tramp 0xe351b000 PT4 0xe3512000 Start @ 0xffffffff8038b000 ... EFI framebuffer information: addr, size 0xf0000000, 0x1d5000 dimensions 800 x 600 stride 800 masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 I believe all these messages are from FreeBSD's bootloader. The first message from the kernel should be "---<<BOOT>>---", yet that message never shows. Xen shows the domain spinning on a single processor which makes me believe the FreeBSD kernel has loaded, panic()ed and the debugger is loaded (but there is no VGA console). >From reading the available information I suspect Tianocore/EDK2 may have tried to move some functionality to a distinct build and neither setup quite works. Notably there is now a "OvmfPkg/OvmfXen.dsc" build configuration. The OVMF.fd for Qemu for Xen functionality may have been moved /here/. There might also be an attempt at functionality similar to "ArmVirtPkg/ArmVirtXen.dsc" (Debian 978595) for x86. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
