* Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU
@ 2009-03-30 13:27 Tim Moore
0 siblings, 0 replies; 10+ messages in thread
From: Tim Moore @ 2009-03-30 13:27 UTC (permalink / raw)
To: 'xen-devel@lists.xensource.com'
[-- Attachment #1.1: Type: text/plain, Size: 3608 bytes --]
Hi
I have been testing xen-unstable.hg (29/03/09) over the past few days .. trying to enable passthrough for VGA.
I am using Debian 5.0 (lenny) x64 and compiling from source each time. Tried both linux-2.6.18.8 and linux-2.6.27.5 from Xenbits ...
Hardware is Nvidia Geforce 8800 512mb GTS PCIe on Intel X58 (ASUS P6T Deluxe) with Core i7 920 CPU.
(had to hack the xen/drviers/pci/passthrough/vtd/dmar.c (line 388) and remove the DMAR bail because of bad RMRR tables.
I also have ATI X300 PCIe for Dom0 Console.
Using Xen parameter: iommu=passthrough,pv
Using Dom) parameter: pciback.hide=('...')
I compiled pciback as embedded in the kernel and I have tried many different scenarios:
1) Nvidia Primary (hidden with pciback.hide= kernel param) (no ATI card installed)
2) ATI Primary, with Nvidia hidden (with pciback.hide= kernel param)
3) all scenarios with pciback as module and using echo devn > /sys/bus/pci/drivers/pciback/new_slot and bind
In all scenarios I can successfully see the correct PCI device in the DomU(s), I have tried primarily Windows XP 32bit SP3 and also: linux-2.6.18.8 and linux-2.6.27.5 PV and non PV kernels as DomU and (although I didn't load a driver) the lspci -vvv showed the devices.
Now, I progressed to installing drivers under the Win32 DomU against the Nvidia card, windows correctly identified the device and installed the driver! (latest from nvidia.com). As we all know - Windows wanted a reboot- beforehand a quick check of the device and it has a Yellow exclamation indicating reboot required and resources unavailable.
Reboot and XP starts up ... BSOD .. nv4 driver fails .. :(
Tried with the ATI X300 Primary (no NVidia connected) and went through the same steps. Windows XP now boots without crash although the ATI device still shows a yellow exclamation and insufficient resources.
To summarise, pciback functions as expected for PCIe in Dom0 and DomU sees the device. All tools work fine (xm pci-attach / pci-detach / pci-list) and devid show and are managed correctly.
I have read all that there is on this subject and have come to the conclusion that this is a problem with qemu-dm and the memory mapping for the new Video device, the Cirrus or stdvga card is always present which I believe may be causing the problem. I have tried nographics=1 but qemu-dm still maps the Video BIOS.
Then I noticed that qemu-dm has the new options for "-vga none" .. so I built a wrapper script for qemu-dm to launch with this param. Unfortuntately the DomU doesn't startup and the qemu log does not show any mention of the Video memory ! so I believe the switch works, but the DomU then fails to boot :(
To solve this and make it usable I think some development of qemu with regards to the Cirrus VGA and memory management when using more than 1 vga controller is necessary in order to remap the Cirrus or secondary vga adapters in memory correctly. (its also difficult to configure a Windows machine for a second vga when the primary is disabled lol.)
Also, I have run strace using a qemu-dm wrapper (very verbose) and analysed the results -nothing seems obvious, but i`m not an expert by far ....
Windows has been able to support multiple VGA cards for a long time; I assume that MS is remapping these somehow?
I have read in 2 different places that this has worked for others before (without the legacy patch for igfx) and with xen-unstable.hg .. why does it not work for me ?
Any help / direction to further debug would be helpful .. I think many people would like to get this one working once and for all!
Tim
[-- Attachment #1.2: Type: text/html, Size: 10894 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU
@ 2009-03-30 13:35 Tim Moore
2009-03-30 14:03 ` Alexia Benington
2010-01-05 14:43 ` Fantu
0 siblings, 2 replies; 10+ messages in thread
From: Tim Moore @ 2009-03-30 13:35 UTC (permalink / raw)
To: 'xen-devel@lists.xensource.com'
[-- Attachment #1.1: Type: text/plain, Size: 3608 bytes --]
Hi
I have been testing xen-unstable.hg (29/03/09) over the past few days .. trying to enable passthrough for VGA.
I am using Debian 5.0 (lenny) x64 and compiling from source each time. Tried both linux-2.6.18.8 and linux-2.6.27.5 from Xenbits ...
Hardware is Nvidia Geforce 8800 512mb GTS PCIe on Intel X58 (ASUS P6T Deluxe) with Core i7 920 CPU.
(had to hack the xen/drviers/pci/passthrough/vtd/dmar.c (line 388) and remove the DMAR bail because of bad RMRR tables.
I also have ATI X300 PCIe for Dom0 Console.
Using Xen parameter: iommu=passthrough,pv
Using Dom) parameter: pciback.hide=('...')
I compiled pciback as embedded in the kernel and I have tried many different scenarios:
1) Nvidia Primary (hidden with pciback.hide= kernel param) (no ATI card installed)
2) ATI Primary, with Nvidia hidden (with pciback.hide= kernel param)
3) all scenarios with pciback as module and using echo devn > /sys/bus/pci/drivers/pciback/new_slot and bind
In all scenarios I can successfully see the correct PCI device in the DomU(s), I have tried primarily Windows XP 32bit SP3 and also: linux-2.6.18.8 and linux-2.6.27.5 PV and non PV kernels as DomU and (although I didn't load a driver) the lspci -vvv showed the devices.
Now, I progressed to installing drivers under the Win32 DomU against the Nvidia card, windows correctly identified the device and installed the driver! (latest from nvidia.com). As we all know - Windows wanted a reboot- beforehand a quick check of the device and it has a Yellow exclamation indicating reboot required and resources unavailable.
Reboot and XP starts up ... BSOD .. nv4 driver fails .. :(
Tried with the ATI X300 Primary (no NVidia connected) and went through the same steps. Windows XP now boots without crash although the ATI device still shows a yellow exclamation and insufficient resources.
To summarise, pciback functions as expected for PCIe in Dom0 and DomU sees the device. All tools work fine (xm pci-attach / pci-detach / pci-list) and devid show and are managed correctly.
I have read all that there is on this subject and have come to the conclusion that this is a problem with qemu-dm and the memory mapping for the new Video device, the Cirrus or stdvga card is always present which I believe may be causing the problem. I have tried nographics=1 but qemu-dm still maps the Video BIOS.
Then I noticed that qemu-dm has the new options for "-vga none" .. so I built a wrapper script for qemu-dm to launch with this param. Unfortuntately the DomU doesn't startup and the qemu log does not show any mention of the Video memory ! so I believe the switch works, but the DomU then fails to boot :(
To solve this and make it usable I think some development of qemu with regards to the Cirrus VGA and memory management when using more than 1 vga controller is necessary in order to remap the Cirrus or secondary vga adapters in memory correctly. (its also difficult to configure a Windows machine for a second vga when the primary is disabled lol.)
Also, I have run strace using a qemu-dm wrapper (very verbose) and analysed the results -nothing seems obvious, but i`m not an expert by far ....
Windows has been able to support multiple VGA cards for a long time; I assume that MS is remapping these somehow?
I have read in 2 different places that this has worked for others before (without the legacy patch for igfx) and with xen-unstable.hg .. why does it not work for me ?
Any help / direction to further debug would be helpful .. I think many people would like to get this one working once and for all!
Tim
[-- Attachment #1.2: Type: text/html, Size: 10894 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU
2009-03-30 13:35 Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU Tim Moore
@ 2009-03-30 14:03 ` Alexia Benington
2010-01-05 14:43 ` Fantu
1 sibling, 0 replies; 10+ messages in thread
From: Alexia Benington @ 2009-03-30 14:03 UTC (permalink / raw)
To: Tim Moore; +Cc: xen-devel@lists.xensource.com
Hi,
I've been trying to get this to work for some months, albeit not
full-time. I concur that many would like to see it working. Some have
posted that they managed to get it to work correctly, however, they
almost always never reply to queries on how they got it to work, or
their observations.
I did manage to get rid of the yellow exclamation mark. You'll need to
disable the emulated VGA bios, pretty much as described here
http://lists.xensource.com/archives/html/xen-devel/2008-12/msg00474.html.
Even after doing so, some of the registers are not directly passed
through. See http://lists.xensource.com/archives/html/xen-devel/2009-02/msg01131.html.
I'm not sure if that may affect anything.
I've experimented with an Intel DQ45CB, nVidia Quadro NVS 290, nVidia
GF9500, ATI Radion HD 2600XT. The best results I get are when using
the onboard igfx as the primary, which is also being passed through.
There is also a writeup which you might want to take a look
http://staff.science.uva.nl/~delaat/sne-2008-2009/p22/report.pdf.
I'm also trying to get DomU's output to the display.
-Alex
2009/3/30 Tim Moore <timothy.moore@expidas.net>:
> Hi
>
>
>
> I have been testing xen-unstable.hg (29/03/09) over the past few days ..
> trying to enable passthrough for VGA.
>
>
>
> I am using Debian 5.0 (lenny) x64 and compiling from source each time. Tried
> both linux-2.6.18.8 and linux-2.6.27.5 from Xenbits …
>
>
>
> Hardware is Nvidia Geforce 8800 512mb GTS PCIe on Intel X58 (ASUS P6T
> Deluxe) with Core i7 920 CPU.
>
> (had to hack the xen/drviers/pci/passthrough/vtd/dmar.c (line 388) and
> remove the DMAR bail because of bad RMRR tables.
>
> I also have ATI X300 PCIe for Dom0 Console.
>
>
>
> Using Xen parameter: iommu=passthrough,pv
>
> Using Dom) parameter: pciback.hide=(‘…’)
>
>
>
> I compiled pciback as embedded in the kernel and I have tried many different
> scenarios:
>
>
>
> 1) Nvidia Primary (hidden with pciback.hide= kernel param) (no ATI card
> installed)
>
> 2) ATI Primary, with Nvidia hidden (with pciback.hide= kernel param)
>
> 3) all scenarios with pciback as module and using echo devn >
> /sys/bus/pci/drivers/pciback/new_slot and bind
>
>
>
> In all scenarios I can successfully see the correct PCI device in the
> DomU(s), I have tried primarily Windows XP 32bit SP3 and also:
> linux-2.6.18.8 and linux-2.6.27.5 PV and non PV kernels as DomU and
> (although I didn’t load a driver) the lspci –vvv showed the devices.
>
>
>
> Now, I progressed to installing drivers under the Win32 DomU against the
> Nvidia card, windows correctly identified the device and installed the
> driver! (latest from nvidia.com). As we all know – Windows wanted a reboot-
> beforehand a quick check of the device and it has a Yellow exclamation
> indicating reboot required and resources unavailable.
>
> Reboot and XP starts up … BSOD .. nv4 driver fails .. L
>
>
>
> Tried with the ATI X300 Primary (no NVidia connected) and went through the
> same steps. Windows XP now boots without crash although the ATI device still
> shows a yellow exclamation and insufficient resources.
>
>
>
> To summarise, pciback functions as expected for PCIe in Dom0 and DomU sees
> the device. All tools work fine (xm pci-attach / pci-detach / pci-list) and
> devid show and are managed correctly.
>
>
>
> I have read all that there is on this subject and have come to the
> conclusion that this is a problem with qemu-dm and the memory mapping for
> the new Video device, the Cirrus or stdvga card is always present which I
> believe may be causing the problem. I have tried nographics=1 but qemu-dm
> still maps the Video BIOS.
>
>
>
> Then I noticed that qemu-dm has the new options for “-vga none” .. so I
> built a wrapper script for qemu-dm to launch with this param. Unfortuntately
> the DomU doesn’t startup and the qemu log does not show any mention of the
> Video memory ! so I believe the switch works, but the DomU then fails to
> boot L
>
>
>
> To solve this and make it usable I think some development of qemu with
> regards to the Cirrus VGA and memory management when using more than 1 vga
> controller is necessary in order to remap the Cirrus or secondary vga
> adapters in memory correctly. (its also difficult to configure a Windows
> machine for a second vga when the primary is disabled lol.)
>
>
>
> Also, I have run strace using a qemu-dm wrapper (very verbose) and analysed
> the results –nothing seems obvious, but i`m not an expert by far ….
>
>
>
> Windows has been able to support multiple VGA cards for a long time; I
> assume that MS is remapping these somehow?
>
>
>
> I have read in 2 different places that this has worked for others before
> (without the legacy patch for igfx) and with xen-unstable.hg .. why does it
> not work for me ?
>
>
>
> Any help / direction to further debug would be helpful .. I think many
> people would like to get this one working once and for all!
>
>
>
> Tim
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU
2009-03-30 13:35 Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU Tim Moore
2009-03-30 14:03 ` Alexia Benington
@ 2010-01-05 14:43 ` Fantu
2010-01-07 15:05 ` Pasi Kärkkäinen
1 sibling, 1 reply; 10+ messages in thread
From: Fantu @ 2010-01-05 14:43 UTC (permalink / raw)
To: xen-devel
I have asus p6t se (bios 0608 with vt-d enable) with core i7 920, nvidia 9800
gt and nvidia 8600 gt for passthrough.
I have installed lenny 64 bit with xen 4 from hg unstable and kernel
2.6.31.6 pv_ops from git but i was not been able to make vt-d working.
can you help me to resolve, please?
Tim Moore-13 wrote:
>
> Hi
>
> I have been testing xen-unstable.hg (29/03/09) over the past few days ..
> trying to enable passthrough for VGA.
>
> I am using Debian 5.0 (lenny) x64 and compiling from source each time.
> Tried both linux-2.6.18.8 and linux-2.6.27.5 from Xenbits ...
>
> Hardware is Nvidia Geforce 8800 512mb GTS PCIe on Intel X58 (ASUS P6T
> Deluxe) with Core i7 920 CPU.
> (had to hack the xen/drviers/pci/passthrough/vtd/dmar.c (line 388) and
> remove the DMAR bail because of bad RMRR tables.
> I also have ATI X300 PCIe for Dom0 Console.
>
> Using Xen parameter: iommu=passthrough,pv
> Using Dom) parameter: pciback.hide=('...')
>
> I compiled pciback as embedded in the kernel and I have tried many
> different scenarios:
>
> 1) Nvidia Primary (hidden with pciback.hide= kernel param) (no ATI card
> installed)
> 2) ATI Primary, with Nvidia hidden (with pciback.hide= kernel param)
> 3) all scenarios with pciback as module and using echo devn >
> /sys/bus/pci/drivers/pciback/new_slot and bind
>
> In all scenarios I can successfully see the correct PCI device in the
> DomU(s), I have tried primarily Windows XP 32bit SP3 and also:
> linux-2.6.18.8 and linux-2.6.27.5 PV and non PV kernels as DomU and
> (although I didn't load a driver) the lspci -vvv showed the devices.
>
> Now, I progressed to installing drivers under the Win32 DomU against the
> Nvidia card, windows correctly identified the device and installed the
> driver! (latest from nvidia.com). As we all know - Windows wanted a
> reboot- beforehand a quick check of the device and it has a Yellow
> exclamation indicating reboot required and resources unavailable.
> Reboot and XP starts up ... BSOD .. nv4 driver fails .. :(
>
> Tried with the ATI X300 Primary (no NVidia connected) and went through the
> same steps. Windows XP now boots without crash although the ATI device
> still shows a yellow exclamation and insufficient resources.
>
> To summarise, pciback functions as expected for PCIe in Dom0 and DomU sees
> the device. All tools work fine (xm pci-attach / pci-detach / pci-list)
> and devid show and are managed correctly.
>
> I have read all that there is on this subject and have come to the
> conclusion that this is a problem with qemu-dm and the memory mapping for
> the new Video device, the Cirrus or stdvga card is always present which I
> believe may be causing the problem. I have tried nographics=1 but qemu-dm
> still maps the Video BIOS.
>
> Then I noticed that qemu-dm has the new options for "-vga none" .. so I
> built a wrapper script for qemu-dm to launch with this param.
> Unfortuntately the DomU doesn't startup and the qemu log does not show any
> mention of the Video memory ! so I believe the switch works, but the DomU
> then fails to boot :(
>
> To solve this and make it usable I think some development of qemu with
> regards to the Cirrus VGA and memory management when using more than 1 vga
> controller is necessary in order to remap the Cirrus or secondary vga
> adapters in memory correctly. (its also difficult to configure a Windows
> machine for a second vga when the primary is disabled lol.)
>
> Also, I have run strace using a qemu-dm wrapper (very verbose) and
> analysed the results -nothing seems obvious, but i`m not an expert by far
> ....
>
> Windows has been able to support multiple VGA cards for a long time; I
> assume that MS is remapping these somehow?
>
> I have read in 2 different places that this has worked for others before
> (without the legacy patch for igfx) and with xen-unstable.hg .. why does
> it not work for me ?
>
> Any help / direction to further debug would be helpful .. I think many
> people would like to get this one working once and for all!
>
> Tim
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
--
View this message in context: http://old.nabble.com/Memory-mapping-for-PEG-PCIe-Graphics-Passthrough-to-%3Cany%3E-DomU-tp22783371p27026626.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU
2010-01-05 14:43 ` Fantu
@ 2010-01-07 15:05 ` Pasi Kärkkäinen
2010-01-07 16:14 ` Fantu
0 siblings, 1 reply; 10+ messages in thread
From: Pasi Kärkkäinen @ 2010-01-07 15:05 UTC (permalink / raw)
To: Fantu; +Cc: xen-devel
On Tue, Jan 05, 2010 at 06:43:05AM -0800, Fantu wrote:
>
> I have asus p6t se (bios 0608 with vt-d enable) with core i7 920, nvidia 9800
> gt and nvidia 8600 gt for passthrough.
> I have installed lenny 64 bit with xen 4 from hg unstable and kernel
> 2.6.31.6 pv_ops from git but i was not been able to make vt-d working.
> can you help me to resolve, please?
>
Please post your "xm dmesg" log.. let's start with that.
-- Pasi
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU
2010-01-07 15:05 ` Pasi Kärkkäinen
@ 2010-01-07 16:14 ` Fantu
2010-01-07 21:07 ` Pasi Kärkkäinen
0 siblings, 1 reply; 10+ messages in thread
From: Fantu @ 2010-01-07 16:14 UTC (permalink / raw)
To: xen-devel
i have grub2 also here and i have add dummy=foo before root...
xm dmesg
])
(XEN) IOAPIC[1]: apic_id 9, version 32, address 0xfec8a000, GSI 24-47
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
(XEN) [VT-D]dmar.c:548: Host address width 39
(XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:374: dmaru->address = fbfff000
(XEN) [VT-D]dmar.c:326: endpoint: 0:1b.0
(XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:374: dmaru->address = fbffe000
(XEN) [VT-D]dmar.c:331: IOAPIC: f0:1f.7
(XEN) [VT-D]dmar.c:331: IOAPIC: 0:13.0
(XEN) [VT-D]dmar.c:386: flags: INCLUDE_ALL
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:446: RMRR region: base_addr ec000 end_address effff
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.0
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.1
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.2
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.7
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.0
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.1
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.2
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.7
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:417: RMRR error: base_addr bf7dc000 end_address bf7dbfff
(XEN) Failed to parse ACPI DMAR. Disabling VT-d.
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
(XEN) PCI: Not using MMCONFIG.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2672.800 MHz processor.
(XEN) Initing memory sharing.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM1)
(XEN) I/O virtualisation disabled
(XEN) CPU0: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 1/2 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM1)
(XEN) CPU1: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 2/4 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM1)
(XEN) CPU2: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 3/6 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM1)
(XEN) CPU3: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 4/1 eip 8c000
(XEN) Initializing CPU#4
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#4.
(XEN) CPU4: Thermal monitoring enabled (TM1)
(XEN) CPU4: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 5/3 eip 8c000
(XEN) Initializing CPU#5
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#5.
(XEN) CPU5: Thermal monitoring enabled (TM1)
(XEN) CPU5: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 6/5 eip 8c000
(XEN) Initializing CPU#6
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#6.
(XEN) CPU6: Thermal monitoring enabled (TM1)
(XEN) CPU6: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 7/7 eip 8c000
(XEN) Initializing CPU#7
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#7.
(XEN) CPU7: Thermal monitoring enabled (TM1)
(XEN) CPU7: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Total of 8 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 8 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) microcode.c:73:d32767 microcode: CPU1 resumed
(XEN) microcode.c:73:d32767 microcode: CPU6 resumed
(XEN) microcode.c:73:d32767 microcode: CPU4 resumed
(XEN) microcode.c:73:d32767 microcode: CPU3 resumed
(XEN) microcode.c:73:d32767 microcode: CPU5 resumed
(XEN) microcode.c:73:d32767 microcode: CPU7 resumed
(XEN) microcode.c:73:d32767 microcode: CPU2 resumed
(XEN) Brought up 8 CPUs
(XEN) HPET: 4 timers in total, 0 timers will be used for broadcast
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x82a000
(XEN) elf_parse_binary: phdr: paddr=0x182a000 memsz=0xe5108
(XEN) elf_parse_binary: phdr: paddr=0x1910000 memsz=0x888
(XEN) elf_parse_binary: phdr: paddr=0x1911000 memsz=0x15ca0
(XEN) elf_parse_binary: phdr: paddr=0x1926ca0 memsz=0x1a9360
(XEN) elf_parse_binary: memory: 0x1000000 -> 0x1ad0000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff81926ea0
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81009000
(XEN) elf_xen_parse_note: FEATURES =
"!writable_page_tables|pae_pgdir_above_4gb"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) elf_xen_addr_calc_check: addresses:
(XEN) virt_base = 0xffffffff80000000
(XEN) elf_paddr_offset = 0x0
(XEN) virt_offset = 0xffffffff80000000
(XEN) virt_kstart = 0xffffffff81000000
(XEN) virt_kend = 0xffffffff81ad0000
(XEN) virt_entry = 0xffffffff81926ea0
(XEN) p2m_base = 0xffffffffffffffff
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1ad0000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 00000001b4000000->00000001b8000000 (114688 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff81ad0000
(XEN) Init. ramdisk: ffffffff81ad0000->ffffffff81ed7400
(XEN) Phys-Mach map: ffffffff81ed8000->ffffffff81fd8000
(XEN) Start info: ffffffff81fd8000->ffffffff81fd84b4
(XEN) Page tables: ffffffff81fd9000->ffffffff81fee000
(XEN) Boot stack: ffffffff81fee000->ffffffff81fef000
(XEN) TOTAL: ffffffff80000000->ffffffff82400000
(XEN) ENTRY ADDRESS: ffffffff81926ea0
(XEN) Dom0 has maximum 8 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff8182a000
(XEN) elf_load_binary: phdr 1 at 0xffffffff8182a000 -> 0xffffffff8190f108
(XEN) elf_load_binary: phdr 2 at 0xffffffff81910000 -> 0xffffffff81910888
(XEN) elf_load_binary: phdr 3 at 0xffffffff81911000 -> 0xffffffff81926ca0
(XEN) elf_load_binary: phdr 4 at 0xffffffff81926ca0 -> 0xffffffff819a4000
(XEN) Scrubbing Free RAM:
.......................................................done.
(XEN) Xen trace buffers: disabled
(XEN) tmem: initialized comp=0 global-lock=0
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to switch
input to Xen)
(XEN) Freed 156kB init memory.
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=0, irq=0
(XEN) ioapic_guest_write: new_entry=00010900
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=2, irq=0
(XEN) ioapic_guest_write: new_entry=00010900
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) irq.c:1431: dom0: pirq 0 or irq 3 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 4 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 5 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 6 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 7 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 8 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 9 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 10 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 11 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 12 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 13 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 14 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 15 already mapped
(XEN) allocated vector for irq:16
(XEN) irq.c:1431: dom0: pirq 0 or irq 16 already mapped
(XEN) allocated vector for irq:17
(XEN) irq.c:1431: dom0: pirq 0 or irq 17 already mapped
(XEN) allocated vector for irq:18
(XEN) irq.c:1431: dom0: pirq 0 or irq 18 already mapped
(XEN) allocated vector for irq:20
(XEN) irq.c:1431: dom0: pirq 0 or irq 20 already mapped
(XEN) allocated vector for irq:21
(XEN) irq.c:1431: dom0: pirq 0 or irq 21 already mapped
(XEN) allocated vector for irq:22
(XEN) irq.c:1431: dom0: pirq 0 or irq 22 already mapped
(XEN) allocated vector for irq:23
(XEN) irq.c:1431: dom0: pirq 0 or irq 23 already mapped
(XEN) allocated vector for irq:24
(XEN) irq.c:1431: dom0: pirq 0 or irq 24 already mapped
(XEN) allocated vector for irq:25
(XEN) irq.c:1431: dom0: pirq 0 or irq 25 already mapped
(XEN) allocated vector for irq:26
(XEN) irq.c:1431: dom0: pirq 0 or irq 26 already mapped
(XEN) allocated vector for irq:27
(XEN) irq.c:1431: dom0: pirq 0 or irq 27 already mapped
(XEN) allocated vector for irq:28
(XEN) irq.c:1431: dom0: pirq 0 or irq 28 already mapped
(XEN) allocated vector for irq:29
(XEN) irq.c:1431: dom0: pirq 0 or irq 29 already mapped
(XEN) allocated vector for irq:30
(XEN) irq.c:1431: dom0: pirq 0 or irq 30 already mapped
(XEN) allocated vector for irq:31
(XEN) irq.c:1431: dom0: pirq 0 or irq 31 already mapped
(XEN) allocated vector for irq:32
(XEN) irq.c:1431: dom0: pirq 0 or irq 32 already mapped
(XEN) allocated vector for irq:33
(XEN) irq.c:1431: dom0: pirq 0 or irq 33 already mapped
(XEN) allocated vector for irq:34
(XEN) irq.c:1431: dom0: pirq 0 or irq 34 already mapped
(XEN) allocated vector for irq:35
(XEN) irq.c:1431: dom0: pirq 0 or irq 35 already mapped
(XEN) allocated vector for irq:36
(XEN) irq.c:1431: dom0: pirq 0 or irq 36 already mapped
(XEN) allocated vector for irq:37
(XEN) irq.c:1431: dom0: pirq 0 or irq 37 already mapped
(XEN) allocated vector for irq:38
(XEN) irq.c:1431: dom0: pirq 0 or irq 38 already mapped
(XEN) allocated vector for irq:39
(XEN) irq.c:1431: dom0: pirq 0 or irq 39 already mapped
(XEN) allocated vector for irq:40
(XEN) irq.c:1431: dom0: pirq 0 or irq 40 already mapped
(XEN) allocated vector for irq:41
(XEN) irq.c:1431: dom0: pirq 0 or irq 41 already mapped
(XEN) allocated vector for irq:42
(XEN) irq.c:1431: dom0: pirq 0 or irq 42 already mapped
(XEN) allocated vector for irq:43
(XEN) irq.c:1431: dom0: pirq 0 or irq 43 already mapped
(XEN) allocated vector for irq:44
(XEN) irq.c:1431: dom0: pirq 0 or irq 44 already mapped
(XEN) allocated vector for irq:45
(XEN) irq.c:1431: dom0: pirq 0 or irq 45 already mapped
(XEN) allocated vector for irq:46
(XEN) irq.c:1431: dom0: pirq 0 or irq 46 already mapped
(XEN) allocated vector for irq:47
(XEN) irq.c:1431: dom0: pirq 0 or irq 47 already mapped
(XEN) tmem_relinquish_page: failing order=6
(XEN) tmem_relinquish_page: failing order=6
(XEN) tmem_relinquish_page: failing order=6
(XEN) tmem_relinquish_page: failing order=6
(XEN) tmem_relinquish_page: failing order=6
(XEN) tmem_relinquish_page: failing order=6
(XEN) tmem_relinquish_page: failing order=6
(XEN) tmem_relinquish_page: failing order=6
(XEN) tmem_relinquish_page: failing order=6
(XEN) tmem_relinquish_page: failing order=3
(XEN) tmem_relinquish_page: failing order=3
(XEN) tmem_relinquish_page: failing order=3
(XEN) tmem_relinquish_page: failing order=3
(XEN) tmem_relinquish_page: failing order=3
(XEN) tmem_relinquish_page: failing order=3
(XEN) tmem_relinquish_page: failing order=3
(XEN) tmem_relinquish_page: failing order=3
(XEN) tmem_relinquish_page: failing order=3
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=0, irq=0
(XEN) ioapic_guest_write: new_entry=00000900
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) PCI add device 00:00.0
(XEN) PCI add device 00:01.0
(XEN) PCI add device 00:03.0
(XEN) PCI add device 00:07.0
(XEN) PCI add device 00:14.0
(XEN) PCI add device 00:14.1
(XEN) PCI add device 00:14.2
(XEN) PCI add device 00:14.3
(XEN) PCI add device 00:1a.0
(XEN) PCI add device 00:1a.1
(XEN) PCI add device 00:1a.2
(XEN) PCI add device 00:1a.7
(XEN) PCI add device 00:1b.0
(XEN) PCI add device 00:1c.0
(XEN) PCI add device 00:1c.2
(XEN) PCI add device 00:1c.3
(XEN) PCI add device 00:1c.4
(XEN) PCI add device 00:1d.0
(XEN) PCI add device 00:1d.1
(XEN) PCI add device 00:1d.2
(XEN) PCI add device 00:1d.7
(XEN) PCI add device 00:1e.0
(XEN) PCI add device 00:1f.0
(XEN) PCI add device 00:1f.2
(XEN) PCI add device 00:1f.3
(XEN) PCI add device 02:00.0
(XEN) PCI add device 06:00.0
(XEN) PCI add device 05:00.0
(XEN) PCI add device 04:00.0
(XEN) PCI add device 04:00.1
(XEN) allocated vector for irq:19
(XEN) Set CPU acpi_id(1) cpuid(0) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(2) cpuid(1) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(3) cpuid(2) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(4) cpuid(3) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(5) cpuid(4) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(6) cpuid(5) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(7) cpuid(6) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(8) cpuid(7) Px State info:
(XEN) _PPC: 0
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=16, irq=16
(XEN) ioapic_guest_write: new_entry=0001a910
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=23, irq=23
(XEN) ioapic_guest_write: new_entry=0001a917
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=19, irq=19
(XEN) ioapic_guest_write: new_entry=0001a913
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=18, irq=18
(XEN) ioapic_guest_write: new_entry=0001a912
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=18, irq=18
(XEN) ioapic_guest_write: new_entry=0001a912
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
Pasi Kärkkäinen wrote:
>
> On Tue, Jan 05, 2010 at 06:43:05AM -0800, Fantu wrote:
>>
>> I have asus p6t se (bios 0608 with vt-d enable) with core i7 920, nvidia
>> 9800
>> gt and nvidia 8600 gt for passthrough.
>> I have installed lenny 64 bit with xen 4 from hg unstable and kernel
>> 2.6.31.6 pv_ops from git but i was not been able to make vt-d working.
>> can you help me to resolve, please?
>>
>
> Please post your "xm dmesg" log.. let's start with that.
>
> -- Pasi
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
--
View this message in context: http://old.nabble.com/Memory-mapping-for-PEG-PCIe-Graphics-Passthrough-to-%3Cany%3E-DomU-tp22783371p27062451.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU
2010-01-07 16:14 ` Fantu
@ 2010-01-07 21:07 ` Pasi Kärkkäinen
2010-01-08 2:45 ` Weidong Han
0 siblings, 1 reply; 10+ messages in thread
From: Pasi Kärkkäinen @ 2010-01-07 21:07 UTC (permalink / raw)
To: Fantu; +Cc: xen-devel
On Thu, Jan 07, 2010 at 08:14:47AM -0800, Fantu wrote:
>
> i have grub2 also here and i have add dummy=foo before root...
>
> xm dmesg
> ])
> (XEN) [VT-D]dmar.c:548: Host address width 39
> (XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
> (XEN) [VT-D]dmar.c:374: dmaru->address = fbfff000
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1b.0
> (XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
> (XEN) [VT-D]dmar.c:374: dmaru->address = fbffe000
> (XEN) [VT-D]dmar.c:331: IOAPIC: f0:1f.7
> (XEN) [VT-D]dmar.c:331: IOAPIC: 0:13.0
> (XEN) [VT-D]dmar.c:386: flags: INCLUDE_ALL
> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:446: RMRR region: base_addr ec000 end_address effff
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.0
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.1
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.2
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.7
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.0
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.1
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.2
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.7
> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:417: RMRR error: base_addr bf7dc000 end_address bf7dbfff
> (XEN) Failed to parse ACPI DMAR. Disabling VT-d.
>
This looks like you have a buggy BIOS, it doesn't have correct DMAR RMRR table..
When RMRR address range is not in reserved memory (BIOS issue), can use
'iommu_inclusive_mapping=1' to work around it.
So try that options for xen.gz in grub config.
http://wiki.xensource.com/xenwiki/VTdHowTo
-- Pasi
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU
2010-01-07 21:07 ` Pasi Kärkkäinen
@ 2010-01-08 2:45 ` Weidong Han
2010-01-08 9:18 ` Han, Weidong
0 siblings, 1 reply; 10+ messages in thread
From: Weidong Han @ 2010-01-08 2:45 UTC (permalink / raw)
To: Pasi Kärkkäinen; +Cc: xen-devel@lists.xensource.com, Fantu
[-- Attachment #1: Type: text/html, Size: 2731 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU
2010-01-08 2:45 ` Weidong Han
@ 2010-01-08 9:18 ` Han, Weidong
2010-01-11 14:15 ` Fantu
0 siblings, 1 reply; 10+ messages in thread
From: Han, Weidong @ 2010-01-08 9:18 UTC (permalink / raw)
To: Han, Weidong, Pasi Kärkkäinen
Cc: xen-devel@lists.xensource.com, Fantu
[-- Attachment #1.1: Type: text/plain, Size: 2506 bytes --]
Fantu,
Can you try with the attached patch? and pls post the output of "lspci -v"?
Regards,
Weidong
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Weidong Han
Sent: Friday, January 08, 2010 10:46 AM
To: Pasi Kärkkäinen
Cc: xen-devel@lists.xensource.com; Fantu
Subject: Re: [Xen-devel] Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU
Pasi Kärkkäinen wrote:
On Thu, Jan 07, 2010 at 08:14:47AM -0800, Fantu wrote:
i have grub2 also here and i have add dummy=foo before root...
xm dmesg
])
(XEN) [VT-D]dmar.c:548: Host address width 39
(XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:374: dmaru->address = fbfff000
(XEN) [VT-D]dmar.c:326: endpoint: 0:1b.0
(XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:374: dmaru->address = fbffe000
(XEN) [VT-D]dmar.c:331: IOAPIC: f0:1f.7
(XEN) [VT-D]dmar.c:331: IOAPIC: 0:13.0
(XEN) [VT-D]dmar.c:386: flags: INCLUDE_ALL
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:446: RMRR region: base_addr ec000 end_address effff
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.0
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.1
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.2
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.7
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.0
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.1
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.2
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.7
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:417: RMRR error: base_addr bf7dc000 end_address bf7dbfff
(XEN) Failed to parse ACPI DMAR. Disabling VT-d.
This looks like you have a buggy BIOS, it doesn't have correct DMAR RMRR table..
When RMRR address range is not in reserved memory (BIOS issue), can use
'iommu_inclusive_mapping=1' to work around it.
So try that options for xen.gz in grub config.
http://wiki.xensource.com/xenwiki/VTdHowTo
yes, obviously the RMRR is setting incorrectly in BIOS. The base address shouldn't be greater than end address. "iommu_inclusive_mapping=1" cannot help here. You should report this issue to the vendor and ask for a correct BIOS.
Regards,
Weidong
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 11396 bytes --]
[-- Attachment #2: fix-rmrr.patch --]
[-- Type: application/octet-stream, Size: 2177 bytes --]
diff -r cba56c13ca3e xen/drivers/passthrough/vtd/dmar.c
--- a/xen/drivers/passthrough/vtd/dmar.c Wed Jan 06 12:45:23 2010 +0000
+++ b/xen/drivers/passthrough/vtd/dmar.c Sat Jan 09 09:44:08 2010 +0800
@@ -410,14 +410,6 @@ acpi_parse_one_rmrr(struct acpi_dmar_ent
u64 base_addr = rmrr->base_address, end_addr = rmrr->end_address;
int ret = 0;
- if ( base_addr >= end_addr )
- {
- dprintk(XENLOG_ERR VTDPREFIX,
- "RMRR error: base_addr %"PRIx64" end_address %"PRIx64"\n",
- base_addr, end_addr);
- return -EFAULT;
- }
-
#ifdef CONFIG_X86
/* This check is here simply to detect when RMRR values are
* not properly represented in the system memory map and
@@ -452,8 +444,47 @@ acpi_parse_one_rmrr(struct acpi_dmar_ent
if ( ret || (rmrru->scope.devices_cnt == 0) )
xfree(rmrru);
+ else if ( base_addr >= end_addr )
+ {
+ u8 b, d, f;
+ u32 vendor;
+ int i, ignore = 0;
+
+ for ( i = 0; i < rmrru->scope.devices_cnt; i++ )
+ {
+ b = PCI_BUS(rmrru->scope.devices[i]);
+ d = PCI_SLOT(rmrru->scope.devices[i]);
+ f = PCI_FUNC(rmrru->scope.devices[i]);
+
+ vendor = pci_conf_read32(b, d, f, PCI_VENDOR_ID);
+ if ( (vendor == 0xffffffff) || (vendor == 0x00000000) ||
+ (vendor == 0x0000ffff) || (vendor == 0xffff0000) )
+ ignore = 1;
+ else
+ {
+ ignore = 0;
+ break;
+ }
+ }
+
+ if ( ignore )
+ dprintk(XENLOG_WARNING VTDPREFIX,
+ " Ignore incorrect RMRR (%"PRIx64", %"PRIx64") due to "
+ "devices under its scope are not PCI discoverable!\n",
+ rmrru->base_address, rmrru->end_address);
+ else
+ {
+ dprintk(XENLOG_WARNING VTDPREFIX,
+ " The RMRR (%"PRIx64", %"PRIx64") is incorrect!\n",
+ rmrru->base_address, rmrru->end_address);
+ ret = -EFAULT;
+ }
+
+ xfree(rmrru);
+ }
else
acpi_register_rmrr_unit(rmrru);
+
return ret;
}
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU
2010-01-08 9:18 ` Han, Weidong
@ 2010-01-11 14:15 ` Fantu
0 siblings, 0 replies; 10+ messages in thread
From: Fantu @ 2010-01-11 14:15 UTC (permalink / raw)
To: xen-devel
I have try with patch, the problem persist, under the output of xm info, xm
dmesg and lspci -v:
lspci -v
00:00.0 Host bridge: Intel Corporation QuickPath Architecture I/O Hub to ESI
Port (rev 13)
Subsystem: ASUSTeK Computer Inc. Device 836b
Flags: fast devsel
Capabilities: [60] Message Signalled Interrupts: Mask+ 64bit-
Queue=0/1 Enable-
Capabilities: [90] Express Root Port (Slot-), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [150] Access Controls <?>
Capabilities: [160] Vendor Specific Information <?>
00:01.0 PCI bridge: Intel Corporation QuickPath Architecture I/O Hub PCI
Express Root Port 1 (rev 13) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Capabilities: [40] Subsystem: ASUSTeK Computer Inc. Device 836b
Capabilities: [60] Message Signalled Interrupts: Mask+ 64bit-
Queue=0/1 Enable+
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [150] Access Controls <?>
Capabilities: [160] Vendor Specific Information <?>
Kernel driver in use: pcieport-driver
00:03.0 PCI bridge: Intel Corporation QuickPath Architecture I/O Hub PCI
Express Root Port 3 (rev 13) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: f8000000-fbbfffff
Prefetchable memory behind bridge: 00000000d0000000-00000000dfffffff
Capabilities: [40] Subsystem: ASUSTeK Computer Inc. Device 836b
Capabilities: [60] Message Signalled Interrupts: Mask+ 64bit-
Queue=0/1 Enable+
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [150] Access Controls <?>
Capabilities: [160] Vendor Specific Information <?>
Kernel driver in use: pcieport-driver
00:07.0 PCI bridge: Intel Corporation QuickPath Architecture I/O Hub PCI
Express Root Port 7 (rev 13) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Capabilities: [40] Subsystem: ASUSTeK Computer Inc. Device 836b
Capabilities: [60] Message Signalled Interrupts: Mask+ 64bit-
Queue=0/1 Enable+
Capabilities: [90] Express Root Port (Slot+), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [150] Access Controls <?>
Capabilities: [160] Vendor Specific Information <?>
Kernel driver in use: pcieport-driver
00:14.0 PIC: Intel Corporation QuickPath Architecture I/O Hub System
Management Registers (rev 13) (prog-if 00 [8259])
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
00:14.1 PIC: Intel Corporation QuickPath Architecture I/O Hub GPIO and
Scratch Pad Registers (rev 13) (prog-if 00 [8259])
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
00:14.2 PIC: Intel Corporation QuickPath Architecture I/O Hub Control Status
and RAS Registers (rev 13) (prog-if 00 [8259])
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
00:14.3 PIC: Intel Corporation QuickPath Architecture I/O Hub Throttle
Registers (rev 13) (prog-if 00 [8259])
Flags: fast devsel
00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #4 (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device 82d4
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at a800 [size=32]
Capabilities: [50] PCIe advanced features <?>
Kernel driver in use: uhci_hcd
00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #5 (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device 82d4
Flags: bus master, medium devsel, latency 0, IRQ 21
I/O ports at a880 [size=32]
Capabilities: [50] PCIe advanced features <?>
Kernel driver in use: uhci_hcd
00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #6 (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device 82d4
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at ac00 [size=32]
Capabilities: [50] PCIe advanced features <?>
Kernel driver in use: uhci_hcd
00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI
Controller #2 (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. Device 82d4
Flags: bus master, medium devsel, latency 0, IRQ 18
Memory at f7fff000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCIe advanced features <?>
Kernel driver in use: ehci_hcd
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio
Controller
Subsystem: ASUSTeK Computer Inc. Device 8357
Flags: bus master, fast devsel, latency 0, IRQ 22
Memory at f7ff8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel <?>
Capabilities: [130] Root Complex Link <?>
Kernel driver in use: HDA Intel
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express
Port 1 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=07, subordinate=07, sec-latency=0
Prefetchable memory behind bridge: 00000000f6f00000-00000000f6ffffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable+
Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 8357
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel driver in use: pcieport-driver
00:1c.2 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express
Port 3 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: fbe00000-fbefffff
Prefetchable memory behind bridge: 00000000f6e00000-00000000f6efffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable+
Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 8357
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel driver in use: pcieport-driver
00:1c.3 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express
Port 4 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fbd00000-fbdfffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable+
Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 8357
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel driver in use: pcieport-driver
00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express
Port 5 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: fbc00000-fbcfffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable+
Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 8357
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel <?>
Capabilities: [180] Root Complex Link <?>
Kernel driver in use: pcieport-driver
00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #1 (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device 82d4
Flags: bus master, medium devsel, latency 0, IRQ 23
I/O ports at a080 [size=32]
Capabilities: [50] PCIe advanced features <?>
Kernel driver in use: uhci_hcd
00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #2 (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device 82d4
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at a400 [size=32]
Capabilities: [50] PCIe advanced features <?>
Kernel driver in use: uhci_hcd
00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI
Controller #3 (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device 82d4
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at a480 [size=32]
Capabilities: [50] PCIe advanced features <?>
Kernel driver in use: uhci_hcd
00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI
Controller #1 (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. Device 82d4
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at f7ffe000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCIe advanced features <?>
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) (prog-if 01
[Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=08, subordinate=08, sec-latency=32
Capabilities: [50] Subsystem: ASUSTeK Computer Inc. Device 82d4
00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface
Controller
Subsystem: ASUSTeK Computer Inc. Device 82d4
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information <?>
00:1f.2 RAID bus controller: Intel Corporation 82801 SATA RAID Controller
Subsystem: ASUSTeK Computer Inc. Device 82d4
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 828
I/O ports at 9c00 [size=8]
I/O ports at 9880 [size=4]
I/O ports at 9800 [size=8]
I/O ports at 9480 [size=4]
I/O ports at 9400 [size=32]
Memory at f7ffc000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/4 Enable+
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA <?>
Capabilities: [b0] PCIe advanced features <?>
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
Subsystem: ASUSTeK Computer Inc. Device 82d4
Flags: medium devsel, IRQ 18
Memory at f7ffd000 (64-bit, non-prefetchable) [size=256]
I/O ports at 0400 [size=32]
02:00.0 VGA compatible controller: nVidia Corporation Device 0640 (rev a1)
(prog-if 00 [VGA controller])
Flags: bus master, fast devsel, latency 0, IRQ 15
Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at f8000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at bc00 [size=128]
Expansion ROM at fbb80000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [b4] Vendor Specific Information <?>
Capabilities: [100] Virtual Channel <?>
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information <?>
04:00.0 SATA controller: JMicron Technologies, Inc. JMicron 20360/20363 AHCI
Controller (rev 03) (prog-if 01 [AHCI 1.0])
Subsystem: ASUSTeK Computer Inc. Device 824f
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at fbcfe000 (32-bit, non-prefetchable) [size=8K]
Expansion ROM at fbce0000 [disabled] [size=64K]
Capabilities: [68] Power Management version 2
Capabilities: [50] Express Legacy Endpoint, MSI 01
Kernel driver in use: ahci
04:00.1 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI
Controller (rev 03) (prog-if 85 [Master SecO PriO])
Subsystem: ASUSTeK Computer Inc. Device 824f
Flags: bus master, fast devsel, latency 0
I/O ports at cc00 [size=8]
I/O ports at c880 [size=4]
I/O ports at c800 [size=8]
I/O ports at c480 [size=4]
I/O ports at c400 [size=16]
Capabilities: [68] Power Management version 2
05:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. Device 3403 (prog-if 10
[OHCI])
Subsystem: ASUSTeK Computer Inc. Device 8384
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at fbdff000 (64-bit, non-prefetchable) [size=2K]
I/O ports at d800 [size=256]
Capabilities: [50] Power Management version 3
Capabilities: [80] Message Signalled Interrupts: Mask+ 64bit+
Queue=0/0 Enable-
Capabilities: [98] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [130] Device Serial Number 12-90-bd-ff-ff-8c-1e-00
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B
PCI Express Gigabit Ethernet controller (rev 02)
Subsystem: ASUSTeK Computer Inc. Device 82c6
Flags: bus master, fast devsel, latency 0, IRQ 827
I/O ports at e800 [size=256]
Memory at fbeff000 (64-bit, non-prefetchable) [size=4K]
Memory at f6ef0000 (64-bit, prefetchable) [size=64K]
Expansion ROM at fbec0000 [disabled] [size=128K]
Capabilities: [40] Power Management version 3
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable- Mask- TabSize=2
Capabilities: [d0] Vital Product Data <?>
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Virtual Channel <?>
Capabilities: [160] Device Serial Number 00-e0-4c-68-00-00-00-03
Kernel driver in use: r8169
xm info
host : vfarm
release : 2.6.31.6-xen
version : #2 SMP Mon Jan 11 14:33:17 CET 2010
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 2672
hw_caps :
bfebfbff:28100800:00000000:00001b40:0098e3bd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 6108
free_memory : 5546
node_to_cpu : node0:0-7
node_to_memory : node0:5546
node_to_dma32_mem : node0:2996
xen_major : 4
xen_minor : 0
xen_extra : .0-rc1-pre
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Sat Jan 09 08:14:44 2010 +0000 20779:596f7893b5ac
xen_commandline : dom0_mem=512M iommu=1 iommu_inclusive_mapping=1
cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1)
cc_compile_by : root
cc_compile_domain :
cc_compile_date : Mon Jan 11 14:25:59 CET 2010
xend_config_format : 4
vfarm:~# xm dmesg
0x08] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x09] address[0xfec8a000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 9, version 32, address 0xfec8a000, GSI 24-47
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
(XEN) [VT-D]dmar.c:579: Host address width 39
(XEN) [VT-D]dmar.c:588: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:374: dmaru->address = fbfff000
(XEN) [VT-D]dmar.c:326: endpoint: 0:1b.0
(XEN) [VT-D]dmar.c:588: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:374: dmaru->address = fbffe000
(XEN) [VT-D]dmar.c:331: IOAPIC: f0:1f.7
(XEN) [VT-D]dmar.c:331: IOAPIC: 0:13.0
(XEN) [VT-D]dmar.c:386: flags: INCLUDE_ALL
(XEN) [VT-D]dmar.c:592: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:438: RMRR region: base_addr ec000 end_address effff
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.0
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.1
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.2
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.7
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.0
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.1
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.2
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.7
(XEN) [VT-D]dmar.c:592: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:425: RMRR address range not in reserved memory base =
bf7dc000 end = bf7dbfff; iommu_inclusive_mapping=1 parameter may be needed.
(XEN) [VT-D]dmar.c:438: RMRR region: base_addr bf7dc000 end_address
bf7dbfff
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.0
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.1
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.2
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.7
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.0
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.1
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.2
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.7
(XEN) [VT-D]dmar.c:479: The RMRR (bf7dc000, bf7dbfff) is incorrect!
(XEN) Failed to parse ACPI DMAR. Disabling VT-d.
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
(XEN) PCI: Not using MMCONFIG.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2672.822 MHz processor.
(XEN) Initing memory sharing.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM1)
(XEN) I/O virtualisation disabled
(XEN) CPU0: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 1/2 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM1)
(XEN) CPU1: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 2/4 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM1)
(XEN) CPU2: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 3/6 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM1)
(XEN) CPU3: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 4/1 eip 8c000
(XEN) Initializing CPU#4
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#4.
(XEN) CPU4: Thermal monitoring enabled (TM1)
(XEN) CPU4: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 5/3 eip 8c000
(XEN) Initializing CPU#5
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#5.
(XEN) CPU5: Thermal monitoring enabled (TM1)
(XEN) CPU5: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 6/5 eip 8c000
(XEN) Initializing CPU#6
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 2
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#6.
(XEN) CPU6: Thermal monitoring enabled (TM1)
(XEN) CPU6: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Booting processor 7/7 eip 8c000
(XEN) Initializing CPU#7
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 8192K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 3
(XEN) HVM: ASIDs enabled.
(XEN) Intel machine check reporting enabled on CPU#7.
(XEN) CPU7: Thermal monitoring enabled (TM1)
(XEN) CPU7: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
(XEN) Total of 8 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 8 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) microcode.c:73:d32767 microcode: CPU1 resumed
(XEN) microcode.c:73:d32767 microcode: CPU6 resumed
(XEN) Brought up 8 CPUs
(XEN) microcode.c:73:d32767 microcode: CPU2 resumed
(XEN) microcode.c:73:d32767 microcode: CPU7 resumed
(XEN) microcode.c:73:d32767 microcode: CPU5 resumed
(XEN) microcode.c:73:d32767 microcode: CPU4 resumed
(XEN) microcode.c:73:d32767 microcode: CPU3 resumed
(XEN) HPET: 4 timers in total, 0 timers will be used for broadcast
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x829000
(XEN) elf_parse_binary: phdr: paddr=0x1829000 memsz=0xe6108
(XEN) elf_parse_binary: phdr: paddr=0x1910000 memsz=0x888
(XEN) elf_parse_binary: phdr: paddr=0x1911000 memsz=0x15ca0
(XEN) elf_parse_binary: phdr: paddr=0x1926ca0 memsz=0x1a9360
(XEN) elf_parse_binary: memory: 0x1000000 -> 0x1ad0000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff81926ea0
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81009000
(XEN) elf_xen_parse_note: FEATURES =
"!writable_page_tables|pae_pgdir_above_4gb"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) elf_xen_addr_calc_check: addresses:
(XEN) virt_base = 0xffffffff80000000
(XEN) elf_paddr_offset = 0x0
(XEN) virt_offset = 0xffffffff80000000
(XEN) virt_kstart = 0xffffffff81000000
(XEN) virt_kend = 0xffffffff81ad0000
(XEN) virt_entry = 0xffffffff81926ea0
(XEN) p2m_base = 0xffffffffffffffff
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1ad0000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 00000001b4000000->00000001b8000000 (114688 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff81ad0000
(XEN) Init. ramdisk: ffffffff81ad0000->ffffffff81ed7400
(XEN) Phys-Mach map: ffffffff81ed8000->ffffffff81fd8000
(XEN) Start info: ffffffff81fd8000->ffffffff81fd84b4
(XEN) Page tables: ffffffff81fd9000->ffffffff81fee000
(XEN) Boot stack: ffffffff81fee000->ffffffff81fef000
(XEN) TOTAL: ffffffff80000000->ffffffff82400000
(XEN) ENTRY ADDRESS: ffffffff81926ea0
(XEN) Dom0 has maximum 8 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81829000
(XEN) elf_load_binary: phdr 1 at 0xffffffff81829000 -> 0xffffffff8190f108
(XEN) elf_load_binary: phdr 2 at 0xffffffff81910000 -> 0xffffffff81910888
(XEN) elf_load_binary: phdr 3 at 0xffffffff81911000 -> 0xffffffff81926ca0
(XEN) elf_load_binary: phdr 4 at 0xffffffff81926ca0 -> 0xffffffff819a4000
(XEN) Scrubbing Free RAM:
.......................................................done.
(XEN) Xen trace buffers: disabled
(XEN) tmem: initialized comp=0 global-lock=0
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to switch
input to Xen)
(XEN) Freed 156kB init memory.
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=0, irq=0
(XEN) ioapic_guest_write: new_entry=00010900
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=2, irq=0
(XEN) ioapic_guest_write: new_entry=00010900
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) irq.c:1431: dom0: pirq 0 or irq 3 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 4 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 5 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 6 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 7 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 8 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 9 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 10 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 11 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 12 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 13 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 14 already mapped
(XEN) irq.c:1431: dom0: pirq 0 or irq 15 already mapped
(XEN) allocated vector for irq:16
(XEN) irq.c:1431: dom0: pirq 0 or irq 16 already mapped
(XEN) allocated vector for irq:17
(XEN) irq.c:1431: dom0: pirq 0 or irq 17 already mapped
(XEN) allocated vector for irq:18
(XEN) irq.c:1431: dom0: pirq 0 or irq 18 already mapped
(XEN) allocated vector for irq:19
(XEN) irq.c:1431: dom0: pirq 0 or irq 19 already mapped
(XEN) allocated vector for irq:20
(XEN) irq.c:1431: dom0: pirq 0 or irq 20 already mapped
(XEN) allocated vector for irq:21
(XEN) irq.c:1431: dom0: pirq 0 or irq 21 already mapped
(XEN) allocated vector for irq:22
(XEN) irq.c:1431: dom0: pirq 0 or irq 22 already mapped
(XEN) allocated vector for irq:23
(XEN) irq.c:1431: dom0: pirq 0 or irq 23 already mapped
(XEN) allocated vector for irq:24
(XEN) irq.c:1431: dom0: pirq 0 or irq 24 already mapped
(XEN) allocated vector for irq:25
(XEN) irq.c:1431: dom0: pirq 0 or irq 25 already mapped
(XEN) allocated vector for irq:26
(XEN) irq.c:1431: dom0: pirq 0 or irq 26 already mapped
(XEN) allocated vector for irq:27
(XEN) irq.c:1431: dom0: pirq 0 or irq 27 already mapped
(XEN) allocated vector for irq:28
(XEN) irq.c:1431: dom0: pirq 0 or irq 28 already mapped
(XEN) allocated vector for irq:29
(XEN) irq.c:1431: dom0: pirq 0 or irq 29 already mapped
(XEN) allocated vector for irq:30
(XEN) irq.c:1431: dom0: pirq 0 or irq 30 already mapped
(XEN) allocated vector for irq:31
(XEN) irq.c:1431: dom0: pirq 0 or irq 31 already mapped
(XEN) allocated vector for irq:32
(XEN) irq.c:1431: dom0: pirq 0 or irq 32 already mapped
(XEN) allocated vector for irq:33
(XEN) irq.c:1431: dom0: pirq 0 or irq 33 already mapped
(XEN) allocated vector for irq:34
(XEN) irq.c:1431: dom0: pirq 0 or irq 34 already mapped
(XEN) allocated vector for irq:35
(XEN) irq.c:1431: dom0: pirq 0 or irq 35 already mapped
(XEN) allocated vector for irq:36
(XEN) irq.c:1431: dom0: pirq 0 or irq 36 already mapped
(XEN) allocated vector for irq:37
(XEN) irq.c:1431: dom0: pirq 0 or irq 37 already mapped
(XEN) allocated vector for irq:38
(XEN) irq.c:1431: dom0: pirq 0 or irq 38 already mapped
(XEN) allocated vector for irq:39
(XEN) irq.c:1431: dom0: pirq 0 or irq 39 already mapped
(XEN) allocated vector for irq:40
(XEN) irq.c:1431: dom0: pirq 0 or irq 40 already mapped
(XEN) allocated vector for irq:41
(XEN) irq.c:1431: dom0: pirq 0 or irq 41 already mapped
(XEN) allocated vector for irq:42
(XEN) irq.c:1431: dom0: pirq 0 or irq 42 already mapped
(XEN) allocated vector for irq:43
(XEN) irq.c:1431: dom0: pirq 0 or irq 43 already mapped
(XEN) allocated vector for irq:44
(XEN) irq.c:1431: dom0: pirq 0 or irq 44 already mapped
(XEN) allocated vector for irq:45
(XEN) irq.c:1431: dom0: pirq 0 or irq 45 already mapped
(XEN) allocated vector for irq:46
(XEN) irq.c:1431: dom0: pirq 0 or irq 46 already mapped
(XEN) allocated vector for irq:47
(XEN) irq.c:1431: dom0: pirq 0 or irq 47 already mapped
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=0, irq=0
(XEN) ioapic_guest_write: new_entry=00000900
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) PCI add device 00:00.0
(XEN) PCI add device 00:01.0
(XEN) PCI add device 00:03.0
(XEN) PCI add device 00:07.0
(XEN) PCI add device 00:14.0
(XEN) PCI add device 00:14.1
(XEN) PCI add device 00:14.2
(XEN) PCI add device 00:14.3
(XEN) PCI add device 00:1a.0
(XEN) PCI add device 00:1a.1
(XEN) PCI add device 00:1a.2
(XEN) PCI add device 00:1a.7
(XEN) PCI add device 00:1b.0
(XEN) PCI add device 00:1c.0
(XEN) PCI add device 00:1c.2
(XEN) PCI add device 00:1c.3
(XEN) PCI add device 00:1c.4
(XEN) PCI add device 00:1d.0
(XEN) PCI add device 00:1d.1
(XEN) PCI add device 00:1d.2
(XEN) PCI add device 00:1d.7
(XEN) PCI add device 00:1e.0
(XEN) PCI add device 00:1f.0
(XEN) PCI add device 00:1f.2
(XEN) PCI add device 00:1f.3
(XEN) PCI add device 02:00.0
(XEN) PCI add device 06:00.0
(XEN) PCI add device 05:00.0
(XEN) PCI add device 04:00.0
(XEN) PCI add device 04:00.1
(XEN) Set CPU acpi_id(1) cpuid(0) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(2) cpuid(1) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(3) cpuid(2) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(4) cpuid(3) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(5) cpuid(4) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(6) cpuid(5) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(7) cpuid(6) Px State info:
(XEN) _PPC: 0
(XEN) Set CPU acpi_id(8) cpuid(7) Px State info:
(XEN) _PPC: 0
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=16, irq=16
(XEN) ioapic_guest_write: new_entry=0001a910
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=23, irq=23
(XEN) ioapic_guest_write: new_entry=0001a917
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=19, irq=19
(XEN) ioapic_guest_write: new_entry=0001a913
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=18, irq=18
(XEN) ioapic_guest_write: new_entry=0001a912
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) io_apic.c:2291:
(XEN) ioapic_guest_write: apic=0, pin=18, irq=18
(XEN) ioapic_guest_write: new_entry=0001a912
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
Han, Weidong wrote:
>
> Fantu,
>
> Can you try with the attached patch? and pls post the output of "lspci
> -v"?
>
> Regards,
> Weidong
>
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Weidong Han
> Sent: Friday, January 08, 2010 10:46 AM
> To: Pasi Kärkkäinen
> Cc: xen-devel@lists.xensource.com; Fantu
> Subject: Re: [Xen-devel] Memory mapping for PEG/PCIe Graphics Passthrough
> to <any> DomU
>
> Pasi Kärkkäinen wrote:
>
> On Thu, Jan 07, 2010 at 08:14:47AM -0800, Fantu wrote:
>
>
>
> i have grub2 also here and i have add dummy=foo before root...
>
>
>
> xm dmesg
>
> ])
>
> (XEN) [VT-D]dmar.c:548: Host address width 39
>
> (XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
>
> (XEN) [VT-D]dmar.c:374: dmaru->address = fbfff000
>
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1b.0
>
> (XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
>
> (XEN) [VT-D]dmar.c:374: dmaru->address = fbffe000
>
> (XEN) [VT-D]dmar.c:331: IOAPIC: f0:1f.7
>
> (XEN) [VT-D]dmar.c:331: IOAPIC: 0:13.0
>
> (XEN) [VT-D]dmar.c:386: flags: INCLUDE_ALL
>
> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>
> (XEN) [VT-D]dmar.c:446: RMRR region: base_addr ec000 end_address effff
>
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.0
>
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.1
>
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.2
>
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.7
>
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.0
>
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.1
>
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.2
>
> (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.7
>
> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>
> (XEN) [VT-D]dmar.c:417: RMRR error: base_addr bf7dc000 end_address
> bf7dbfff
>
> (XEN) Failed to parse ACPI DMAR. Disabling VT-d.
>
>
>
>
>
>
>
> This looks like you have a buggy BIOS, it doesn't have correct DMAR RMRR
> table..
>
>
>
> When RMRR address range is not in reserved memory (BIOS issue), can use
>
> 'iommu_inclusive_mapping=1' to work around it.
>
>
>
> So try that options for xen.gz in grub config.
>
>
>
> http://wiki.xensource.com/xenwiki/VTdHowTo
>
>
>
>
>
>
> yes, obviously the RMRR is setting incorrectly in BIOS. The base address
> shouldn't be greater than end address. "iommu_inclusive_mapping=1" cannot
> help here. You should report this issue to the vendor and ask for a
> correct BIOS.
>
> Regards,
> Weidong
>
>
>
>
>
>
> _______________________________________________
>
> Xen-devel mailing list
>
> Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
>
> http://lists.xensource.com/xen-devel
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
--
View this message in context: http://old.nabble.com/Memory-mapping-for-PEG-PCIe-Graphics-Passthrough-to-%3Cany%3E-DomU-tp22783371p27111077.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2010-01-11 14:15 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-30 13:35 Memory mapping for PEG/PCIe Graphics Passthrough to <any> DomU Tim Moore
2009-03-30 14:03 ` Alexia Benington
2010-01-05 14:43 ` Fantu
2010-01-07 15:05 ` Pasi Kärkkäinen
2010-01-07 16:14 ` Fantu
2010-01-07 21:07 ` Pasi Kärkkäinen
2010-01-08 2:45 ` Weidong Han
2010-01-08 9:18 ` Han, Weidong
2010-01-11 14:15 ` Fantu
-- strict thread matches above, loose matches on Subject: below --
2009-03-30 13:27 Tim Moore
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.