xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: ccmail111 <ccmail111@yahoo.com>
Cc: deshantm@gmail.com, xen-devel@lists.xensource.com
Subject: Re: boot Xen 4.0
Date: Fri, 14 May 2010 08:55:02 +0300	[thread overview]
Message-ID: <20100514055502.GP17817@reaktio.net> (raw)
In-Reply-To: <274417.35576.qm@web34206.mail.mud.yahoo.com>

On Thu, May 13, 2010 at 06:42:44PM -0700, ccmail111 wrote:
>    Thanks Pasi/Todd,
> 
>    I did:
>    # mkinitrd -v -f --builtin=ehci-hcd --builtin=ohci-hcd --builtin=uhci-hcd
>    --builtin=ahci --builtin=aacraid --builtin=aacraid --builtin=sd_mod
>    --builtin=scsi_mod /boot/initrd.img-2.6.31.13 2.6.31.13
> 
>    Now
>    I see during boot: kernel panic:
> 
>    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
>    setuproot: error mounting /proc: No such file or directory
>    setuproot: error mounting /sys: No such file or directory
>    switchroot: mount failed: No such file or directory
>      kernel panic - not syncing : Attempted to kill init !
> 


So your root= parameter is wrong or initrd is wrong (not loading correct modules)..
please paste your grub.conf.

-- Pasi

>    --- On Thu, 5/13/10, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> 
>      From: Pasi Kärkkäinen <pasik@iki.fi>
>      Subject: Re: [Xen-devel] initrd Xen 4.0
>      To: "ccmail111" <ccmail111@yahoo.com>
>      Cc: deshantm@gmail.com, xen-devel@lists.xensource.com
>      Date: Thursday, May 13, 2010, 4:27 PM
> 
>      On Thu, May 13, 2010 at 01:08:36PM -0700, ccmail111 wrote:
>      >    The #5 of README is not clear in details.
>      >    which directory to run depmod and mkinitrd from ?
>      >
> 
>      It doesn't matter.
> 
>      >    I see:
>      >
>      >    # depmod xen-4.0.0
>      >    WARNING: Couldn't find symtab and strtab in module xen-4.0.0
>      >
> 
>      Wrong. You need to run depmod for the *kernel*, not for xen.
> 
>      So like this:
>      depmod -a 2.6.32.12
> 
>      Or whatever is your kernel version.
> 
>      -- Pasi
> 
>      >    # ls -l
>      >    total 1356
>      >    -rw-r--r-- 1 root root 1380620 May 13 13:05 xen-4.0.0
>      >
>      >    Any suggestions ?
>      >
>      >    --- On Wed, 5/12/10, Todd Deshane <deshantm@gmail.com> wrote:
>      >
>      >      From: Todd Deshane <deshantm@gmail.com>
>      >      Subject: Re: [Xen-devel] initrd Xen 4.0
>      >      To: "ccmail111" <ccmail111@yahoo.com>
>      >      Cc: xen-devel@lists.xensource.com
>      >      Date: Wednesday, May 12, 2010, 9:46 PM
>      >
>      >      Hi,
>      >
>      >      See inline.
>      >
>      >      On Wed, May 12, 2010 at 12:25 PM, ccmail111
>      <[1]ccmail111@yahoo.com>
>      >      wrote:
>      >      >
>      >      > Hi,
>      >      >
>      >      > I downloaded Xen 4.0 and did:
>      >      > make install
>      >      > I donot see initrd (ramdisk) being created at all.
>      >      >
>      >      > Any suggestions ?
>      >      >
>      >
>      >      Step 5 of the README
>      >         Depending on your config, you may need to use 'mkinitrd' to
>      create
>      >         an initial ram disk, just like a native system e.g.
>      >          # depmod 2.6.18-xen
>      >          # mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod
>      >      initrd-2.6.18-xen.img 2.6.18-xen
>      >         Other systems may requires the use of 'mkinitramfs' to create
>      the
>      >         ram disk.
>      >          # depmod 2.6.18-xen
>      >          # mkinitramfs -o initrd-2.6.18-xen.img 2.6.18-xen
>      >
>      >      You may need to change the kernel version based on what you
>      built.
>      >      Also some distros use different commands to build initrd files.
>      >
>      >      I actually forgot about this step for a second too.
>      >
>      >      Thanks,
>      >      Todd
>      >
>      >      --
>      >      Todd Deshane
>      >      [2][1]http://todddeshane.net
>      >      [3][2]http://runningxen.com
>      >
>      > References
>      >
>      >    Visible links
>      >    1. file:///mc/compose?to=ccmail111@yahoo.com
>      >    2. [3]http://todddeshane.net/
>      >    3. [4]http://runningxen.com/
> 
>      > _______________________________________________
>      > Xen-devel mailing list
>      > Xen-devel@lists.xensource.com
>      > [5]http://lists.xensource.com/xen-devel
> 
> References
> 
>    Visible links
>    1. http://todddeshane.net/
>    2. http://runningxen.com/
>    3. http://todddeshane.net/
>    4. http://runningxen.com/
>    5. http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-05-14  5:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14  1:42 boot Xen 4.0 ccmail111
2010-05-14  5:55 ` Pasi Kärkkäinen [this message]
2010-05-15 16:34 ` yingbin wang
2010-05-17 20:17   ` ccmail111
  -- strict thread matches above, loose matches on Subject: below --
2010-05-18 19:08 ccmail111
2010-05-18 19:11 ` Pasi Kärkkäinen
2010-05-18 21:46   ` ccmail111
2010-05-26 17:44     ` Konrad Rzeszutek Wilk
2010-06-04 20:30 ccmail111
2010-06-04 20:34 ` Konrad Rzeszutek Wilk
2010-06-10 16:02 ccmail111
2010-06-15 21:26 ` Konrad Rzeszutek Wilk
2010-06-17 18:27 ccmail111
2010-06-21 20:54 ccmail111
2010-06-22 17:30 ` Konrad Rzeszutek Wilk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100514055502.GP17817@reaktio.net \
    --to=pasik@iki.fi \
    --cc=ccmail111@yahoo.com \
    --cc=deshantm@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).