From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Xu <xu.an@cloudex.cn>
Cc: xen-devel@lists.xensource.com, yunhong.jiang@intel.com
Subject: Re: vcpu-pin cause dom0 kernel panic
Date: Tue, 24 May 2011 10:01:50 -0400 [thread overview]
Message-ID: <20110524140150.GE10926@dumpdata.com> (raw)
In-Reply-To: <20110519210823.9595.3A8D29D5@cloudex.cn>
On Thu, May 19, 2011 at 09:08:24PM +0800, Andrew Xu wrote:
> I use xen 4.0(dom0 is suse11.sp1,2.6.32 x86_64) on
Did you open a Bugzilla with SLES?
> Dell R710 with PERC H700 RAID adapter.
> --Intel(R) Xeon(R) CPU E5620 @ 2.40GHz
> --8 CPU cores.
> --Memory 64G
> --RAID5 4.5T
>
> When I dedicated (pin) a CPU core only for dom0 use.
> (I specify "dom0_max_vcpus=1 dom0_vcpus_pin" options for Xen)
> I got dom0 kernel panic error(pin-1-5.30.bmp)
>
> When I pin 2 core to dom0, the dom0 system can boot up,
> but it can't find any disk devices.
>
> But when I pin 4 core to dom0, it run OK.
>
> Does anyone can help me, please.
>
> I have read this mail, and updated my megaraid_sas to version 05.30.
> http://xen.1045712.n5.nabble.com/HOWTO-Update-megaraid-sas-driver-in-Linux-2-6-32-x-to-make-it-boot-and-work-with-Dell-LSI-RAID-adapts-td3254332.html
> Anyone can help me?
>
> I download megaraid_sas_05.30 driver from LSI web:
> http://www.lsi.com/storage_home/products_home/internal_raid/megaraid_sas/6gb_s_value_line/sas9260-8i/index.html
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-05-24 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 13:08 vcpu-pin cause dom0 kernel panic Andrew Xu
2011-05-24 14:01 ` Konrad Rzeszutek Wilk [this message]
2011-05-27 9:38 ` Re[2]: " Andrew Xu
2011-05-30 1:12 ` Re[3]: " Andrew Xu
2011-05-31 14:12 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2011-05-20 1:33 Andrew Xu
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=20110524140150.GE10926@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=xu.an@cloudex.cn \
--cc=yunhong.jiang@intel.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.