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

Re: [Xen-users] Trouble in boot dom0 in xen3.0devel


  • To: yang jianguo <yangjianguo_biy@xxxxxxxxxxxx>
  • From: Boris Lenzinger <boris.lenzinger@xxxxxxxxx>
  • Date: Wed, 20 Jul 2005 21:25:43 +0200
  • Cc: "Petersson, Mats" <mats.petersson@xxxxxxx>, Xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 20 Jul 2005 19:25:02 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:user-agent:x-accept-language:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Hq1m6zhQFn8Z2/KkwJuTfDOkp1l2RxXtwmnrj3lqbHS9Z25gJf8uJVhx3c9XAOh5vF9ImcgsOz8AkE86x+/YtPB5QgOxUZymQbfGWKHVyFg3iL2VWeHu+Z8v2WU9ihwJIe4D8+R4SutscZpBwIvp5b3BVXsGxHr3go62PYqTYfw=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

When I look at my grub.conf, I see that the initrd passed to xen kernel
is written:
module /path/to/initrd-2.6.11.2-xen0

In your configuration file, I see
initrd /initrd-2.6.11.2-xen0

I think it is your problem. The initrd directive tells to kernel xen.gz
to take this initrd.
Setting module /path/to/initrd-2.6.11.2-xen0 tells to use
initrd-2.6.11.2-xen0 with vmlinuz-2.6.11.2-xen0

Hope this helps.

Boris

yang jianguo wrote:

>
> Thanks Petersson,
> I have not LVM, the Xen use xen.gz as a kernel and use
> vmlinuz-2.6.11.2-xen0 as a module, if i initrid vmlinuz-xxx-xen0, and
> add lines in grub/menu.lst:
> kernel /xen.gz dom0_mem=131072 console=vga
> module /vmlinuz-2.6.11.2-xen0 root=dev/hda1 ro console=tty0
> initrd /initrd-2.6.11.2-xen0
> it said:
> Error19: Linux kernel must be loaded before initrd
> how to set the initrd?
> */"Petersson, Mats" <mats.petersson@xxxxxxx>/* writon:
>
>     Most likely, you haven't got your initrd set up correctly, so your
>     root file system isn't being detected. The final step in the
>     kernel is to try NFS and Floppy file systems, if it can't find a
>     root fs somewhere else.
>     You either need to make sure that your initrd contains the
>     relevant modules for the disk(s) and file-systems that you use
>     (including for instance LVM if you're using that on the disk).
>     Another method is to disable modules, building a monolithic
>     kernel. That way, you don't need an initrd to get things going.
>     This was the way I got it working when I had the same problem.
>     --
>     Mats
>
>         
> ------------------------------------------------------------------------
>         *From:* xen-users-bounces@xxxxxxxxxxxxxxxxxxx
>         [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] *On Behalf Of
>         *yang jianguo
>         *Sent:* 20 July 2005 10:03
>         *To:* Xen-users@xxxxxxxxxxxxxxxxxxx
>         *Subject:* [Xen-users] Trouble in boot dom0 in xen3.0devel
>
>                 xen3.0 booted and dom0 kernel loaded, it said:
>
>                 Root-NFS: No NFS server available, giving up.
>
>                 VFS: Unable to mount root fs via NFS, trying floppy.
>
>                 VFS: Insert root floppy and press ENTER
>
>                 what should i do?
>
>                 -----------info----------------------
>
>                 xen: unstable, 3.0-devel
>
>                 kernel 2.6.11.2-xen0
>
>                 .coom/xen-users
>
>         
> ------------------------------------------------------------------------
>         DO YOU YAHOO!?
>
> __________________________________________________
> 赶快注册雅虎超大容量免费邮箱?
> http://cn.mail.yahoo.com
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Xen-users mailing list
>Xen-users@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-users
>


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