From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Florian Wagner <f_wagner@syscomp.de>
Cc: xen-devel@lists.xensource.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Areca RAID with Xen 3.4 and Linux 2.6.32 dom0
Date: Thu, 06 May 2010 11:07:09 -0700 [thread overview]
Message-ID: <4BE3054D.8070500@goop.org> (raw)
In-Reply-To: <20100506152537.758074dc@auedv3.syscomp.de>
On 05/06/2010 06:25 AM, Florian Wagner wrote:
> I'm trying to boot Xen 3.4.1 with a Linux 2.6.32-12 with dom0 support
> from Debian unstable (linux-image-2.6.32-12-xen-amd64).
I'm not exactly sure what kernel version this is. Have you tried a
xen.git 2.6.32.12 kernel?
> The result is
> a system unable to find its root filesystem on an Areaca ARC-1120 RAID
> controller because of some SCSI issues. I've attach the Xen and Linux
> boot messages.
>
> Booting the very same kernel without a the Xen hypervisor works with no
> problems.
>
OK, that's good to know.
> Another system with a LSI MegaRAID SCSI 320-2 shows the same behaviour
> but with different error messages. If helpful I could provide captured
> boot messages for this system, too.
>
Yes please.
> Any idea if this is a hypervisor or a kernel problem?
>
It looks like the kernel is having some problem mapping the device into
its address space, but it isn't clear where the problem lies.
Things to try:
1. boot with dom0 with <4G and <2G RAM and see if that changes the
behaviour (dom0_mem= on the Xen command line)
2. boot Xen with iommu=off (though I'm not sure it gets used on AMD
systems?)
3. try a newer version of Xen (3.4.2, 3.4.3-rc or 4.0.0)
4. try a current xen.git xen/stable-2.6.32.x kernel
Thanks,
J
next prev parent reply other threads:[~2010-05-06 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 13:25 Areca RAID with Xen 3.4 and Linux 2.6.32 dom0 Florian Wagner
2010-05-06 18:07 ` Jeremy Fitzhardinge [this message]
2010-05-07 8:54 ` Florian Wagner
2010-05-07 18:25 ` Jeremy Fitzhardinge
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=4BE3054D.8070500@goop.org \
--to=jeremy@goop.org \
--cc=f_wagner@syscomp.de \
--cc=konrad.wilk@oracle.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 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.