hrfraz

Members
  • Posts

    4
  • Joined

  • Last visited

hrfraz's Achievements

Noob

Noob (1/14)

0

Reputation

  1. That would be a total bummer if so.. In the BIOS, I can select Integrated, PCIe, or PCI as a video device. The system will post and boot successfully to unraid using any of the 3 cards- a GeForce 210, ATI Mach64, or the i7's integrated... Does this shed any more light or clues to the situation? If the PCI card initializes through the bios successfully, does that mean that it still needs to be UEFI for vfio to send it a reset and map it to the VM? I also had diffuculty with other PCI devices until I added them to the boot parameters making the vfio-pci driver attach. (append vfio-pci.ids=blah blah) Another clue might be that it isn't assigned a subsystem (or doesn't have one?)... does that point to a non-uefi problem as well or a different issue? 04:01.0 USB controller: NEC Corporation OHCI USB Controller (rev 41) Subsystem: NEC Corporation USB Controller Kernel driver in use: vfio-pci 04:01.1 USB controller: NEC Corporation OHCI USB Controller (rev 41) Subsystem: NEC Corporation USB Controller Kernel driver in use: vfio-pci 04:01.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 02) Subsystem: HaSoTec GmbH uPD72010x USB 2.0 Controller Kernel driver in use: vfio-pci 04:02.0 Ethernet controller: Lite-On Communications Inc LNE100TX [Linksys EtherFast 10/100] (rev 25) Subsystem: Lite-On Communications Inc LNE100TX [ver 2.0] Kernel driver in use: vfio-pci 04:04.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mach64 GTB [3D Rage II+ DVD] (rev 9a) Kernel driver in use: vfio-pci Sorry, I'm still new to all this unraid stuff. (My main Xeon unraid rig works perfectly but then again I'm not trying to do all this PCI weirdness with it!) Also, here are my IOMMU groups, if it may help: IOMMU group 0 [8086:0150] 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) IOMMU group 1 [8086:0151] 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) IOMMU group 2 [8086:0162] 00:02.0 Display controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) IOMMU group 3 [8086:1e31] 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) IOMMU group 4 [8086:1e3a] 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) IOMMU group 5 [8086:1502] 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) IOMMU group 6 [8086:1e2d] 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) IOMMU group 7 [8086:1e10] 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) IOMMU group 8 [8086:1e18] 00:1c.4 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 (rev c4) IOMMU group 9 [8086:1e26] 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) IOMMU group 10 [8086:244e] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4) [1033:0035] 04:01.0 USB controller: NEC Corporation OHCI USB Controller (rev 41) [1033:0035] 04:01.1 USB controller: NEC Corporation OHCI USB Controller (rev 41) [1033:00e0] 04:01.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 02) [11ad:c115] 04:02.0 Ethernet controller: Lite-On Communications Inc LNE100TX [Linksys EtherFast 10/100] (rev 25) [1002:4755] 04:04.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mach64 GTB [3D Rage II+ DVD] (rev 9a) IOMMU group 11 [8086:1e47] 00:1f.0 ISA bridge: Intel Corporation Q77 Express Chipset LPC Controller (rev 04) [8086:1e00] 00:1f.2 IDE interface: Intel Corporation 7 Series/C210 Series Chipset Family 4-port SATA Controller [IDE mode] (rev 04) [8086:1e22] 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04) [8086:1e08] 00:1f.5 IDE interface: Intel Corporation 7 Series/C210 Series Chipset Family 2-port SATA Controller [IDE mode] (rev 04) IOMMU group 12 [10de:0a65] 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) [10de:0be3] 01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1) IOMMU group 13 [8086:150c] 03:00.0 Ethernet controller: Intel Corporation 82583V Gigabit Network Connection
  2. Hi Everyone! I've got a bit of an odd configuration.. I have this weird industrial motherboard (ASRock IMB-770) that is highly configurable (for POS systems or something.) It's got the intel Q77 Chipset and an i7-3770S, and most notably, 4 plain ol' 33MHz PCI slots. My goal with this particular machine is to do retro gaming and run older software and pass through an older PCI GPU, sound card, and usb controller so that there is full windows 98/2000/XP compatibility. Unfortunately, I am having issues getting the video card to attach. I've tried all 4 pci slots, iommu and VT is enabled, allow_unsafe_interrupts is set to 1, etc. All QEMU returns is 'internal error: qemu unexpectedly closed the monitor' 3236: error : qemuMonitorIORead:586 : Unable to read from monitor: Connection reset by peer 3236: error : qemuProcessReportLogError:1807 : internal error: qemu unexpectedly closed the monitor The PCI bridge and video card are in their own IOMMU group, do I need to somehow pass through the PCI bridge as well? IOMMU group 10 [8086:244e] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4) [1002:4755] 03:04.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mach64 GTB [3D Rage II+ DVD] (rev 9a) Do any of you more experienced vfio vets have any suggestions? I hope we can make this thing work. Thanks!!
  3. Yah, I'm just saying that if someone has this issue, disabling the boot logo with that line in msdos.sys will fix that specific issue.
  4. Hi All, I found a way around having to do the step-by-step confirmation in order to boot. Disable the boot splash by putting logo=0 under the options section in msdos.sys! [Options]logo=0BootMulti=1..BLAH... To unlock msdos.sys for editing, edit, and re-lock: