This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: Fedora Core 3 -- boot ok, can't login.

To: yi yang <yangyiyy@xxxxxxxxx>
Subject: [Xen-devel] Re: Fedora Core 3 -- boot ok, can't login.
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 15 Nov 2004 17:42:24 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 15 Nov 2004 20:26:46 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> I just installed the xen2.0 on my FC2  system, it works well. So I
> guess it is the FC3 problem. And also I guess xen2.0 does not support
> the udev well.

It turns out to be fairly simple to boot FC3 on Xen -- the problem is
that it relies on an initial ramdisk (initrd) to bootstrap itself.

So, you have two possible ways to get an FC3 filesystem working:

1. Manually create some device nodes in /dev. To do this, boot a
   rescue disk or some other partition and then mount the
   root filesystem, and:
    # mknod /mnt/dev/null c 1 3
    # mknod /mnt/dev/console c 5 1
2. Load and run a suitable initrd file. You can either use one
   provided in the /boot directory of your FC3 filesystem, or you
   can use the slightly-modified one that we supply at:

   To specify an initrd file for domain 0 add an extra "module"
   line to your GRUB config, after your kernel-module line
   (e.g., "module /boot/initrd-2.6.9-xen0.img"). To use an
   initrd file for other domains, set the "ramdisk" variable in
   your domain configuration file
   (e.g., "ramdisk = path/to/initrd-2.6.9-xenU.img").

 Hope this helps,

This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Re: Fedora Core 3 -- boot ok, can't login., Keir Fraser <=