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? > So the 2.6.25-2-xen-686 kernel was not added to the menu.lst automatically. By > "hand" I tried first: > > title Xen 3.2-1-i386 / Debian GNU/Linux, kernel 2.6.25-2-xen-686 > root (hd0,0) > kernel //xen-3.2-1-i386.gz > module //vmlinuz-2.6.25-2-xen-686 root=/dev/mapper/vg00-root ro > console=tty0 > module //initrd.img-2.6.25-2-xen-686 > > It started to boot but froze after: > > (XEN) Xen is relinquishing VGA console. 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. > > Then I tried: > > title Debian GNU/Linux, kernel 2.6.25-2-xen-686 > root (hd0,0) > kernel //vmlinuz-2.6.25-2-xen-686 root=/dev/mapper/vg00-root > ro console=tty0 > initrd //initrd.img-2.6.25-2-xen-686 > > but that returned: > > 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 It is contrary to reasoning to say that there is a vacuum or space in which there is absolutely nothing. -- Descartes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]