Bug#903821:

On Fri, 2018-07-20 at 10:53 +0200, Wiebe Cazemier wrote: > Hi, > > Yesterday, it was already due to be installed on FTP. When is that? > Because of the delay, I caused our Xen server to get stuck into a > kernel panic reboot loop after upgrading and rebooting Jul 19 23:00 > UTC. It was actually

Bug#903821:

Hi, Yesterday, it was already due to be installed on FTP. When is that? Because of the delay, I caused our Xen server to get stuck into a kernel panic reboot loop after upgrading and rebooting Jul 19 23:00 UTC. It was actually during an upgrade from Debian 8 to 9 and I had no older 4.9 kernel,

Bug#903821: marked as done (xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64))

Your message dated Thu, 19 Jul 2018 19:17:39 + with message-id and subject line Bug#903767: fixed in linux 4.9.110-2 has caused the Debian Bug report #903767, regarding xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64) to be marked as done.

Bug#903821: 4.9.112 boots with Xen PV

I can confirm that a build of the 4.9 series against 4.9.112 boots under Xen PV with the following patches removed: --- linux-4.9.110/debian/patches/series 2018-07-15 18:05:38.614069505 + +++ linux-4.9.112/debian/patches/series 2018-07-16 03:22:09.551240940 + @@ -12,7 +12,6 @@

Bug#903821: [Pkg-xen-devel] Bug#903821: linux-image-4.9.0-7-amd64: Can not boot 4.9.0_7_amd64 with Xen

I’ll pile on top of this: domUs crash with the kernel as well, with a GPF. Looks like any Xen + 4.9.0-7 = Crash, regardless of it being a domU or dom0. John > On 15 Jul 2018, at 21:55, Sebastien KOECHLIN wrote: > > Package: src:linux > Followup-For: Bug #903821 > > When bo

Bug#903821: 4.9.110-1 Xen PV boot workaround

I've tested the workaround successfully. Added `pti=off` to my kernel's boot arguments, updated GRUB, and it started as intended. Benoît, Just to be sure, since you're loading your guests' kernels directly like that, you're passing pti=off via the `extra` config line in your domU config files,

Bug#903821: 4.9.110-1 Xen PV boot workaround

Reportedly, adding pti=off to the kernel boot parameters will work around the issue for now. Turning off pti in the guest kernel is done in any case for PV. The issue between 4.9.107 and 4.9.111 affects the detection and turning off of pti, that's why forcing it off helps. In 4.9.112 it's fixed

Bug#903821: [Pkg-xen-devel] Bug#903821: xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64)

Hi, On 07/15/2018 12:16 PM, Benoît Tonnerre wrote: > [...] > > After updating 3 Xen servers from stretch (9.4) to stretch (9.5), I > notice a kernel panic on these 3 servers. Thanks for the report. This is probably all related: This went into 4.9.102:

Bug#903821: 4.16 kernel

Hi, Thanks your report! I can start my system with 4.16 backport kernel.

Bug#903821: linux-image-4.9.0-7-amd64: Can not boot 4.9.0_7_amd64 with Xen

Package: src:linux Followup-For: Bug #903821 When booting with the new kernel, I got the following Dom0 crash: Loading Xen 4.8-amd64 ... Loading Linux 4.9.0-7-amd64 ... Loading initial ramdisk ... (XEN) Xen version 4.8.4-pre (Debian 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9) (ijack

Bug#903821: Re : xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64)

Hi, If you prefer, you can find a kernel panic screenshot from R720 Dell server's : https://s33.postimg.cc/b2t056y8f/S_lection_027.png Best regards Benoît

Bug#903821: xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64)

Package: xen-hypervisor-4.8-amd64 Version: 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9 Severity: critical Justification: breaks the whole system Dear Maintainer, After updating 3 Xen servers from stretch (9.4) to stretch (9.5), I notice a kernel panic on these 3 servers. If I boot xen hypervisor