reluctantflux

My diagram is wrong. Every single USB port on my board uses the 00:14.0 Intel controller besides the 2 ASMedia ports. Ugh. Guess I'm getting a USB controller card.

Ok, so I think this might be the layout for our ASRock Xtreme 6 motherboards. Each internal USB 2.0 mainboard header has its own controller (00:1a.0 and 00:1d.0). The onboard port, and 4 left USB 3.0 ports are the Intel 3.0 USB controller (00:14.0). And the right two, and then 2 internal 20-pin USB 3.0 headers are the ASMedia controller (0c:00.0). Only reason I think the internal 20-pin ports work off the ASMedia instead of Intel is because "6 ports Asmedia and 5 ports Intel" makes more sense than "2 ports Asmedia and 9 ports Intel". I'll confirm this once some parts I just ordered arrive.

root@Tower:~# lspci | grep USB 00:14.0 USB controller: Intel Corporation Device 8cb1 00:1a.0 USB controller: Intel Corporation Device 8cad 00:1d.0 USB controller: Intel Corporation Device 8ca6 0c:00.0 USB controller: ASMedia Technology Inc. Device 1142 So you are using the intel controller. Crud, I was really hoping to avoid that. Aren't the four rear USB ports and the internal port all on that controller? That's a lot of ports for me to forward through when I only need one of them for my USB active extender, and that only leaves me with 2 for other machines. Maybe I did my testing wrong.

So you're passing through the ASMedia controller, and not the intel one, correct? Can you show me your "Universal Serial Bus Controllers" section of Device Manager? I'm curious on if you have different host controllers showing than me. Also, I read this could be an issue with the Bios, having the USB 3.0 supporting legacy devices.

Only itself in the group. ### Group 28 ### 0c:00.0 USB controller: ASMedia Technology Inc. Device 1142 Maybe I just need to try harder with the drivers, but I did try a bunch of different ones the last time I tried.

htpcnewbie and I have the same motherboard, and I came across having the same issues as they were. It is not a Win7 issue, as the same thing happens in Win8. Basically, the controller shows up in device manager, but it has a yellow exclamation because it has failed to start. We have the ASRock Xtreme6 LGA1150 motherboard. Here's a few commands with their outputs: root@Tower:~# lspci | grep ASMedia 05:00.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:01.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:03.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:05.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:07.0 PCI bridge: ASMedia Technology Inc. Device 1184 08:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0a:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0c:00.0 USB controller: ASMedia Technology Inc. Device 1142 root@Tower:~# lsusb Bus 002 Device 002: ID 8087:8001 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 007: ID 04f2:0841 Chicony Electronics Co., Ltd HP Multimedia Keyboard Bus 005 Device 016: ID 1532:0101 Razer USA, Ltd Copperhead Mouse Bus 005 Device 008: ID 046d:0a1f Logitech, Inc. G930 Bus 005 Device 006: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Bus 005 Device 013: ID 0cf3:3002 Atheros Communications, Inc. AR3011 Bluetooth Bus 005 Device 011: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 005 Device 005: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Bus 005 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub Bus 005 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 005 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8009 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 010: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 004: ID 045e:006d Microsoft Corp. eHome Remote Control Keyboard keys Bus 003 Device 003: ID 174c:2074 ASMedia Technology Inc. Bus 003 Device 002: ID 0781:5580 SanDisk Corp. SDCZ80 Flash Drive Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@Tower:~# readlink /sys/bus/usb/devices/usb5 ../../../devices/pci0000:00/0000:00:1c.6/0000:0c:00.0/usb5 root@Tower:~#

I had the same problem the Microsoft All-in-One keyboard. I ended up returning it for a Logitech and haven't had any issues since. I believe the issue stems from the device going into sleep mode after a short period (10 seconds?) of inactivity to save power. I got frustrated and just returned the unit since it was a new purchase. Perhaps you could look into some of the nitty gritty driver details on the device going to sleep or passing through the USB controller, instead of individual USB devices.

Best diagrams explaining the difference.

I checked out the site. I don't really see how it's relevant to an Unraid setup, as it only backs up VM's from Hyper-V or VMware.

Thanks! I ended up manually switching it to 4096MB in the XML, and then changing the main page drop down to 4096, and that allowed me to change it via the main page to whatever I wanted again. The 512 default for unrecognized manual entries makes sense, but I just thought it was weird that it couldn't change it then. Thanks for the great program!

