All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Katin <gmane@askneil.com>
To: xen-devel@lists.sourceforge.net
Subject: EDD failing; not finding ide disks
Date: Fri, 21 Jan 2005 17:45:38 -0800	[thread overview]
Message-ID: <cssb7v$so4$1@sea.gmane.org> (raw)


I'm a first time xen user, trying to get 2.0.3 up
and running for the first time.  I've made some
progress, but xen doesn't seem to want to discover
my ide disks.

I built a xen kernel, starting from an existing, known-working
config file.  I am running linux 2.6.10.  The base distribution
is gentoo.

The hardware is a low end IBM server (xSeries 200).

The relevant grub config lines are:

   title=IBM Gentoo Linux (bzImage)
   root (hd0,0)
   kernel /bzImage root=/dev/hda3

   title=IBM Gentoo Linux (xen0)
   root (hd0,0)
   kernel /xen.gz dom0_mem=131072 noreboot com1=38400,8n1
   module /vmlinuz-xen0 root=/dev/hda3 console=ttyS0,38400


The boot fails with this message when booting xen:

   BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
   EDD information not available.
   VFS: Cannot open root device "hda3" or unknown-block(0,0)
   Please append a correct "root=" boot option

(the full serial log is available at
http://www.askneil.com/neil/xen/xenboot.txt
if anyone wants to see all the info...)

When EDD is running in a normal, non-xen kernel it reports:

   BIOS EDD facility v0.16 2004-Jun-25, 1 devices found

Full dmesg output from the working, normal kernel is available at:
http://www.askneil.com/neil/xen/normalboot.txt

I'm sorry for bothering the list, but I'm trying to figure
out what I could be doing wrong that would interfere with
EDD, which just makes low level bios calls.

In addtion, the "normal" kernel probes all the ide busses
and connected drives; none of this output appears in the
xen boot listing (but this might just be a difference between
console and dmesg outputs...)


Thanks in advance for any help folks might have about
this...




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

                 reply	other threads:[~2005-01-22  1:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='cssb7v$so4$1@sea.gmane.org' \
    --to=gmane@askneil.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.