Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > #390927: xen-hypervisor-3.0.2-1-i386: Xen kernel panics when booting, > which was filed against the xen-hypervisor-3.0.2-1-i386 package. > > It has been closed by Bastian Blank <[EMAIL PROTECTED]>. > > Their explanation is attached below. If this explanation is > unsatisfactory and you have not received a better one in a separate > message then please contact Bastian Blank <[EMAIL PROTECTED]> by replying > to this email. > > Debian bug tracking system administrator > (administrator, Debian Bugs database) > > > > ------------------------------------------------------------------------ > > Subject: > Re: [Pkg-xen-devel] Bug#390927: xen-hypervisor-3.0.2-1-i386: Xen > kernel panics when booting > From: > Bastian Blank <[EMAIL PROTECTED]> > Date: > Tue, 3 Oct 2006 22:10:42 +0200 > To: > [EMAIL PROTECTED] > > To: > [EMAIL PROTECTED] > > Received: > (at 390927-done) by bugs.debian.org; 3 Oct 2006 20:10:53 +0000 > Return-path: > <[EMAIL PROTECTED]> > Received: > from wavehammer.waldi.eu.org ([82.139.201.20]) by spohr.debian.org > with esmtp (Exim 4.50) id 1GUqbN-0005sI-6T for > [EMAIL PROTECTED]; Tue, 03 Oct 2006 13:10:53 -0700 > Received: > by wavehammer.waldi.eu.org (Postfix, from userid 1000) id A72AA540C3; > Tue, 3 Oct 2006 22:10:42 +0200 (CEST) > Message-ID: > <[EMAIL PROTECTED]> > References: > <[EMAIL PROTECTED]> > MIME-Version: > 1.0 > Content-Type: > text/plain; charset=utf-8 > Content-Disposition: > inline > In-Reply-To: > <[EMAIL PROTECTED]> > User-Agent: > Mutt/1.5.13 (2006-08-11) > X-Spam-Checker-Version: > SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on > spohr.debian.org > X-Spam-Status: > No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no > version=2.60-bugs.debian.org_2005_01_02 > > > On Tue, Oct 03, 2006 at 09:22:17AM -0500, Jason Martens wrote: > >> When booting Xen Dom0 on my Dell 2950, the kernel panics. I have been >> unable to get the serial console working under xen (works under normal >> kernels), so the best debugging info I can provide is a screenshot of >> the console when it dies. I will attach that after the bug is opened. >> If you have suggestions for capturing the entire crash, I will be glad >> to follow them. >> > > You have a kernel which does not match the interface of xen. It is not a > bug that the hypervisor can't work with them. > > Bastian > > Hmm, I have linux-image-2.6.18-1-xen-686 and linux-image-2.6.17-2-xen-686 installed. My grub menu.lst looks like this:
title Xen 3.0.2-1-i386 / Debian GNU/Linux, kernel 2.6.18-1-xen-686 root (hd0,0) kernel /boot/xen-3.0.2-1-i386.gz module /boot/vmlinuz-2.6.18-1-xen-686 root=/dev/sda1 ro console=ttyS1,57600n8 console=tty0 module /boot/initrd.img-2.6.18-1-xen-686 savedefault title Xen 3.0.2-1-i386 / Debian GNU/Linux, kernel 2.6.17-2-xen-686 root (hd0,0) kernel /boot/xen-3.0.2-1-i386.gz module /boot/vmlinuz-2.6.17-2-xen-686 root=/dev/sda1 ro console=ttyS1,57600n8 console=tty0 module /boot/initrd.img-2.6.17-2-xen-686 Are these not the correct kernels for Xen? Jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
