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年11月27日 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年11月27日 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年11月27日 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
