Bug#1102066: Workarounds

[Nagy Elemér Károly]

Dear All!

A previously mentioned workaround is to recompile the DomU kernel with
xz compression.

Another workaround is to not use pvgrub but make Xen boot the kernel
directly by changing the xl conf file to something like:
 kernel="/root/xen/images/debian13/devdev/incoming/latest_vmlinuz"
 ramdisk="/root/xen/images/debian13/devdev/incoming/latest_initrd"
 extra='root=UUID=b37347d8-3217-4a1b-81a7-5bc9f64ae059 ro
ipv6.disable=1 noacpi nolapic quiet'

For this, the kernel and the initrd file must be copied from DomU to
Dom0 (and after each kernel upgrade, it must be re-done), so it's less
convenient, but can be scripted and is working well. The package
needrestart is helpful to remind you about this additional step ;)

Another workaround is to use HVM mode, but that has severe performance
penalties.

I built a grub-x86_64-xen.bin with current grub (2.13) but even that
has the same problem as the version in trixie, so I will try to
contact the grub developers to move this issue forward.

Alternatively, is there a chance to have a linux-image-amd64-xz or
linux-image-cloud-amd64-xz or to switch linux-image-cloud-amd64 back
to xz?

Best wishes:
Elmar