Hi the patch works and we are able to
insert the module in the kernel. Subsequently we’re dedicating the MgaRAID SAS
card to an HVM guest as well but once that is done we’re unable to see the
volumes i.e. the disk is not showing up through fdisk –l in the HVM guest. The
error received on the dmesg of HVM is that the firmware doesn’t initialize: -
megasas: 00.00.03.01 Sun May 14 22:49:52 PDT 2006
megasas: 0x1000:0x0411:0x1000:0x1008: bus 0:slot 6:func 0
PCI: Enabling device 0000:00:06.0 (0080 -> 0082)
ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 40 (level,
low) -> IRQ 169
megasas: Waiting for FW to come to ready state
megasas: Failed to init firmware
ACPI: PCI interrupt for device 0000:00:06.0 disabled
This Megasas card however worked fine on an HVM on a dell
dq35 machine. Does anyone face the same issue?
Bhaskar.
From: Han, Weidong
[mailto:weidong.han@xxxxxxxxx]
Sent: Thursday, September 18, 2008
12:02 PM
To: Kumar,
Venkat
Cc: Cui, Dexuan; xen-devel@xxxxxxxxxxxxxxxxxxx;
espen.skoglund@xxxxxxxxxxxxx
Subject: RE: Megaraid SAS driver
failing in Xen-3.3.0 but was working in Xen-3.2.2-rc3
per this log, we can see the context
mapping is not created for 02:0e.0.
I checked the code, I suspect context
mapping() for PCI device is incorrect (see case DEV_TYPE_PCI block code in
domain_context_mapping()). Obviously the PCI device is not mapped. Espen
changed this code in c/s 17972. Espen, can you give some explanation?
Venkat, pls try attached patch. and pls
post your "lspci -v" output.
Randy (Weidong)
From: Kumar, Venkat [mailto:Venkat.Kumar@xxxxxxx]
Sent: 2008年9月18日 12:45
To: Han, Weidong
Cc: Cui, Dexuan;
xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: Megaraid SAS driver
failing in Xen-3.3.0 but was working in Xen-3.2.2-rc3
Hi Randy,
I am attaching the complete output in a
file.
But for your reference, a part of it I am
pasting in the body.
==================================================================================
(XEN) PCI add device 02:0e.0
(XEN) [VT-D]iommu.c:775: iommu_page_fault:
iommu->reg = ffff828bfff55000
(XEN) [VT-D]iommu.c:744:
iommu_fault_status: Fault Overflow
(XEN) [VT-D]iommu.c:729: iommu_fault:DMA
Write: 2:e.0 addr cddf2000 REASON 2 iommu->reg = ffff828bfff55000
(XEN) print_vtd_entries: iommu =
ffff8300cde0db00 bdf = 2:e:0 gmfn = cddf2
(XEN) root_entry =
ffff83012bfe5000
(XEN)
root_entry[2] = 12779e001
(XEN) context =
ffff83012779e000
(XEN) context[70]
= 0_0
(XEN)
ctxt_entry[70] not present
(XEN) PCI add device 00:1b.0
(XEN) PCI remove device
02:0e.0
==================================================================================
02:0e.0 is the pci id of Megaraid SAS
controller.
For some reason you can see that the
device is removed.
I guess this output would give you some
idea.
Thx,
Venkat
From: Han, Weidong
[mailto:weidong.han@xxxxxxxxx]
Sent: Thursday, September 18, 2008
8:01 AM
To: Kumar,
Venkat; xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: Cui, Dexuan
Subject: RE: Megaraid SAS driver
failing in Xen-3.3.0 but was working in Xen-3.2.2-rc3
Venkat,
Can you post the serial console output?
Randy (Weidong)
From: Kumar, Venkat [mailto:Venkat.Kumar@xxxxxxx]
Sent: 2008年9月17日 20:38
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: Han, Weidong; Cui, Dexuan
Subject: Megaraid SAS driver
failing in Xen-3.3.0 but was working in Xen-3.2.2-rc3
On Xen-3.3.0, domain0 Megaraid SAS (SAS 1068 controller)
driver is not loading correctly if vtd support in Xen is enabled.
It fails at the point of initializing firmware.
I wasn’t seeing this error with Xen-3.2.2-rc3 (Unstable
version), though with vtd disabled in Xen-3.3.0, it is working.
Looks like a degrade problem.
Any clues?
Home