From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Bauer Subject: Re: [VT-D]iommu.c:775: iommu_page_fault: iommu->reg =ffff828bfff57000 Date: Tue, 28 Oct 2008 20:41:59 +0100 Message-ID: <49076B07.2010100@cubewerk.de> References: <4906E4BE.7040102@cubewerk.de> <409D32C55C48D34DB5E31C8AB29EB15B071C6AF6@FTLPEXCH05.citrite.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------050900010209000900070708" Return-path: In-Reply-To: <409D32C55C48D34DB5E31C8AB29EB15B071C6AF6@FTLPEXCH05.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --------------050900010209000900070708 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Ross Philipson schrieb: > So the trace below is showing a failure during Xen boot and later you > have trouble passing through a graphics card to an HVM? Do you get > subsequent errors when starting the HVM? What is device 00:2.0 that is > causing the fault below? Reason 5 indicates a DMA write to a page where > the IOMMU PTE W bit is clear to disallow DMA writes. Hi Ross, the error after trying to start the hvm guest by xm create win2k is: VmError: fail to assign device(1:0.0): maybe it has already been assigned to other domain, or maybe it doesn't exist. [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=5 [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) XendDomainInfo.destroyDomain(5) [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) No device model [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) Releasing devices [2008-10-25 19:59:30 2460] ERROR (__init__:1072) Domain construction failed Traceback (most recent call last): File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 92, in create vm.start() File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 424, in start XendTask.log_progress(0, 30, self._constructDomain) File "//usr/lib64/python/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds) File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 2103, in _constructDomain raise VmError("fail to assign device(%x:%x.%x): maybe it has" VmError: fail to assign device(1:0.0): maybe it has already been assigned to other domain, or maybe it doesn't exist. I also noticed that lspci did not show the graphiccard anymore after i use the boot option iommu in combination with vtd. Might be caused by that initial error. I have to admit that lspci did not show device 00:2.0. that looks strange to me. please see attached the output of lspci -vv Thanks in advance -- stefan --------------050900010209000900070708 Content-Type: text/plain; name="lspci" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="lspci" 00:00.0 Host bridge: Intel Corporation Unknown device 29b0 (rev 02) Subsystem: Lenovo Unknown device 3037 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- Capabilities: [88] Subsystem: Lenovo Unknown device 3037 Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Address: 00000000 Data: 0000 Capabilities: [a0] Express Root Port (Slot+) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s <64ns, L1 <1us Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported- Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 2 Link: Latency L0s <256ns, L1 <4us Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch- Link: Speed 2.5Gb/s, Width x16 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug- Surpise- Slot: Number 4096, PowerLimit 75.000000 Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- Slot: AttnInd Off, PwrInd On, Power- Root: Correctable- Non-Fatal- Fatal- PME- 00:03.0 Communication controller: Intel Corporation Unknown device 29b4 (rev 02) Subsystem: Lenovo Unknown device 3037 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- Capabilities: [50] Subsystem: Lenovo Unknown device 3037 00:1f.0 ISA bridge: Intel Corporation Unknown device 2914 (rev 02) Subsystem: Lenovo Unknown device 3037 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Region 1: I/O ports at Region 2: I/O ports at Region 3: I/O ports at Region 4: I/O ports at 1c40 [size=16] Region 5: I/O ports at 1c30 [size=16] Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [b0] #13 [0306] 00:1f.3 SMBus: Intel Corporation Unknown device 2930 (rev 02) Subsystem: Lenovo Unknown device 3037 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR-