Nothing to pass through как исправить

• • Share

Link to comment

• • Share

Link to comment

• • Share

Link to comment

• • Share

1. Do you use a vbios file? Did you dump it yourself or download from TechPowerup? Wrong vbios can cause strange and weird issues.

2. Does Unraid boot on the Intel iGPU?

3. Please attach a current diagnostic. Your attached diagnostics doesn’t have any xml in it.

4. Maybe obvious question but do you have PCIe power (aka the VGA / GPU / graphics card power) connected from your PSU to the card? If yes, check that all connections are tight (unplug and replug is probably a good idea). Try different cables as well just in case.

Link to comment

• • Share

Link to comment

• • Share

1. Did you dump your vbios using the Linux command line? (i.e. it’s NOT done using GPUZ).

If so, I would trust that file as the right vbios. No point trying anything else.

But just in case, watch SpaceInvader One tutorial and double check that you have done the right step (link at end of this post) — obviously ignore the primary / secondary portion since you boot Unraid on the iGPU (which would be the «primary»).

2a. Did you connect a monitor to the onboard graphics output to be 100% sure Unraid booted on the iGPU?

It’s critical to confirm this point. You may have to go as far as making sure the onboard graphics is always connected to a monitor / a dummy HDMI/DP plug.

2b. In addition, are you booting Unraid in legacy mode (i.e. Main -> Flash -> «Permit UEFI boot mode» is NOT ticked)?

Booting Unraid in legacy mode + make sure it boots with the iGPU (or a non-passed-through GPU) are very important.

3. I made a few edits to the Q35 own vbios xml (presumably that’s the one you dumped yourself).

Just use that one and don’t bother trying anything else. In fact, your xml is fine on its own.

4. So having said the above, I can only conclude that you have a hardware issue.

• The fact the card, with the right vbios by all indications, tells you something isn’t right with the PCIe power points to either the card has gone kaput or (hopefully) a PSU / power connector issue.
  • This is consistent with your description on the other topic — that is things worked for you for a few days and then stopped working. That is how a power issue tends to manifest.
  • I would suggest trying a different cable / different PSU.
• Error 43 is generic — basically the driver fails to load. It can be because the card itself doesn’t work completely or the driver refuses to load (i.e. it detects a VM environment). It is not gonna show if the card is unstable (because the driver loads successfully).

i7-6700 + boot Unraid legacy mode + boot Unraid with the iGPU should work fine with the RTX 2060.

Something else is going on and it’s a b**** to diagnose hardware issues.

SIO tutorial

XML:

<domain type='kvm'>
  <name>Windows 10q35_5_own_vBIOS</name>
  <uuid>2c7af116-09ba-6622-ac03-5e73fefb2f3e</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>16777216</memory>
  <currentMemory unit='KiB'>16777216</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='4'/>
    <vcpupin vcpu='2' cpuset='1'/>
    <vcpupin vcpu='3' cpuset='5'/>
    <vcpupin vcpu='4' cpuset='2'/>
    <vcpupin vcpu='5' cpuset='6'/>
    <vcpupin vcpu='6' cpuset='3'/>
    <vcpupin vcpu='7' cpuset='7'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-5.0'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/2c7af116-09ba-6622-ac03-5e73fefb2f3e_VARS-pure-efi.fd</nvram>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='a0123456789b'/>
    </hyperv>
	<kvm>
      <hidden state='on'/>
    </kvm>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' dies='1' cores='4' threads='2'/>
    <cache mode='passthrough'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.185.iso'/>
      <target dev='hdb' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='qemu-xhci' ports='15'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x8'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-to-pci-bridge'>
      <model name='pcie-pci-bridge'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x9'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0xa'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0xb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/>
    </controller>
    <controller type='pci' index='6' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='6' port='0xc'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/>
    </controller>
    <controller type='pci' index='7' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='7' port='0xd'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/>
    </controller>
    <controller type='pci' index='8' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='8' port='0xe'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/>
    </controller>
    <controller type='pci' index='9' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='9' port='0xf'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:be:94:98'/>
      <source bridge='br0'/>
      <model type='virtio-net'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/user/isos/rtx2060s.dump'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x2'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x2'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x3'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x3'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
</domain>

Link to comment

• • Share

Link to comment

• • Share

i440fx (aka Intel 440FX) was released in 1996 (Pentium II). Q35 was released in 2007 (Pentium Core) so is more modern.

The key diff in my experience is that Q35 has better (native) support for PCIe devices while i440fx essentially emulates PCIe as PCI devices.

When the original guide for Unraid VM came out in the 6.0 wiki, Q35 machine type didn’t work well at all (rather unstable IME) so i440fx was the default choice for Windows VM. It was almost a «pick i440fx unless your OS requires Q35».

However, since about Q35-3.0, instability wasn’t an issue anymore but there was a bug requiring the «PCIe root port patch» to make PCIe runs at full speed (otherwise it runs at x1).

The x1 speed bug was fixed in Q35-4.0+ so basically there isn’t really a reason to always pick i440fx over Q35 anymore.

Well, there is sort of an unintended reason to use i440fx. Some graphics card may work better in a VM precisely because i440fx doesn’t have full support for PCIe. However, it’s now more of a «pick Q35 unless your hardware requires i440fx» situation.

Those who started out early with Unraid who have already picked i440fx generally don’t have an inventive changing to Q35.

However, for those starting a new template, especially those with latest graphics card (e.g. RTX), there is really no reason to pick i440fx.

In terms of what I edited in your template.

• Change vendor id to an actual value instead of none as none sometimes doesn’t work
• Add kvm hidden tag (used to help with some cards but is now generally not needed)

Edited July 31, 2020 by testdasi

Link to comment

• • Share

Link to comment