William Pitcock
2009-Mar-10 17:23 UTC
[Pkg-xen-devel] Bug#519149: xen-3: does not really load bzImage kernels.
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
Debian Bug Tracking System
2009-Nov-22 15:57 UTC
[Pkg-xen-devel] Bug#519149: marked as done (xen-3: only loads bzImage domU kernels, not dom0)
Your message dated Sun, 22 Nov 2009 16:43:15 +0100 with message-id <20091122154315.GA15763 at wavehammer.waldi.eu.org> and subject line fixed has caused the Debian Bug report #519149, regarding xen-3: only loads bzImage domU kernels, not dom0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 519149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519149 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: William Pitcock <nenolod at dereferenced.org> Subject: xen-3: does not really load bzImage kernels. Date: Tue, 10 Mar 2009 12:23:39 -0500 Size: 3157 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20091122/b840a0e2/attachment-0002.eml> -------------- next part -------------- An embedded message was scrubbed... From: Bastian Blank <waldi at debian.org> Subject: fixed Date: Sun, 22 Nov 2009 16:43:15 +0100 Size: 1672 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20091122/b840a0e2/attachment-0003.eml>
Apparently Analagous Threads
- Processed: severity of 519149 is important
- A couple of bugs with patches
- Processed: Re: Bug#474509: xen: Please enable support for loading bzImages with v2.08 of the x86 bootloader protocol
- Sucessful Upgrade from 3.0.4 to 3.2 anyone?
- Bug#695056: xen - Missing support for XZ compressed bzimage kernels