Bug#479018: marked as done (linux-image-2.6.24-1-xen-686: update-grub doesn't recognize vmlinuz-2.6.24-1-xen-686 or vmlinuz-2.6.25-1-xen-686)
Your message dated Mon, 26 May 2008 18:41:44 +0200
with message-id <20080526164144.GA26495@stro.at>
and subject line Re: Bug#479018: linux-image-2.6.24-1-xen-686: update-grub doesn't recognize vmlinuz-2.6.24-1-xen-686 or vmlinuz-2.6.25-1-xen-686
has caused the Debian Bug report #479018,
regarding linux-image-2.6.24-1-xen-686: update-grub doesn't recognize vmlinuz-2.6.24-1-xen-686 or vmlinuz-2.6.25-1-xen-686
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@bugs.debian.org
immediately.)
--
479018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479018
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.24-1-xen-686
Version: 2.6.24-6
Severity: important
Run update-grub sets up only:
Found Xen hypervisor 3.2-1-i386, kernel: //vmlinuz-2.6.18-6-xen-686
Found kernel: //vmlinuz-2.6.24-1-686
Found kernel: //vmlinuz-2.6.22-3-686
But skips the other two vmlinuz-2.6.24-1-xen-686 and vmlinuz-2.6.25-1-xen-686.
When I manualy tried to add vmlinuz-2.6.24-1-xen-686 to the /boot/grub/menu.lst and tried
to boot the kernel. I got this error message:
Error 13: Invalid or unsupported executable format.
# apt-show-versions | grep grub
grub/lenny uptodate 0.97-37
grub-common/lenny uptodate 1.96+20080426-1
Jozef.
-- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (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
Versions of packages linux-image-2.6.24-1-xen-686 depends on:
ii initramfs-tools 0.92 tools for generating an initramfs
ii linux-modules-2.6.24-1-xen-68 2.6.24-6 Linux 2.6.24 modules on i686
Versions of packages linux-image-2.6.24-1-xen-686 recommends:
ii libc6-xen 2.7-10 GNU C Library: Shared libraries [X
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, 14 May 2008, Ian Campbell wrote:
> On Wed, 2008-05-14 at 09:46 +0200, Jozef Kutej wrote:
> > maximilian attems wrote:
> > > On Fri, 02 May 2008, Jozef Kutej wrote:
> > >
> > > can you please try out the upcoming 2.6.25-2 package,
> > > should be available next days.
> > >
> > >
> >
> > Setting up linux-image-2.6.25-2-xen-686 (2.6.25-2) ...
> > update-initramfs: Generating /boot/initrd.img-2.6.25-2-xen-686
> > Searching for GRUB installation directory ... found: /boot/grub
> > Searching for default file ... found: /boot/grub/default
> > Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
> > Searching for splash image ... none found, skipping ...
> > Found Xen hypervisor 3.2-1-i386, kernel: //vmlinuz-2.6.18-6-xen-686
> > Found kernel: //vmlinuz-2.6.24-1-686
> > Found kernel: //vmlinuz-2.6.22-3-686
> > Found kernel: //memtest86.bin
> > Updating /boot/grub/menu.lst ... done
>
> This is in domain 0 rather than domain U, correct?
>
> The 2.6.24/25/etc... kernels do not support domain 0 operation yet and
> this seems like a reasonable enough point for them to fail if you
> tried...
>
> Pretty much the only options for domain 0 kernel at the moment is to use
> the Etch 2.6.18 xen kernels or to build your own from the XenSource
> tree.
>
> >
> > Error 13: Invalid or unsupported executable format.
>
> That's expected since this kernel requires Xen to boot it (as for the
> first stanza above) and grub won't directly understand this kind of -xen
> kernel which is just a gzipped ELF file.
>
> You original problem "But skips the other two vmlinuz-2.6.24-1-xen-686
> and vmlinuz-2.6.25-1-xen-686." is down to an oddity in update-grub when
> used with paravirt_ops kernels which is being addressed in this thread:
> http://lists.alioth.debian.org/pipermail/pkg-grub-devel/2008-April/004701.html / http://lists.alioth.debian.org/pipermail/pkg-grub-devel/2008-May/004821.html. However since these kernels can't do domain 0 yet it isn't really the root cause...
>
> Ian.
>
> --
> Ian Campbell
closing as inappropriate usage of a domU kernel as dom0.
the grub issues are tracked against grub.
the xen dom0 features aren't yet upstream available nor in
fedora, but will follow as soon as they are there.
regards
--
maks
--- End Message ---
Reply to: