Bug 517049

Created attachment 357280 [details]
Implement bzip2 and LZMA loading of PV kernels

First cut of a patch to implement the ability to decompress bzip2 and LZMA compressed PV kernels.  It seems to work, although I haven't been able to verify 100% because the 2.6.30 kernel I'm using freezes immediately after boot (even with gzip compression, which leads me to suspect a bug in the kernel itself).  The patch itself is a little bit rough, but I'm going to post it upstream with the hopes that someone can point out where I can do things better.

Chris Lalancette

A variant of the above patch was checked into xen-unstable.hg as c/s 20103 and 20104.  So I just need to clean up the patch a bit for RHEL-5, and we should be set.

Chris Lalancette

upstream patches:

  http://xenbits.xensource.com/xen-unstable.hg?rev/a687c4d35fdd
  http://xenbits.xensource.com/xen-unstable.hg?rev/7dad2e23bf89

also filed bug #518588 to have these added to Fedora 12

Created attachment 358543 [details]
Implement bzip2 and LZMA loading of PV kernels (v2)

New version of the patch, that more closely conforms to what upstream eventually committed as xen-unstable c/s 20103 and 20116.

Tested by me with gzip, lzma, and bzip2 compressed kernels.

Check this bug on xen-3.0.3-102.el5 with follow platform and F12 kernel:
x86_64 platform (server and client)
i386 platform (server and client)
no check on ia64 platform since it doesn't support fedora 12.

The checking steps are follows:
1. Download kernel-2.6.32.2-1.fc12.src.rpm (latest f12 kernel now)
2. Install this .src.rpm and run rpmbuild
3. Change the .config file to use:
  (1)for LZMA:
      CONFIG_HAVE_KERNEL_GZIP=y
      CONFIG_HAVE_KERNEL_BZIP2=y
      CONFIG_HAVE_KERNEL_LZMA=y
      CONFIG_KERNEL_LZMA=y
  (2)for bzip2:
     CONFIG_HAVE_KERNEL_GZIP=y
     CONFIG_HAVE_KERNEL_BZIP2=y
     CONFIG_HAVE_KERNEL_LZMA=y
     CONFIG_KERNEL_BZIP2=y
4. Run "make rpm" to compile my new kernel, choose LZMA  option or bzip2 option to compress/uncompress, then get the new kernel:
    kernel-2.6.32.2.lzma-1.x86_64.rpm
    kernel-2.6.32.2bzip2-2.x86_64.rpm
    kernel-2.6.32.2LZMA-1.i386.rpm
    kernel-2.6.32.2bzip2-1.i386.rpm
5. In f12 DomU guest, install this new kernel rpm and make the initrd.img file for it.
6. Modify the grub.conf file to use new kernel as default
7. Reboot this F12 guest and boot into new kernel
8  After login, run "uname -r"
   (1)for LZMA
      you will see 2.6.32.2-LZMA
   (2)for bzip2
      you will see 2.6.32.2-bzip2
9. Reboot this guest again, then you will also boot successfully from new kernel

So this bug is fixed on xen-3.0.3-102.el5, change this bug's status to verified.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0294.html

This bug was closed during 5.5 development and it's being removed from the internal tracking bugs (which are now for 5.6).