WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] FW: megaraid sas driver failing in Xen-3.4 unstable vers

To: "Han, Weidong" <weidong.han@xxxxxxxxx>
Subject: RE: [Xen-devel] FW: megaraid sas driver failing in Xen-3.4 unstable version
From: "Manyam, Ramesh" <Ramesh.Manyam@xxxxxxx>
Date: Mon, 1 Dec 2008 17:52:08 +0530
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 01 Dec 2008 04:27:30 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <715D42877B251141A38726ABF5CABF2C018BF05473@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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
Thread-index: AclKUUqAqjX7sXkZQo2R2NdSe87UjAGGPCaQAABzT6AAAGi28AAAgXsQAACQb9AABCXpQAC8ncYgAAMxCEAACmBTcA==
Thread-topic: [Xen-devel] FW: megaraid sas driver failing in Xen-3.4 unstable version

 

I am using 4 port MegaRAID SAS Controller card and only one disk is connected to this controller (only one port we are using). When I tried to bind the device 0000:02:09.0 to pciback driver it saying “no such device”. Is there any other way to bind this device to pciback driver?

 

When I remove MegaRAID SAS Controller card from the machine I couldn’t find this device (02:09.0) in “xm dmesg” after dedicating onboard SAS Controller to Linux HVM.

 

 

 

Thanks,

Ramesh

 


From: Han, Weidong [mailto:weidong.han@xxxxxxxxx]
Sent: Monday, December 01, 2008 12:35 PM
To: Manyam, Ramesh
Cc: 'xen-devel@xxxxxxxxxxxxxxxxxxx'
Subject: RE: [Xen-devel] FW: megaraid sas driver failing in Xen-3.4 unstable version

 

02:09.0 is just 2:9.0. I found lots of page faults of this device on xmdmesg.

 

Per your lspci -v output, I can know 02:0e.0 is under the PCI bridge 00:01.0.device 02:09.0 is under the same bridge. You must assign all the pci devices under the same PCI bridge to the same guest. But it's curious we cannot find 02:09.0 in lspci whilc there are its DMR page faults. The reason (REASON 2) is that it is not mapped in VT-d context table.

 

Regards,

Weidong

 


From: Manyam, Ramesh [mailto:Ramesh.Manyam@xxxxxxx]
Sent: 2008
121 13:32
To: Han, Weidong
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] FW: megaraid sas driver failing in Xen-3.4 unstable version

 

I found 2:9.0 in xmdmesg but not 02:09.0

 

Where you found 02:09.0?

 

Yes, 02:09.0 is not showed in lspci –v

 

Why you are so specific to 02:09.0?

 

Device 02:0e.0 is the MegaRAID SAS controller not 02:09.0

 

 


From: Han, Weidong [mailto:weidong.han@xxxxxxxxx]
Sent: Thursday, November 27, 2008 7:58 PM
To: Manyam, Ramesh
Cc: 'xen-devel@xxxxxxxxxxxxxxxxxxx'
Subject: RE: [Xen-devel] FW: megaraid sas driver failing in Xen-3.4 unstable version

 

what's 02:09.0? why is it not showed in lspci -v?

 


From: Manyam, Ramesh [mailto:Ramesh.Manyam@xxxxxxx]
Sent: 2008
1127 18:51
To: Han, Weidong
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] FW: megaraid sas driver failing in Xen-3.4 unstable version

 

Yes I used docs/misc/vtd.txt

 

Device 02:0e.0 is the MegaRAID SAS controller not 02:09.0

 

I am attaching the lspci output and the log messages of Xen & HVM. Please find them with this email

 

Xen log messages (xmdmesg)

HVM guest kernel log messages (hvm_dmesg_with_msi_1st_time)

Domain0 Kernel log messages (dom0_var_log_messages)

 

Now I destroyed the HVM guest and created HVM guest again

 

HVM guest kernel log messages (hvm_dmesg_with_msi_2nd_time)

 

 

 

 


From: Han, Weidong [mailto:weidong.han@xxxxxxxxx]
Sent: Thursday, November 27, 2008 2:43 PM
To: Manyam, Ramesh
Cc: 'xen-devel@xxxxxxxxxxxxxxxxxxx'
Subject: RE: [Xen-devel] FW: megaraid sas driver failing in Xen-3.4 unstable version

 