Here's an update after testing, so that people know what to expect with the Tripp Lite 4-port USB 2.0 over cat5. 1) The local device is a usb to gigabit nic. The remote side is a usb server hub. There is a program that starts at logon that makes the connection to the remote hub. This prevents you from being able to login with devices on the extended hub. Why they didn't design it as a service instead of an application is beyond me. This won't be an issue if you have auto-logon. 2) It did not work with my Logitech G930 gaming headset. I thought this might be an issue as their specs did explain that it does not work with isochronous data transfers (items such as cameras and speakers sometimes use this). As I couldn't find any mention one way or another on Logitech's website, I figured I'd give it a shot. Once I plugged in the wireless headset adapter usb, it broke the mouse and keyboard from working. 3) When the headset wasn't plugged in, and I was logged on, the keyboard and mouse worked flawlessly for the time that I used it. At that point, though, I didn't really need a USB 2.0 extender, which made the purchase unnecessarily expensive ($150). I'm returning this cat5 extender, going with some active usb extenders, and running them through my house this weekend. I plan on putting a powered hub on the other end.

So of course I decide to keep messing around after I've already started the Amazon return process and purchased new Active USB extenders. Turns out, it was the controller issue I originally thought it was. To get around the vague "error" messages I was getting when trying to start my VM after changes, I started my vm using virsh create on CLI. This would give me a more detailed error on what was failing, but unfortunately, this destroys the xml file, so it was a good thing I kept a backup. Long story short, adding the <controller> parts, recommended in Jonp's KVM passthrough pointers post, allowed the USB over cat5 to start properly within Windows. As an aside, I had to remove all of the <address> portions, otherwise there were conflicts and the XML wouldn't save. The USB extender software that I needed to install on my Windows VM picked up my Razer Copperhead mouse, and HP keyboard right away. I'm curious to see performance with my Logitech G930 headset tonight when I get home. The USB over Cat5 extender that I'm using is the Tripp Lite 4-port USB 2.0 over Cat5. It remains to be seen if this is reliable. The reason I wanted to go this route instead of Active USB extenders is I reaaaally didn't want to run new USB cabling through my house, and if I got this to work, since it's a single device on the host side, anything I plug in on the remote side will show up without having to reboot the vm. I need to test this further, but so far this appears to be true. If anyone has any questions, let me know. Here's my working XML. Going to be adding a new vid card tonight for GPU passthrough. <domain type='kvm' id='24'> <name>Gaming</name> <uuid>50c291fb-b433-a522-fae8-fb576a964cc7</uuid> <memory unit='KiB'>17301504</memory> <currentMemory unit='KiB'>4000000</currentMemory> <vcpu placement='static'>4</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> <boot dev='cdrom'/> <bootmenu enable='yes' timeout='3000'/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode='host-passthrough'> <topology sockets='2' cores='2' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='yes'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/disk/by-id/ata-Samsung_SSD_840_PRO_Series_S1ATNSAF906981Z'/> <backingStore/> <target dev='hdc' bus='virtio'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </disk> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb0'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb0'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb0'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:15:fb:47'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/2'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='cirrus' vram='9216' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0b95'/> <product id='0x1780'/> <address bus='3' device='6'/> </source> <alias name='hostdev0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </memballoon> </devices> </domain>

Bah! Then I have to run new cables from my basement, up my stack to the attic, and then back down to my office. I'll do it if I have to, though. How long is your run? Have you had success with putting a regular hub on the other end?

I tried adding the following for preparation of adding a GPU passthrough on this same VM, thinking maybe theses USB controllers would help and the XML saves successfully, but when I go to start the VM, it simply says "error" <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb0'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb0'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb0'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x2'/> </controller>

I'm having an issue with USB Passthrough of a Tripp Lite USB 2.0 over Cat5. Here's the rundown: 1) The device is basically a USB NIC that talks over an ethernet cable to a usb hub on the other side of the network cable. 2) The device shows up in an ssh session with lsusb resulting in: Bus 003 Device 013: ID 0b95:1780 ASIX Electronics Corp. AX88178 3) The device works fine with my Win 8.1 Pro Surface tablet. 4) I can see the device with the same driver in my Win 8.1 VM, except the device cannot start (Code 10). 5) Even though I can see it using an lsusb call, in VMman, the device shows up as Device: Blank, Identification: Blank, Driver: none, Vendor: Unknown, Product: Unknown. 6) I've done all the basic troubleshooting (restarting host, restarting VM, reinstalling drivers, trying different drivers, etc.) I *think* it has to do with the USB controller in my XML settings.

