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

Re: [Xen-users] Suse 9.3 "kernel panic - not syncing: VFS: Unable tomount root fs on unknown-block (8, 1)"


  • To: Tom Brown <tbrown@xxxxxxxxxxxxx>, David Schmidt <David_Schmidt@xxxxxxxx>, David F Barrera <dfbp@xxxxxxxxxx>, James Bulpin <james@xxxxxxxxxxxxx>, Noniko H <hitumabushi@xxxxxxxxxxxxxxx>
  • From: e&v <ervin23@xxxxxxxxx>
  • Date: Thu, 16 Jun 2005 17:51:42 +0200
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 16 Jun 2005 15:50:48 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=h7J/KeBOKKGKYll3yc9pGS1knyR/8WPpSa9DgZM1lFGz/7tb1CpTJFLrd5jdnX1tg28apmWBGOVbk3hpN9c7Ywc4lRkV9IAwb3Hn4DKxZ0w37CQUl+tXlH6K7iTh4KaLMgyDoiEiJIYwCaHG+gdNeRK+rOHsLHp0BXBSwGPoMXE=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

thanks to all of you / the combined ideas you gave me did the trick 
... I have several domins running now!

Next step is to get the network up to speed and the graphical
interface in place  /

Have fun / 

On 6/14/05, Tom Brown <tbrown@xxxxxxxxxxxxx> wrote:
> On Tue, 14 Jun 2005, David F Barrera wrote:
> 
> > > > disk = ['file:/home/name/vm1disk,sda1,w']
> > Try using '0801' instead of sda1
> 
> why? The kernel went to the right spot (8,1)...
> 
> > > > > "kernel panic - not syncing: VFS: Unable to mount root fs on
> > > > > unknown-block (8,1)"
> 
> there just wasn't anything there... which suggests /home/name/vm1disk is
> somehow not correct.
> 
> hhmm, I must be wrong. 2.0.5 won't let you specify an non existant file.
> 
>    [root@xen1 /etc/xen]# xm create bogus -c
>    Using config file "bogus".
>    Error: Error creating domain: vbd: Segment not found:  \
>      uname=file:/home/name/vm1disk
> 
> ok, if I create a bogus file, e.g. not a legit filesystem, I get
> 
>    Kernel panic - not syncing: VFS: Unable to mount root fs on
>    unknown-block(8,1)
> 
> if I now turn around and format that bogus file as a filesystem,
> e.g. mke2fs /tmp/delete.me and boot with
> 
>    disk = [ 'file:/tmp/delete.me,sda1,w']
> 
> I get past that stage, and instead run into the more normal:
> 
>    Warning: unable to open an initial console.
>    Kernel panic - not syncing: No init found.  Try passing init=
>       option to kernel.
> 
> The warning indicates there was no /dev/console, and the "no
> init" means that there was no /sbin/init program on the
> filesystem (no suprise, it was just built for testing, so it was empty).
> 
> Anyhow, to cut a long story short...
> /home/name/vm1disk file does exist, but apparently is not a valid
> filesystem. And that is likely to take more than a few sentences to
> explain away :-(
> 
> -Tom
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 


-- 


mvh/best regards  ervin

_______________________________________________
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®.