Did you use VT-d followed docs/misc/vtd.txt?

 

Per xmdmesg file, device 02:09.0 didn't be mapped in context sucessfully. Is device 02:09.0 the MegaRAID SAS controller? Can you post "lspci -v" output?

 

 

 


From: Manyam, Ramesh [mailto:Ramesh.Manyam@xxxxxxx]
Sent: 2008
1127 16:57
To: Han, Weidong
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] FW: megaraid sas driver failing in Xen-3.4 unstable version

VT-d support is enabled

 

Here I am attaching three files dmesg (hvm dmesgs), dom0_varlogmessages and xmdmesg

 

Thanks,

Ramesh


From: Han, Weidong [mailto:weidong.han@xxxxxxxxx]
Sent: Thursday, November 27, 2008 2:18 PM
To: Manyam, Ramesh; 'xen-devel@xxxxxxxxxxxxxxxxxxx'
Subject: RE: [Xen-devel] FW: megaraid sas driver failing in Xen-3.4 unstable version

 

you mean you assign MegaRAID SAS controller with VT-d to your guest?

 

You'd better provide more info, such as serial output, so people can be easy to help you.

 

Regards,

Weidong

 


From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Manyam, Ramesh
Sent: 2008
1127 16:36
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] FW: megaraid sas driver failing in Xen-3.4 unstable version

A gentle reminder on this issue

 

Please can any one help on this problem?

 


From: Manyam, Ramesh
Sent: Wednesday, November 19, 2008 7:46 PM
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: megaraid sas driver failing in Xen-3.4 unstable version

 

 

On Xen-3.4 (unstable version), I have created CentOS HVM guest & WS2K8 HVM guest and dedicated MegaRAID SAS controller but I am not able to see the disk which is connected to MegaRAID SAS controller when I do fdisk l (vtd support is enabled in Xen).

 

Looks like the pci device(MegaRAID SAS controller) is getting dedicated successfully as I can see the device in the list of pci devices shown by lspci(on CentOS HVM).

 

00:06.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS

 

 

However the driver is not getting attached properly and fails with the following error

 

=======================================================================================

“dmesg” of HVM CentOS

megasas: Failed to init firmware

ACPI: PCI interrupt for device 0000:00:06.0 disabled

 

 

“/var/log/messages”

pciback 0000:02:0e.0: seizing device

 PCI: Enabling device 0000:02:0e.0 (0190 -> 0192)

 ACPI: PCI Interrupt 0000:02:0e.0[A] -> GSI 66 (level, low) -> IRQ 25

 ACPI: PCI interrupt for device 0000:02:0e.0 disabled

=======================================================================================

 

 

 

On WS2K8 HVM, I am able to see MegaRAID SAS controller under “Storage Controllers” on WS2K8 HVM and the status of device is

 

=========================================================================================================================================================

This device cannot start.(Code 10)

Description:

 Windows was able to successfully install device driver software, but the driver software encountered a problem when it tried to run. The problem code is   

 10.

Problem Signature:

 Problem Event Name:PnPDeviceProblemCode

 Architecture: x86

 Hardware Id: PCI\VEN_1000&DEV_0411&SUBSYS_10081000&REV_00

 Setup class GUID: {4d36e97b-e325-11ce-bfc1-08002be10318}

 PnP problem code: 0000000A

 Driver name: megasas.sys

 Driver version: 2.13.0.32

 Driver date: 01-19-2008

 OS Version: 6.0.6001.2.1.0.272.7

 Locale ID: 1033

 ========================================================================================================================================================

And also I am not able to see the disk which is connected to MegaRAID SAS controller

 

============================================================================

“/var/log/messages”

pciback 0000:02:0e.0: seizing device

PCI: Enabling device 0000:02:0e.0 (0190 -> 0192)

ACPI: PCI Interrupt 0000:02:0e.0[A] -> GSI 66 (level, low) -> IRQ 25

ACPI: PCI interrupt for device 0000:02:0e.0 disabled

============================================================================

 

 

Any clues ?

 

Thanks,

Ramesh

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • RE: [Xen-devel] FW: megaraid sas driver failing in Xen-3.4 unstable version, Manyam, Ramesh <=