| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] kernel panic when creating domainU
I've modified my etc/fstab in the guest as you said. I had already the
disk= line in my guestdomain config (I had only dropped it when pasting
here). I didn't consider for now yuor useful advice about boot loader
in the guest.
However, something seems still to be wrong!
My final
output, before kernel panic, is the same:
.....
Making device-mapper
control node
Scanning logical volumes
Reading all physical volumes.
This may take a while...
No volume groups found
Activating logical
volumes
Unable to find volume group "VolGroup00"
Creating root
device.
Mounting root filesystem.
mount: could not find filesystem
'/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys,
mounting internal defaults
setuproot: error mounting /proc: No such
file or directory
setuproot: error mounting /sys: No such file or
directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No
such file or directory
Kernel panic - not syncing: Attempted to kill
init!
Do you think It's only because of the kind of kernel I used
(that is that one of domain0)?
----Messaggio originale----
Da: mark.
williamson@xxxxxxxxxxxx
Data: 13-giu-2007 7.36 PM
A: <xen-users@lists.
xensource.com>, "andrea15@xxxxxx"<andrea15@xxxxxx>
Ogg: Re: [Xen-users]
kernel panic when creating domainU
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
|
|
|
| |
|
Home