Ah, okay, good to know.  (and half is better that all the time )

 

I tried moving the driver file to the desktop of the VM to install it from there (instead of from a network drive), but it failed in the same place, the same way.

 

The Device Manager shows the correct video card name, and that it has a driver installed, but not the most recent driver.  Which means that video is working, and seems generally fine, but is not using the latest driver at this time.  i don't think this is a big deal for now, but something that probably needs fixed at some point in the future.

 

For now, I'm happy that I have a working Windows VM with passthru, so I can use it for watching stuff on my TV.

 

I still suffer some niggling issues with all my VM's, but I've got usable systems at this point, which is nice.

If a VM hangs like that, you can issue

 

XL destroy VMName

 

from the unRAID command line. (obviously replace 'VMName' with your own vm name.

 

That's the equivalent of pulling the plug on a physical machine.

 

I've found that if I need to do that on a VM with GPU passthrough and then start it up again, hald the time the video will be scrambled necessitating a full system reboot in any case.

 

So, windows 8 finally completed the installation of 8.1, and restarted, a couple of times.  Now, I have a black screen in tightVNC, and also on the monitor attached to unRAID.  So, I tried to kill the VM with this command, and got this...

 

root@media:~# xl destroy windows8
libxl: error: libxl_pci.c:990:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:14.0

 

00:14.0 is my Intel Corporation Lynx Point USB xHCI Host Controller (rev 04)

 

I guess it's time to restart unRAID again

So, windows 8 finally completed the installation of 8.1, and restarted, a couple of times.  Now, I have a black screen in tightVNC, and also on the monitor attached to unRAID.  So, I tried to kill the VM with this command, and got this...

 

root@media:~# xl destroy windows8
libxl: error: libxl_pci.c:990:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:00:14.0

 

00:14.0 is my Intel Corporation Lynx Point USB xHCI Host Controller (rev 04)

 

Are you attempting to passthrough a motherboard USB Controller to Windows?

 

While others have had luck passing through a single onboard controller, I was not able to pass one through to 8.1 without bugs. 

 

My Onboard USB Controllers

00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)

 

I COULD passthrough all 3 controllers, but then unraid was not left with a USB port from which to boot (tested after I installed a PCI USB controller).

 

I am using a $10 PCI card ( 4 external and 1 internal)

Rosewill NEC 4+1 Port USB 2.0 PCI Card, Black/Silver RC-101

http://www.amazon.com/gp/product/B00BAU2QZQ/ref=oh_details_o06_s00_i01?ie=UTF8&psc=1

PCI card (and yes, it takes up 3 addresses)

05:00.0 USB controller: NEC Corporation OHCI USB Controller (rev 43)
05:00.1 USB controller: NEC Corporation OHCI USB Controller (rev 43)
05:00.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 04)

 

I have NO problems with restarting the VM and loosing the USB in Windows.

 

One of the cases front panel connectors is hooked up to the single internal slot on my NEC controller, the other front panel connector is hooked up to the header shared with unRaid, for unRaid access - I am using 2 of these: IDC 5 Male (single row) to USB A Male (Used to connect devices designed to plug into USB motherboard header pins to an external USB 2.0 connector)

http://www.amazon.com/gp/product/B000V6WD8A/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1

I'm still a bit unclear on what I should be passing thru to Windows, a USB controller, or a PCI controller.  I had originally had successfully passed thru a Bluetooth USB dongle, which windows recognized and installed a driver for, which I then successfully connected a keyboard to.  however, when I finished the upgrade to 8.1 (which I had to do in tightVNC, with no passthru active to get it to complete), this device is no longer properly recognized by windows.  Other than this one device, I have it all working again, with the following settings for passthru...

 

syslinux.cfg...

  append /xen --- /bzimage xen-pciback.hide=(00:14.0)(01:00.0)(01:00.1)(09:00.0)(00:1b.0) --- /bzroot

 

windows8.cfg...

usb = '1'

usbdevice = ['tablet','host:0a12:0001','host:045e:0745','host:174c:5106','host:045e:00db','host:147a:e03e']

pci = [ '00:14.0','01:00.0','01:00.1','09:00.0','00:1b.0' ]

 

I'm calling this good enough, for now.  I may try finding the driver for the BT dongle, to see if installing it gets the device recognized, but I have other keyboards I can connect, so it's not such a big deal at this point.

 

With the eminent move to KVM as the host (instead of XEN), I suspect I'll have to redo all this soon anyway

 

Thanks again for all the help.

You can passthrough

1 - USB Device

2 - USB Controller embedded into the motherboard

3 - PCI Device (filled with a USB Controller)

 

1 - seems to work FINE for simple devices (wired keyboard, wired mouse).  Works but buggy for Flash drives, Wireless controllers, etc - By buggy I mean may require full system restarts, may work today but not tomorrow.

2 - I have had no luck with this

3 - This works the best, no bugs, runs smoothly, USB devices work just as if baremetal OS install.

With the eminent move to KVM as the host (instead of XEN), I suspect I'll have to redo all this soon anyway

 

I sure hope the work transfers... it took me WEEKS to figure out the bits and pieces... to have a stable running system with the required passthroughs...