WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] kernel panic when creating domainU

To: xen-users@xxxxxxxxxxxxxxxxxxx, "andrea15@xxxxxx" <andrea15@xxxxxx>
Subject: Re: [Xen-users] kernel panic when creating domainU
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Wed, 13 Jun 2007 18:36:12 +0100
Delivery-date: Wed, 13 Jun 2007 13:41:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <113248f34ec.andrea15@xxxxxx>
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: <113248f34ec.andrea15@xxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.6
On Wednesday 13 June 2007, andrea15@xxxxxx wrote:
> I used a file-backed VBD for the virtual disk of my VM.
> I formatted it
> as ext3, I mounted it in a directory and I copied directories from my
> linux-domain0 installation as a test.
> I used this configuration file:
> kernel = "/boot/vmlinuz-2.6.16.29-xen_3.0.3.0"
> ramdisk = "/boot/initrd-
> 2.6.16.29-xen_3.0.3.0.img"
> memory = 256
> name = "dominio1"
> vif = [ '' ]

You don't have a disk = line in there - you need one or it won't see any disks 
to boot off.

Also, you should be aware that kernel= and ramdisk= fetch the kernel and 
ramdisk from Domain 0's filesystem, not from the guest's.  If you want to 
boot from a kernel in the guest's filesystem, take away the kernel= and 
ramdisk= options and you should get a bootloader coming up...

Probably best to tackle that problem after you've got the domain booting 
though - one problem to solve at a time.

> and this is the
> etc/fstab in my vm(perhaps I made some mistakes in it!?!):
> /home/sibilia/dominio1  /                       ext3    defaults

     ^ That's probably wrong.  I guess that's the path to the domain's virtual 
disk on dom0, right?  The virtual machine can't see the dom0 filesystem just 
it's virtual disks.

> 1 1
> proc                    /proc                   proc
> defaults        0 0
> sysfs                   /sys
> sysfs   defaults        0 0
> I've only cut some lines from the original
> /etc/fstab.
>
> Do you think It's a problem whit config files?

OK, change the GUEST fstab's first line to look like this:

/dev/sda1       /       ext3    defaults        1       1

sda1 will be the virtual disk the guest sees.

Now, to your domain config file (in domain 0), you should add:

disk = ['tap:aio:/home/sibilia/dominio1,sda1,w']

Now try booting the domain, does this work better?

Cheers,
Mark

-- 
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
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users