Opened 13 years ago
Closed 12 years ago
#10300 closed defect (fixed)
Intel HD2000 VT-d IOMMU fails boot of Windows 7 (VB hang)
Reported by: | mhakali | Owned by: | |
---|---|---|---|
Component: | VMM | Version: | VirtualBox 4.1.8 |
Keywords: | iommu vt-d intel graphics | Cc: | |
Guest type: | Windows | Host type: | Linux |
Description
Trying to import two devices via VT-d / IOMMU.
VBoxManage modifyvm "Windows 7" --pciattach 03:00.0@01:05.0 VBoxManage modifyvm "Windows 7" --pciattach 00:02.0@01:06.0
Kernel: 3.2.6 Ubuntu branch with Tresor AES patches. IOMMU and DMAR enabled and verified (working USB3.0 device import)
03:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) (prog-if 30 [XHCI]) Subsystem: Intel Corporation Device 2008 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 18 Region 0: Memory at fb900000 (64-bit, non-prefetchable) [size=8K] Capabilities: <access denied> Kernel driver in use: pci-stub Kernel modules: xhci-hcd
00:02.0 Display controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Intel Corporation Device 2008 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 16 Region 0: Memory at fb400000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at c0000000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at f000 [size=64] Capabilities: <access denied> Kernel driver in use: pci-stub Kernel modules: i915
The host is running on an NVidia card. Neither i915 nor xhci-hcd is loaded as kernel modules.
The USB3 succeeds import. The Intel GFX creates a crash on Windows 7 boot.
Have not found any clear instructions to how to assign guest device PCI-ID's, so just took two examples as found in the advanced settings documents.
Tips and/or workarounds appreciated.
Attaching virtualbox logs.
Attachments (2)
Change History (3)
by , 13 years ago
Attachment: | VBox.log.gz added |
---|
by , 13 years ago
comment:1 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if still relevant with VBox 4.2.8.
VBox log file