Hi Damien, On Donnerstag, 16. Januar 2025 00:08:24 CET Damien Norris wrote: [...] > > All this left me with an incomplete grub config after xen-create-image > was finished, so pvgrub will not boot it. > > Currently xen-create-image installs 6.1.0-29 kernel (because it's not > looking at bookworm-updates by default) so this problem is recoverable; > boot in pygrub and then run "update-grub" to install grub-xen properly. > After which it's safe to update to 6.1.0-30 in the DomU. > > But as soon as a kernel >= 6.1.0-30 is installed by default (ie from > debian-security) then it will be impossible to boot or recover the new DomU. > > Is there any possibility of an updated Xen 4.17 package with the fix, or > will we have to wait for other fixes as well? > > D.
This sounds like a different issue to me as the xz compression change [1] only went into linux 6.12 and was not back-ported to 6.1. To make the version numbers a bit better understandable: 6.1.0-29 is 6.1.123-1 6.1.0-30 is 6.1.124-1 For the xz compression problem (this bug) we want to put a fix in bookworm xen in the next stable point release. We recently got informed about a different issue which should be fixed by the following patches for the kernel, but I'm also not sure this is what you are experiencing: https://lore.kernel.org/xen-devel/5c6d80bf-f090-4812-9620-5051e8ebb...@citrix.com/T/#m9800c88df2f5ed26e514142003c847b0cd766578 [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8653c909922743bceb4800e5cc26087208c9e0e6
signature.asc
Description: This is a digitally signed message part.
