Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

New View the Bug / Feature Tracker

[6.6.5] internal error: PCI host devices must use 'pci' address type

By Cisnet

· 7792 views
  • Minor

EDIT: After re-creating the VM I was able to update it sucessfully & add a GPU; however, now I can no longer change the USB controller to USB 3.0 without receiving the same error when I hit the update button. USB 2.0 works.

 

 

 

When I add my GTX 1070s to any VM's & press the update button I receive the error message below:

 

image.png.fb1f508e8e56d04ee16f060ab5a64f03.png

 

If I update the VM through the XML view it works fine. This machine has been running unraid since v4 with no issues until the latest few released this started happening. I cannot currently start one of my VMs due to thi. Once of my other VMs I have not touched works & starts up fine. I just cannot update usb devices.

 

This happens on both my VMs with two different GTX 1070s.

 

I checked the system log only to see this:

  

Nov 10 12:27:22 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000
Nov 10 12:27:22 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout
Nov 10 12:27:22 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2
Nov 10 12:27:22 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 10 12:27:22 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000
Nov 10 12:27:22 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout
Nov 10 12:27:24 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2
Nov 10 12:27:24 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 10 12:27:24 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000
Nov 10 12:27:24 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout
Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: AER: Multiple Corrected error received: 0000:00:03.2
Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000040/00002000
Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: [ 6] Bad TLP
Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: AER: Multiple Corrected error received: 0000:00:03.2
Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000040/00002000
Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: [ 6] Bad TLP
Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2
Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000
Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout
Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2
Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000
Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout
Nov 10 12:27:41 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2
Nov 10 12:27:41 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 10 12:27:41 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000
Nov 10 12:27:41 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout
Nov 10 12:27:42 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2
Nov 10 12:27:42 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 10 12:27:42 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000
Nov 10 12:27:42 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout
Nov 10 12:27:44 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2
Nov 10 12:27:44 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 10 12:27:44 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000
Nov 10 12:27:44 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout
Nov 10 12:29:15 Tower kernel: usb 3-10.2: reset full-speed USB device number 8 using xhci_hcd
Nov 10 12:29:15 Tower kernel: usb 3-10.2: reset full-speed USB device number 8 using xhci_hcd
Nov 10 12:29:16 Tower kernel: usb 3-10.2: reset full-speed USB device number 8 using xhci_hcd
Nov 10 12:30:18 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2
Nov 10 12:30:18 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 10 12:30:18 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000
Nov 10 12:30:18 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout
Nov 10 12:30:20 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2
Nov 10 12:30:20 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 10 12:30:20 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000
Nov 10 12:30:20 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout
Nov 10 12:31:10 Tower kernel: usb 3-10.2: reset full-speed USB device number 8 using xhci_hcd
Nov 10 12:31:10 Tower kernel: usb 3-10.2: reset full-speed USB device number 8 using xhci_hcd
Nov 10 12:31:10 Tower kernel: usb 3-10.2: reset full-speed USB device number 8 using xhci_hcd

 

 

Here is my XML File: 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>vm1</name>
  <uuid>5c2de3e6-bc1b-d47d-db69-df51fc9c3ab4</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'>6</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='3'/>
    <vcpupin vcpu='1' cpuset='9'/>
    <vcpupin vcpu='2' cpuset='4'/>
    <vcpupin vcpu='3' cpuset='10'/>
    <vcpupin vcpu='4' cpuset='5'/>
    <vcpupin vcpu='5' cpuset='11'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='3' threads='2'/>
  </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='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/vdisks/vm1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/Windows.iso'/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.141.iso'/>
      <target dev='hdb' bus='ide'/>
      <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='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:2e:30:0b'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' 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='tablet' bus='usb'>
      <address type='usb' bus='0' port='5'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <address bus='5' device='3'/>
      </source>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x045e'/>
        <product id='0x0719'/>
      </source>
      <address type='usb' bus='0' port='1'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x04d8'/>
        <product id='0x00df'/>
      </source>
      <address type='usb' bus='0' port='3'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x248a'/>
        <product id='0x8367'/>
      </source>
      <address type='usb' bus='0' port='4'/>
    </hostdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

 

Here is my VM config:

1690488494_Screenshotfrom2018-11-1103-28-40.thumb.png.8cb7ded9b62084564556890373b67ca0.png

 

 

More VM settings:

image.thumb.png.7db7ceb7cf366ed3292b37f5e91a6553.png

    • Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.