All of lore.kernel.org
 help / color / mirror / Atom feed
From: aq <aquynh@gmail.com>
To: xen-devel@lists.sourceforge.net
Subject: Re: Problem when making a domain
Date: Wed, 15 Dec 2004 03:41:01 +0900	[thread overview]
Message-ID: <9cde8bff04121410417f37ae01@mail.gmail.com> (raw)
In-Reply-To: <9cde8bff04121410347acee6a8@mail.gmail.com>

Hello,

> > Doesn't look like it from your boot messages. It's either a garbage
> > file, or it needs decompressing.
>
> You could try running file(1) on it to determine type.

I check again the rootfs, and found nothing wrong, like below
---
$ file rootfs
rootfs: Linux rev 1.0 ext2 filesystem data
---

I can even mount the rootfs (with -o loop), and found all the data
inside it in perfectly shape.

One more thing I noticed in the bootup message is:
---
fsck.ext2: Invalid argument while trying to open /dev/ram0
---

It seems the bootup process tried to check /dev/ram0? why is that? I
expect it would check /dev/hda1, like what I declared in my
configuration file (!!??)

Please help me. I struggle a lot at this step. Making a first domain
in Xen looks tedious for me ;-)

I posted again my configuration file (which follows the demo in the
2.0 manual, with ttylinux as rootfs).

Here is my configuration file:
----
$ cat tty.xm
kernel = "/boot/vmlinuz-2.6.9-xenU"
memory = 64
name = "tty"
disk = [ 'file:~/myxen/rootfs,hda1,w' ]
root = "/dev/hda1 ro"
----

And finally here is the excerpt of bootup message. It always ask me to
enter root password then it enters System maintenance mode, which
mounts / as read-only:

----
...
Starting fsck for root filesystem.
e2fsck 1.35 (28-Feb-2004)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: Invalid argument while trying to open /dev/ram0

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

WARNING: Errors found while checking root filesystem.
You can login as root now, the system will reboot after logout.

Give root password for system maintenance (or type Control-D for
normal startup):

----

Best regards,
AQ


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

      parent reply	other threads:[~2004-12-14 18:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-12  9:39 Problem when making a domain aq
2004-12-12 10:00 ` Keir Fraser
2004-12-12 10:36   ` aq
2004-12-12 10:53     ` Steven Hand
     [not found]   ` <20041212201539.U85095@acropolis.argolis.org>
     [not found]     ` <9cde8bff04121410347acee6a8@mail.gmail.com>
2004-12-14 18:41       ` aq [this message]

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=9cde8bff04121410417f37ae01@mail.gmail.com \
    --to=aquynh@gmail.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.