Bug#1041533: Root Cause is probably related to a linking issue

found 1041533 4.17.3+10-g091466ba55-1~deb12u1 Hello all, This bug also affects me, with the same symptoms and setup that were described earlier: root@hypervisor:~# cat /var/log/xen/qemu-dm-vm.log xen-qemu-system-i386: -vnc :0,password=on,to=99: Cipher backend does not support D

Bug#1017944: Also affects PVH DomUs

Severity: grave I have just confirmed that this bug also seems to affect PVH DomUs, failing with: root@hypervisor:~# xl dmesg -c (XEN) MMIO emulation failed (1): d69v0 32bit @ :3fff -> 00 (XEN) d69v0 Triple fault - invoking HVM shutdown action 1 (XEN) *** Dumping Dom69 vcpu#0 state: ***

Bug#1017944: grub-xen-host: 2.06-3 crashes PV guests in early boot

Package: grub-xen-host Version: 2.06-3 When used as `kernel` for a PV guest, the VM fails to boot immediately: # xl dmesg root@hypervisor:~# xl dmesg -c (XEN) printk: 3 messages suppressed. (XEN) d163v0 Unhandled page fault fault/trap [#14, ec=0003] (XEN) Pagetable walk from 0062702c: (XE

Bug#871702: Latest Stretch qemu-system-i386 process balloons in Xen Dom0 RAM, crashes DomU

deb9u1. On 1:2.8+dfsg-6+deb9u2, my Windows 7 x64 VM used 4GiB of Dom0 during setup and at least 1GiB for "normal operation" (slowly growing). Now, using 1:2.8+dfsg-6+deb9u1, QEMU consumes about 40MiB of Dom0 which is a lot better. Hope this helps to narrow down the issue. -- Best regards Thomas Keppler