[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] xen unstable boot problem - Kernel panic - not syncing: VFS


  • To: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • From: "Hardeep Singh" <hardeepguru@xxxxxxxxx>
  • Date: Wed, 21 Jun 2006 14:04:02 -0500
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 21 Jun 2006 12:05:12 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=fOD9gB/4dvLcCjVnZhEK1czOj+dZrL0OCoYXxOBEqwLGvtK8E4Q1JB2KgcrWJ8nprgAg5FNlNSLOnP82j6LsJeSD+ohODZY9vb4c1fr/qOnFmzrmP7JR+eg9Qy9OfKZQ7WrqMYhMFwrltMFEgWiIo+oRCFUhmVsje0LGpYjaoYg=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi Mats,

Well an lsmod in Xen 3.0 gives the following:

root@pippin:/home/hardeep# lsmod
Module                  Size  Used by
loop                   13288  4
bridge                 48788  0
video                  13252  0
container               3232  0
button                  4944  0
battery                 7620  0
ac                      3460  0
ipv6                  251360  16
nfs                   216148  1
lockd                  60680  2 nfs
sunrpc                146020  3 nfs,lockd
e1000                 108756  0
shpchp                 43936  0
pci_hotplug            25596  1 shpchp
uhci_hcd               29872  0
intel_agp              22812  0
agpgart                31176  1 intel_agp
i82875p_edac            5732  0
edac_mc                13064  1 i82875p_edac
dm_mod                 49620  0
parport_pc             33648  1
lp                     10176  0
parport                36648  2 parport_pc,lp
md_mod                 69172  0
ext3                  129288  1
jbd                    55060  1 ext3
trm290                  4132  0 [permanent]
sc1200                  6400  0 [permanent]
opti621                 4004  0 [permanent]
ns87415                 3948  0 [permanent]
it821x                  7492  0 [permanent]
cs5535                  3616  0 [permanent]
thermal                10696  0
processor              16660  1 thermal
fan                     3364  0


and,

root@merry:/lib/modules/2.6.16.13-xen# ls
build   modules.alias   modules.dep          modules.inputmap   modules.pcimap     modules.symbols  source
kernel  modules.ccwmap  modules.ieee1394map  modules.isapnpmap  modules.seriomap  modules.usbmap

this is the same as for the stable version,

root@pippin:/lib/modules/2.6.16-xen# ls
build   modules.alias   modules.dep          modules.inputmap   modules.pcimap    modules.symbols  source
kernel  modules.ccwmap  modules.ieee1394map  modules.isapnpmap  modules.seriomap  modules.usbmap

I still have no idea of how to fix this :(

Regards,
Hardeep Singh

On 6/21/06, Petersson, Mats <Mats.Petersson@xxxxxxx> wrote:
Ok, then it comes to what the .config file contains. I don't know hwat it SHOULD contain, as I don't know the rest of your system setup... Since you're using basic IDE controller, it shouldn't be a problem with that (unless you've got some weird chipset that requires a different driver).
 
Try booting your working Xen-version and do a lsmod, then check that all modules listed there are also in the .../modules/2.6.16.13-xen directory...
 
--
Mats
 


From: Hardeep Singh [mailto:hardeepguru@xxxxxxxxx]
Sent: 21 June 2006 19:04

To: Petersson, Mats
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] xen unstable boot problem - Kernel panic - not syncing: VFS

Oh no no, my initrd is the one as mentioned in the grub. I guess I messed up in my first post. Sorry for that!

Hardeep

On 6/21/06, Petersson, Mats <Mats.Petersson@xxxxxxx> wrote:
Is your initrd file called
/boot/initrd.img- 2.6.16.13-xen
or
/boot/initrd-2.6.16.13-unstable
 
If you give one name to mkinitrd and another name to grub, it could be the reason it doesn't work...
 
--
Mats


Sent: 21 June 2006 18:24
To: Petersson, Mats
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] xen unstable boot problem - Kernel panic - not syncing: VFS

Dear Mats,

I'm sure the root partition on the command line for my vmlinuz is correct.

My grub looks like the following:


title           Xen 3.0
root            (hd0,0)
kernel          /boot/xen- 3.0.2-2.gz dom0_mem=262144 com1=38400,8n1 sched=bvt
module          /boot/vmlinuz-2.6.16-xen root=/dev/hda1 ro console=ttyS0
module          /boot/initrd.img-2.6.16-xen
boot


title           Xen 3.0 Unstable
root            (hd0,0)
kernel          /boot/xen-3.0-unstable.gz dom0_mem=262144 com1=38400,8n1 sched=credit
module          /boot/vmlinuz-2.6.16.13-xen root=/dev/hda1 ro console=ttyS0
module          /boot/initrd.img- 2.6.16.13-xen
boot


title           Ubuntu, kernel 2.6.12-9-686
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.12-9-686 root=/dev/hda1 ro quiet splash
initrd          /boot/initrd.img-2.6.12-9-686
savedefault
boot


However, the problem is only with xen-unstable. Xen 3.0 boots fine and is working normally! Also I am a newbie to all this so could'nt really get you regarding the drivers!

Please let me know if you need me to provide any additional information or append a config file!

Regards,
Hardeep Singh

On 6/21/06, Petersson, Mats <Mats.Petersson@xxxxxxx > wrote:
Usually, this is becuase you don't have the right drivers set up in the .config for your Linux kernel (either as modules or as builtin - if they are built in, you wouldn't need an initrd). Or you're not specifying the right root partionion on the command-line for your vmlinuz when you boot it... It's impossible to say which one of those it is without knowing more about your setup, both what hardware [including, for example, what partitions are used for what] and what the commands in grub.conf are.
 
Very likely is that you have either a SATA or SCSI drive, and the drivers for your SATA/SCSI controller isn't configured into the kernel .config file. Or you're using an unusual file-system on your root-drive, and this file-system isn't supported by the default .config.
 
And yes, mkinitrd is different for different distributions of Linux, so one set of arguments for one distribution doesn't necessarily work for another distritution :-(
 
 
I hope this helps.
 
--
Mats


From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto: xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Hardeep Singh
Sent: 21 June 2006 17:33
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xen unstable boot problem - Kernel panic - not syncing: VFS

Hi all,

I'm trying to install xen-unstable on ubuntu. I downloaded the tarball from the download page. Everything goes on fine until the compilation. However when I boot xen-unstable this the error I get:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block (0,0)

I guess this has something to do with the ram disk image. What I am doing currently is:

depmod -F /boot/System.map-2.6.16.13-xen 2.6.16.13-xen
mkinitrd -o /boot/initrd-2.6.16.13-unstable 2.6.16.13-xen

The readme however says to do this:

mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16.13-xen.img 2.6.16.13-xen

But when I do this, mkinitrd gives an error regarding illegal options. The only ones it provides are:

-d confdir         Specify an alternative configuration directory.
-k                     Keep temporary directory used to make the image.
-m command  Set the command to make an initrd image.
-o outfile          Write to outfile.
-r root              Override ROOT setting in mkinitrd.conf.

Please help me on how to go about booting xen-unstable. I desperately need to get it working!

Regards,
Hardeep



--
hardeep



--
hardeep



--
hardeep
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.