[Pkg-xen-devel] Bug#519149: xen-3: does not really load bzImage kernels.

[William Pitcock]

Package: xen-hypervisor-3.2-1-amd64
Version: 3.2.1-2
Severity: serious

After noting that this version supposedly loads bzImage kernels:

| xen-3 (3.2.1-2) unstable; urgency=low
| 
|   * Use e2fslibs based ext2 support for pygrub. (closes: #476366)
|   * Fix missing checks in pvfb code.
|     See CVE-2008-1952. (closes: #487095)
|   * Add support for loading bzImage files. (closes: #474509)
|   * Enable TLS support in ioemu code.
|   * Drop libcrypto usage because of GPL-incompatibility.
|   * Remove AES code from blktap drivers. Considered broken.

I thought I might give it a try (right now I am running on xen-3.4 hg), 
to see if I couldn't run the paravirt-ops work in production.

Seems I can't, as it complains that the kernel is not a valid ELF image. 
But this image works under 3.4, as I am using it right now.

As the paravirt-ops work is the future of dom0 support, it is probably a 
good idea to fix this in squeeze.

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-rc7-tip-0-pvopsxen0-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

xen-hypervisor-3.2-1-amd64 depends on no packages.

Versions of packages xen-hypervisor-3.2-1-amd64 recommends:
ii  xen-utils-3.2-1               3.2.1-2    XEN administrative tools

Versions of packages xen-hypervisor-3.2-1-amd64 suggests:
pn  xen-docs-3.2                  <none>     (no description available)

-- no debconf information