Your message dated Sat, 14 Apr 2012 16:34:55 +0100
with message-id <1334417695.7150.431.camel@deadeye>
and subject line Re: linux-image-2.6.18-6-xen-vserver-686: No grub entry's
after install of kernel, and when I add it by hand the kernel can't start
has caused the Debian Bug report #515255,
regarding linux-image-2.6.18-6-xen-vserver-686: No grub entry's after install
of kernel, and when I add it by hand the kernel can't start
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 [email protected]
immediately.)
--
515255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515255
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-2.6.18-6-xen-vserver-686
Version: 2.6.18.dfsg.1-24
Severity: important
This is a very big problem for my anyway, I have to use both Xen and Vserver,
and the kernel can provide my both, but when I install it, (both amd64
and 686 kernel) it says “Changing /boot/grub/menu.lst” but there is
nothing changed in menu.lst so I can't start the kernel, then I entered
it by hand (see my menu.lst below) and rebooted and tried to start the
new kernel, but then it boots and stops with “waiting for root filesystem...
...” and then never continues
*** My menu.lst ***
## ## End Default Options ##
title Debian GNU/Linux, kernel 2.6.18-6-686
root (hd2,0)
kernel /boot/vmlinuz-2.6.18-6-686 root=/dev/md1 ro
initrd /boot/initrd.img-2.6.18-6-686
savedefault
title Debian GNU/Linux, kernel 2.6.18-6-xen-vserver-686
root (hd2,0)
kernel /boot/vmlinuz-2.6.18-6-xen-vserver-686 root=/dev/md1 ro
initrd /boot/initrd.img-2.6.18-6-xen-vserver-686
savedefault
title Debian GNU/Linux, kernel 2.6.18-6-vserver-686
root (hd2,0)
kernel /boot/vmlinuz-2.6.18-6-vserver-686 root=/dev/md1 ro
initrd /boot/initrd.img-2.6.18-6-vserver-686
savedefault
*** ls -a of /boot ***
config-2.6.18-6-486
config-2.6.18-6-686
config-2.6.18-6-vserver-686
config-2.6.18-6-xen-vserver-686
grub
initrd.img-2.6.18-6-486
initrd.img-2.6.18-6-486.bak
initrd.img-2.6.18-6-686
initrd.img-2.6.18-6-vserver-686
initrd.img-2.6.18-6-xen-vserver-686
initrd.img-2.6.18-6-xen-vserver-686.bak
System.map-2.6.18-6-486
System.map-2.6.18-6-686
System.map-2.6.18-6-vserver-686
System.map-2.6.18-6-xen-vserver-686
vmlinuz-2.6.18-6-486
vmlinuz-2.6.18-6-686
vmlinuz-2.6.18-6-vserver-686
vmlinuz-2.6.18-6-xen-vserver-686
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.18-6-xen-vserver-686 depends on:
ii initramfs-tools 0.85i tools for generating an initramfs
ii linux-modules-2.6.18-6- 2.6.18.dfsg.1-24 Linux 2.6.18 modules on i686
Versions of packages linux-image-2.6.18-6-xen-vserver-686 recommends:
pn libc6-xen <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
It is not correct to make the Xen hypervisor a dependency of a
Xen-enabled kernel, because the hypervisor may often be installed
outside of the Debian system.
Ben.
--
Ben Hutchings
It is easier to change the specification to fit the program than vice versa.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
