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


    Cisnet
    • 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




    User Feedback

    Recommended Comments

    Post your diagnostics and XML file.

    A screenshot of your VM settings would be helpful too.

    Edited by bonienl
    Link to comment

    Hi Cisnet and thank you for reporting your issue.  I just tried to recreate it and I'm not experiencing this problem.  Here were the steps I took:

     

    • Create a new Windows 10 VM with SeaBIOS
    • Did not assign any GPUs or other PCI devices to it
    • Saved the VM
    • Edited the VM
    • Selected a GPU instead of VNC for graphics
    • Clicked "Update"
    • Changes were applied and no error message was received.

     

    Can you recreate the issue by creating a new VM?  If not, this may be something specific in the XML that was specific to a prior release.

    Link to comment

    Another test to try.  With the VM stopped, click Edit, then click apply without changing anything.  Now click Edit again, then try to add your GPU and see if the Update button works.

    Link to comment

    Thanks for the response. I've tried editing then applying without any changes which worked; then I tried adding my GPU but the update button still gave the error on both my VMs. Ive since then tried re-creating a new VM with the same settings this time with the OVMF virtualization which worked. I could change the settings & update but it wouldn't boot.

     

    I created another VM using Sealbios with the same settings. I can now boot & update. Seems like it was a issue with the old code & re-creating the VM worked.

     

    That being said I am still getting this issue - this time with the USB controller.

    I can select USB 2.0, but if I select any of the USB 3.0 options I get the same error.

     

     

     

     

    1559832182_Screenshotfrom2018-11-1400-28-55.png.b91268157d57f5b13777404bc3428816.png

     

    tower-diagnostics-20181114-0029.zip

    Edited by Cisnet
    Link to comment

    Just wanted to bump this & say I tried disabling ACS along with resetting my motherboard bios. No luck still cannot select USB 3.0.

    • Like 1
    Link to comment

    I experienced this same error on 6.6.1. I had to recreate the VM by first creating a new Windows 10 VM and then copying over the old XML and relinking the image. The new VM with the same XML did not yield the error which I did not understand. 2 VMs with the same XML. One would start, and the other would give the error below.

     

    This is a detail of my post from Sept. 29th. --> 

     

     

    Link to comment
    On 11/25/2018 at 8:12 PM, Cisnet said:

    Unraid has become unusable at this point. Downgraded to v5.

    Uh oh, what has become unusable?  I'm assuming you meant Unraid 6.5, not Unraid 5.  I will attempt to recreate this issue this week in the lab.  If I can, we should be able to fix.

    Link to comment

    I'm experiencing the same issue.

     

    Unraid 6.6.6 - Changing the USB wrecks the XML file and fudge's you trying to simply change something and reload your VM.

    Frustrating for a paid for product.

    Link to comment

    I know this is old, but I ran in to a similar problem today. I found a way to solve this so I figured I'd add it here for the next person. 

    In my case I had been adding some usb devices manually, and thats what first caused the issue. but I see similar malformed xml in the configuration above. 

    Try removing any usb configs with 2 address tags in them. then save and make your changes.

    <hostdev mode='subsystem' type='usb' managed='yes'>
    	<source>
    		<address bus='5' device='3'/>
    	</source>
    	<address type='usb' bus='0' port='2'/>
    </hostdev>

     


    Basically any usb config that contains the <address> tag with a bus and device id shouldn't also have an address tag with type,bus, port. Usually you add the bus and device id when trying to pass through usb devices with matching vendor and product ids. But you should still remove the second address tag.  I found it was easiest to remove all the offending usb configs. Save, and then reconfigure things correctly. 

    Edited by djrico20one1
    Typos, Clean up
    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.