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] vcpu-pin cause dom0 kernel panic

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] vcpu-pin cause dom0 kernel panic
From: Andrew Xu <xu.an@xxxxxxxxxx>
Date: Fri, 20 May 2011 09:33:58 +0800
Cc: yunhong.jiang@xxxxxxxxx
Delivery-date: Thu, 19 May 2011 18:34:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I use xen 4.0(dom0 is suse11.sp1,2.6.32 x86_64) on 
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.zip)

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.
Anyone can help me?

I download megaraid_sas_05.30 driver from LSI web:

Attachment: pin-1-5.30.bmp.zip
Description: Zip compressed data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>