This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Kernel panic FC7 and Debian Etch

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Kernel panic FC7 and Debian Etch
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Thu, 18 Oct 2007 03:03:47 +0100
Cc: mccoy silva <mccoy.silva@xxxxxxxxx>
Delivery-date: Wed, 17 Oct 2007 19:04:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <adeae2fb0710091106y74cae3ccq969f7c8f95f25ec3@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <adeae2fb0710091106y74cae3ccq969f7c8f95f25ec3@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.6
Hi there!

> I have installed Fedora Core 7 with kernel-xen-2.6.20-2931.fc7 and
> xen-3.1.0-6.fc7, but every time that try to boot my Debian Etch VM I got
> the following error:
>     device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised:
> dm-devel@xxxxxxxxxx
>     Kernel panic - not syncing: Attempted to kill init!

Hmm, how did you originally install your Etch VM?  Can you post the full boot 
output, please?

> My VM config file:
>   kernel = '/boot/vmlinuz-2.6.20-2936.fc7xen'
>   ramdisk = '/boot/initrd-2.6.20-2936.fc7xen.img'

I see you're using the FC7 kernel and initrd.  You might get a better 
experience if you use the Debian kernel and initrd.  I believe Etch has a Xen 
3 Linux kernel, right?

You can then keep the guest's kernel and initrd in the guest's filesystem so 
that apt updates will apply software updates to them.  You can then set up a 
grub-style menu.lst that will allow the "pygrub" bootloader in dom0 to boot 
these, without you having to specify a kernel= or ramdisk= line in the VM 

I guess it's possible that the kernel and initrd you're using from FC7 isn't 
doing the right thing for your debian install, so this might also help fix 
your actual problem ;-)

Nb.  pygrub runs as root in dom0 so there is some risk of exposing your dom0 
to exploit by a user who has xm console access to the domU.  If you're using 
both of them yourself, I guess that'd be less of an issue ;-)  A dom0 root 
exploit of this type was found recently.

If you didn't want to use pygrub you could always copy the Debian kernel and 
initrd out of the guest FS and use kernel= and ramdisk= in the config file to 
point to them.


>   memory = '256'
>   name = 'email-teste'
>   root = "/dev/hda1 ro"
>   disk = [
> 'phy:/dev/vg00/lvEmailTeste,hda1,w','phy:/dev/vg00/lvSwap-EmailTeste,hda2,w
>'] vif = [ 'mac=00:16:3e:4b:10:20,bridge=virbr0' ]
>   extra = '3'
>   vmid = '1'
> Thanks for any help.
> Regards,
> McCoy

Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>