Not sure what's up with this, but I can't change the memory on a certain VM. Also, even though the XML has it set for 16GB, VMman says only 512MB is allocated. When I start the VM, it boots with the 16GB and shows the right amount in VMman. <domain type='kvm'> <name>Gaming</name> <uuid>50c291fb-b433-a522-fae8-fb576a964cc7</uuid> <memory unit='KiB'>19531250</memory> <currentMemory unit='KiB'>19531250</currentMemory> <vcpu placement='static'>4</vcpu> <os> <type arch='x86_64' machine='pc-i440fx-2.1'>hvm</type> <boot dev='hd'/> <boot dev='cdrom'/> <bootmenu enable='yes' timeout='3000'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='yes'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/cache/iso/Win81Pro.iso'/> <target dev='hdc' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/cache/iso/virtio-win-0.1-81.iso'/> <target dev='hdd' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='1' target='0' unit='1'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/disk/by-id/ata-Samsung_SSD_840_PRO_Series_S1ATNSAF906981Z'/> <target dev='hdc' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </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> <interface type='bridge'> <mac address='52:54:00:15:fb:47'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0b95'/> <product id='0x1780'/> </source> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </memballoon> </devices> </domain> I can change the RAM on my other VMs without issue. I can change it manually, but not from the web interface. Even changed it to 4GB manually then tried to change it, but the screen refreshes and just stays at 512.

Jonp. Thanks for the info! Do you know if there's a way to set it back to Virtio from Sata? My HTPC is a raw qcow2 image on Sata bus. I've read that you can install the virtio drivers, shutdown the vm, change the bus, and then boot back up and it'll be fine, but I'd like a second opinion before I started messing with it.

Yes to both, as well. I was able to restore from my original VDI file that I converted to qcow2, so it wasn't a huge headache to get back to regular. I love VM's. So easy to backup the hard drive file and revert back if necessary.

For the performance of the SYBA-SI-PEX40071, I haven't noticed any problems with it all, but I also have not run any sort of performance testing on it. I guess those SYBA SY-PEX40039 cards will work. At first I didn't think so since it's a PCIe 2.0 card, but the reviews say people are using them in the x1 slots. Having an x8 card running at x2 is definitely going to be a performance hit. If the card was able to run at full performance at x2 instead of x8, then they surely would have advertised as such. As for an x8 running at x2 compared to the Syba x2 card, there's no way to tell the performance difference without running tests. That PCIe 2.0 slot is x16, though, so why wouldn't you run the x8 card at x8?

SYBA SI-PEX40071 8 Internal SATA III Ports PCI-Express Card Works great for me and works right out of the box. Go here for a hardware compatibility list. http://lime-technology.com/wiki/index.php/Hardware_Compatibility#PCI_SATA_Controllers I would not go with the card you're asking about. First, your case would need a SAS board that all of your SATA drives would plug into. Second, that IBM card requires a PCI Express 3.0 x8 slot, which you only have two slots for. If you go with the Syba that I recommended, you can put him in the PCI express 2.0 slot, leaving your two 3.0 slots for video cards. The IBM card is probably a bit more expensive as it is meant for enterprise servers and can handle raid, which you don't need. Also, the raid controller would increase boot time. Let me know if you have any more questions.

Just a quick note, I don't think anyone else will have this problem, but if you're going to use all three PCIe slots, you need to provide a 4 pin molex power to the board side furthest from the CPU. Since I'm using a server case, this pretty much butted right up to the case wall. When you're installing the board, and this port is close to the wall that you won't be able to plug something in later, make sure to get a molex extension cable and plug it in prior to install. I ended up having to cut a molex end in half to get it to fit between the plug and the case wall, and I still had to unscrew the motherboard to give me the wiggle room to do that. Why they have it angled, and not just pointed straight up is beyond me, but just make sure to check this before you install the board.

I just got the ASRock Z97 Extreme6 and I love it. Easy bios, I'm rocking 32GB of RAM and it picked up the speed and timings perfectly. Hardware passthrough is working and has an onboard usb port, so you can keep your unraid usb stick on the inside of the computer. I have two graphic cards plugged into the two PCIe 3.0 ports, and then a SYBA SI-PEX40071 8 Internal SATA III Ports PCI-Express Card for the PCIe 2.0 slot, giving me a total of 18 Sata III ports. Hopefully someone will crack the iGPU issue, but even if not, this board will be able to cover everything I want to do. The sale on the board is also a great deal, don't let it pass by if you're looking for a new one.

I had ATI drivers installed, and then switched which card was being passed through and that's when the disk activity went crazy. Once I got the Nvidia drivers installed (which was painfully slow), it resumed to regular speed. There were some issues with the Nvidia card, and I reverted back to the ATI, and it worked fine until a reboot, and now my whole VM is hosed. Trying a system restore. I had taken a snapshot, but for some reason, he decided to delete himself.... *sad trombone noise* Might have to just rebuild this guy from scratch. He was from a Virtualbox build anyways. Might be good to do fresh all through KVM.

Was simply the drivers. Wow that was brutal.