| [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 13:04:05 -0500Cc: xen-users@xxxxxxxxxxxxxxxxxxxDelivery-date: Wed, 21 Jun 2006 11:04:41 -0700Domainkey-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=oqY90sbrh1E6j4miHAhaFiEppOCnUULVzPh1vYX89wVxfs0PmK8rD6sOK+8YoBXyPm+fJwjpfwLR3dE7BHilJWQHDx3+bDeQKzJLcbompaLrWa/AeEXg6B2Gf9JpK7Ey1veRrpHA5RiG6XtGtKgiixrMZke7XTW+gLTpzZz5Sac=List-id: Xen user discussion <xen-users.lists.xensource.com> 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:24To: 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 
 
       
    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
 _______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users 
 |