Hello,
https://paste.debian.net/1077718/
I get a kernel panic as shown in the paste above no matter how I
launch pvh, with bootloader (pygrub), kernel direct (4.18+), or
pvgrub2 (i386-xen_pvh support).
The dom0 here is ub1804, kernel-4.18, and xen-4.12 with debian
packages (self built).
~$ sudo dpkg -l | grep -P 'xen|qemu' | grep '^ii'
ii libxen-4.12:amd64 4.12.0-1+ub18u04.1 amd64
Public libs for Xen
ii libxenstore3.0:amd64 4.12.0-1+ub18u04.1 amd64
Xenstore communications library for Xen
ii libxentoolcore1:amd64 4.12.0-1+ub18u04.1 amd64
helper for qemu & libxenstore
ii qemuu 3.1.0-1+ub18u04.1 amd64
qemu-system-i386 (3.1.0/xen-4.12) with 9pfs support
ii xen-hypervisor-4.12-amd64 4.12.0-1+ub18u04.1
amd64 Xen Hypervisor on AMD64
ii xen-utils-4.12 4.12.0-1+ub18u04.1
amd64 XEN administrative tools
ii xen-utils-common 4.12.0-1+ub18u04.1
all Xen administrative tools - common files
ii xen-virbr0 0.1-2
all Setup a virbr0 bridge and dnsmasq on a
ii xenstore-utils 4.12.0-1+ub18u04.1
amd64 Xenstore command line utilities for Xen
The same xl config and grub config works in xen-4.11.1. I've searched
for any new options in xl.cfg that could influence this, but nothing
catches my eye.
I get the same dmesg in other boot methods, but the i386-xen_pvh style
yields more info at the end. The (fire-missle) grub script is provided
Hans van Kranenburg .
Before the initrd unpacks I see many errors (line 201 of paste):
fuse init modprobe trap invalid opcode ip:7f797dc7bb95
But later the xen_netfront and xen_blkfront drivers load fine and then
trouble starts.
PryMar56,
##xen-packaging on Freenode IRC
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
