[RESOLVED] Windows 10 VM Issues


comfox

Recommended Posts

Hello All,

 

I am trying hard to get in to this world of VM's on unRAID but I am having a hell of time.  So far I have spent the better part of 8 hours and near a thousand dollars and still don't have a working Windows 10 image that I can use.

 

I am trying to create a Windows 10 VM on top of unRAID that has all the functionality I am used to having including GPU passthrough, USB harddrives and sticks working, sound and a general stability that would be normally expected.

 

So far I have sound and GPU passthrough but that is.  I am working on the USB part now and hopefully will tack general stability last.

 

How do I go about getting USB to work?  I have USB sticks that I can't get to work in windows.  I have a Thermaltake external HDD bay that I can't get to work.

 

Even when I assign some of these items in the GUI they aren't loaded in Windows.

 

I have followed these threads and have had no luck.

 

https://lime-technology.com/forum/index.php?topic=36768.0

http://lime-technology.com/forum/index.php?topic=41922.0

http://lime-technology.com/wiki/index.php/UnRAID_Manual_6

Link to comment

Great.  How did you get them to work?

 

I followed the first link you posted.....  ;D

 

So until YOU tell US what YOU'RE doing, we can't tell you where you're going wrong...

 

Honestly if you want help, then give us more information.  What worked on my machine, won't necessarily be the same on yours..

 

Why don't you post what steps you're taking, what outputs you're getting, what error messages you're seeing..

Link to comment

Well right now I have completely blown away the unRAID configuration and am starting from scratch due to my VM being stuck in a state where it was laggy as all heck and basically unsuable.  This will be the fourth time today I am starting from scratch so I am a bit frustrated to say the least.

 

I am currently creating a slipsteamed Windows 10 ISO with build 1511 in it because installing a fresh ISO and upgrading is causing severe stability issues for me.  Any time I change the processor count and turn on the VM it goes all squirrelly and i have to start over.

 

After that I am going to install the VM using the unRAID 6.0 Manual steps outlined in section 7.5 of this wiki page http://lime-technology.com/wiki/index.php/UnRAID_Manual_6#Installing_a_Windows_VM

Link to comment

Personally I would tackle general stability first then start adding in devices, otherwise it's impossible to tell what's causing the instability.

 

I'm not clear from your last post if Unraid itself is unstable or just the Windows VM.

 

Think of it as a house, get the foundations right, then build a wall at a time, before putting a roof on and decorating the lounge....

Link to comment

good suggestion and good point.

 

I will go that route.  I am not sure where the stability issue lies right now.  In two instances unRAID was the problem and deleted my KVM information thus having me to remake it and the in two instances the Windows 10 VM was the stability issues.  One time having severe lag and performance issues and another time just constantly rebooting in a boot loop.

 

I will work to get a stable VM running now.

Link to comment

because installing a fresh ISO and upgrading is causing severe stability issues for me.  Any time I change the processor count and turn on the VM it goes all squirrelly and i have to start over.

 

Just throwing in that upgrading builds in Windows 10 guests has not worked for me either. It happened twice so far that upon guest reboot the keyboard was no longer passed through, unraid locked up, and I was forced to do a hard reset & parity check. Windows 10 also won't accept changes to processor count.

Link to comment

Just throwing in that upgrading builds in Windows 10 guests has not worked for me either. It happened twice so far that upon guest reboot the keyboard was no longer passed through, unraid locked up, and I was forced to do a hard reset & parity check

 

This... might actually explain some of the issues I'm having. Do you have any more information about this anywhere/ways to stop it?

Link to comment

I didn't notice any stability issues after upgrading to the latest build of Windows 10.

I completed this on 3 VM's, all with GPU passthrough.

I did have to set the CPU cores to 1 to complete the upgrade (if not I believe it fails), but then set them all back to original with no apparent issues (1 has 4 cores, 1 has 3 cores, and the last has 2 cores).

I did notice a little lag on 1 VM while the other was upgrading, however I assume the 1 core (Core 0) being hammered with the upgrade was introducing this.

Either way the server remained stable with no issues during any of this.

 

One last thing in regards to the USB woes, I just want to make sure you're aware that you cannot do ANY hot plugging of USB devices without passing through a USB controller to the VM (so assign prior to start, do not expect to remove and reinsert afterwards and expect it to work).

 

Also, are you using any USB extension cables? I have certainly had some issues with mine supporting multiple devices using a 20' cable without a powered hub, leading to the need to limit devices on the link (I somewhat expected this, so it wasn't exactly surprising).

Link to comment

OK so I started from scratch.  Here are the steps I took.

 

Created the VM.

2hwezbR.png

Started the VM

Windows went through install and upon first automatic reboot during isntallation the VM stopped (Green arrow turned to red box on the KVM screen) for some unkown reason.  Is there a way to get a log to see why?

Installed my graphics driver and then rebooted

Shut down and changed the CPU to 1

during bootup the VM stopped (Green arrow turned to red box on the KVM screen) for some unkown reason.  Is there a way to get a log to see why?

started backup again

Installed Windows 10 update 1511

shut down and changed the CPU back to 7

booted Windows 10 up

Windows only showed 1 vCPU. 

shut down but the KVM screen wouldn't show the VM as stopped.  Had to force stop.

checked settings.  7 vCPUs were assigned, not sure why windows didn't recognize the 7 of them.

Booted Windows 10 back up and it showed 7 vCPUs now.

 

I now have a fully updated Windows 10 build that I think is stable.  How do I go about getting hot plugging of USB to work?

Link to comment

One last thing in regards to the USB woes, I just want to make sure you're aware that you cannot do ANY hot plugging of USB devices without passing through a USB controller to the VM (so assign prior to start, do not expect to remove and reinsert afterwards and expect it to work).

 

Thanks for pointing this out.  I do want hot plugging so will have to figure out how to pass through a USB controller I guess.

 

Also, are you using any USB extension cables? I have certainly had some issues with mine supporting multiple devices using a 20' cable without a powered hub, leading to the need to limit devices on the link (I somewhat expected this, so it wasn't exactly surprising).

 

No I am not in this scenario.

Link to comment

OK scratch that.  This VM is not stable.  It keeps crashing and changing to a red box on the KVM page.  Any way I can check to see why it keeps crashing?

 

Here is the VM log, though I can't see any issues in it.

 

2015-12-23T14:25:55.621623Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
qemu: terminating on signal 15 from pid 2023
2015-12-23 14:26:18.547+0000: shutting down
2015-12-23 14:27:15.503+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name Win 10 Main PC -S -machine pc-i440fx-2.3,accel=kvm,usb=off,mem-merge=off -cpu host -m 14848 -realtime mlock=on -smp 1,sockets=1,cores=1,threads=1 -uuid e43d49b3-00c0-a740-1250-341a6f1f11a4 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Win 10 Main PC.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive file=/mnt/user/VM_HDD_Lib/Win 10 Main PC/vdisk1.img,if=none,id=drive-virtio-disk2,format=raw,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1 -drive file=mnt/user/VM_ISO_Lib/Win10ProSlipstreamed.iso,if=none,id=d0,bus=root.1,addr=00.0,multifunction=on,x-vga=on -device vfio-pci,host=00:1b.0,bus=root.1,addr=01.0 -msg timestamp=on
Domain id=4 is tainted: high-privileges
Domain id=4 is tainted: custom-argv
Domain id=4 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2015-12-23T14:27:17.669054Z Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23T14:27:19.719511Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23T14:27:21.719626Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
qemu: terminating on signal 15 from pid 2023
2015-12-23 15:03:56.986+0000: shutting down
2015-12-23 15:04:36.629+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name Win 10 Main PC -S -machine pc-i440fx-2.3,accel=kvm,usb=off,mem-merge=off -cpu host -m 14848 -realtime mlock=on -smp 7,sockets=1,cores=7,threads=1 -uuid e43d49b3-00c0-a740-1250-341a6f1f11a4 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Win 10 Main PC.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive file=/mnt/user/VM_HDD_Lib/Win 10 Main PC/vdisk1.img,if=none,id=drive-virtio-disk2,format=raw,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1 -drive file=mnt/user/VM_ISO_Lib/Win10ProSlipstreamed.iso,if=none,id=d0,bus=root.1,addr=00.0,multifunction=on,x-vga=on -device vfio-pci,host=00:1b.0,bus=root.1,addr=01.0 -msg timestamp=on
Domain id=5 is tainted: high-privileges
Domain id=5 is tainted: custom-argv
Domain id=5 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2015-12-23T15:04:38.871019Z Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23T15:04:40.890480Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23T15:04:42.890614Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
qemu: terminating on signal 15 from pid 2023
2015-12-23 15:09:13.183+0000: shutting down
2015-12-23 15:09:23.987+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name Win 10 Main PC -S -machine pc-i440fx-2.3,accel=kvm,usb=off,mem-merge=off -cpu host -m 14848 -realtime mlock=on -smp 7,sockets=1,cores=7,threads=1 -uuid e43d49b3-00c0-a740-1250-341a6f1f11a4 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Win 10 Main PC.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive file=/mnt/user/VM_HDD_Lib/Win 10 Main PC/vdisk1.img,if=none,id=drive-virtio-disk2,format=raw,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1 -drive file=mnt/user/VM_ISO_Lib/Win10ProSlipstreamed.iso,if=none,id=d0,bus=root.1,addr=00.0,multifunction=on,x-vga=on -device vfio-pci,host=00:1b.0,bus=root.1,addr=01.0 -msg timestamp=on
Domain id=6 is tainted: high-privileges
Domain id=6 is tainted: custom-argv
Domain id=6 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2015-12-23T15:09:26.196466Z Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23T15:09:28.290248Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23T15:09:30.289636Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23 15:29:23.258+0000: shutting down
2015-12-23 15:29:46.812+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name Win 10 Main PC -S -machine pc-i440fx-2.3,accel=kvm,usb=off,mem-merge=off -cpu host -m 14848 -realtime mlock=on -smp 7,sockets=1,cores=7,threads=1 -uuid e43d49b3-00c0-a740-1250-341a6f1f11a4 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Win 10 Main PC.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive file=/mnt/user/VM_HDD_Lib/Win 10 Main PC/vdisk1.img,if=none,id=drive-virtio-disk2,format=raw,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1 -drive file=mnt/user/VM_ISO_Lib/Win10ProSlipstreamed.iso,if=none,id=d0,bus=root.1,addr=00.0,multifunction=on,x-vga=on -device vfio-pci,host=00:1b.0,bus=root.1,addr=01.0 -msg timestamp=on
Domain id=7 is tainted: high-privileges
Domain id=7 is tainted: custom-argv
Domain id=7 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2015-12-23T15:29:49.004967Z Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23T15:29:51.023759Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23T15:29:53.023647Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23 15:46:43.130+0000: shutting down
2015-12-23 15:49:02.731+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name Win 10 Main PC -S -machine pc-i440fx-2.3,accel=kvm,usb=off,mem-merge=off -cpu host -m 14848 -realtime mlock=on -smp 7,sockets=1,cores=7,threads=1 -uuid e43d49b3-00c0-a740-1250-341a6f1f11a4 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Win 10 Main PC.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive file=/mnt/user/VM_HDD_Lib/Win 10 Main PC/vdisk1.img,if=none,id=drive-virtio-disk2,format=raw,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1 -drive file=mnt/user/VM_ISO_Lib/Win10ProSlipstreamed.iso,if=none,id=d0,bus=root.1,addr=00.0,multifunction=on,x-vga=on -device vfio-pci,host=00:1b.0,bus=root.1,addr=01.0 -msg timestamp=on
Domain id=8 is tainted: high-privileges
Domain id=8 is tainted: custom-argv
Domain id=8 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2015-12-23T15:49:04.921181Z Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23T15:49:07.017300Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23T15:49:09.016687Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23 15:49:42.225+0000: shutting down
2015-12-23 15:50:38.459+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name Win 10 Main PC -S -machine pc-i440fx-2.3,accel=kvm,usb=off,mem-merge=off -cpu host -m 14848 -realtime mlock=on -smp 7,sockets=1,cores=7,threads=1 -uuid e43d49b3-00c0-a740-1250-341a6f1f11a4 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Win 10 Main PC.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive file=/mnt/user/VM_HDD_Lib/Win 10 Main PC/vdisk1.img,if=none,id=drive-virtio-disk2,format=raw,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1 -drive file=mnt/user/VM_ISO_Lib/Win10ProSlipstreamed.iso,if=none,id=d0,bus=root.1,addr=00.0,multifunction=on,x-vga=on -device vfio-pci,host=00:1b.0,bus=root.1,addr=01.0 -msg timestamp=on
Domain id=9 is tainted: high-privileges
Domain id=9 is tainted: custom-argv
Domain id=9 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2015-12-23T15:50:40.646472Z Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23T15:50:42.671410Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23T15:50:44.671641Z qemu-system-x86_64: Warning: speed mismatch trying to attach usb device "USB to ATA/ATAPI Bridge" (super speed) to bus "usb.0", port "1" (full speed)
2015-12-23 15:51:21.335+0000: shutting down

Link to comment

 

Would one of those be causing this?

 

I don't know and that's why I was suggesting adding one at a time, testing, then add in another one...

 

OK but if I figure out which one is causing it, then what?  I can't live without any of them so is there a way to fix it once we determine which one it is?

Link to comment

 

Would one of those be causing this?

 

I don't know and that's why I was suggesting adding one at a time, testing, then add in another one...

 

OK but if I figure out which one is causing it, then what?  I can't live without any of them so is there a way to fix it once we determine which one it is?

 

I don't know...

 

The way to fix a problem (if possible) is to first work out what the problem is, I'm afraid there's no easy way around this. 

For what it's worth, when I was trying to setup a Unraid Virtual Machine, it took me over two weeks of work to get it going.  That's just how it works..

Link to comment

Any reason you have the the Initial and Max memory as different values?

I believe this use case is still experimental and not recommended.

It may only show up in the advanced mode (which you are in) but can't recall.

 

As CHBMB as already stated, we need to build the foundation before we add the walls/extras.

 

It only takes 1 unhappy component to make a VM unstable, period.

 

Case in point (and you can pull your hair, kick scream, get frustrated, punt the dog, etc... and it will make no difference) some hardware does NOT play friendly with pass through.

I spent countless hours figuring this out, and seriously thought JonP was bullshitting me with all the positive "look at how great this is" posts he was making.

 

However, nope, I just had unfriendly hardware, and I am happy that is behind me.

 

Anyhow, mine was always GPU related, and could make my VM's laggy, unstable, reboots would cause the entire server to freeze, complete power off of VM wouldn't allow it to come back up. This continued, I was frustrated, bought another old GPU and had similar problems... (this continues)..

 

I would definitely start with 1 item (your GPU would be the 1st I'd start with), and add a keyboard/mouse and use it, see how it does....

Then (and only then) if it is stable, add another..

 

Like it or not (and I am not saying this is the case) your GPU may not act right, and there are some things you can do to troubleshoot (see wiki about passing the rom file, OVMF, using Q35).

I also had a GPU (G210) that worked bad on 2 separate motherboards (Asus Z87, ASRock Z97), but worked great on my current X99 platform.

 

I think you'll get to the bottom of it, but unfortunately you have some work to get there.

Some people just have it easy from the get go (I was not one of these either).

Link to comment

Thanks for the post bungee91.  I am a tinkerer but I am not sure I am up for the time sink of making this work. 

 

Since I am down to only passing through the bare minimums I don't know what to turn off in order to even start the trial and error.

 

As for the memory, there is no reason to have them split, I was just doing it based on the assumption that it was offered.

 

I will put them back to the same and see what that does.

Link to comment

OK so I have put the memory to the same amount AND I have turned off PCIe ACS Override and so far the stability has been great!

 

Still don't have USB drive connectivity yet but will tackle that next.

 

Good to hear.

Also there is no reason to enable the override unless you have devices in the same group that you only want to pass some of them (it's an all or nothing thing).

This override could cause silent corruption or instability, however a LOT of people have no good alternative (including myself previously) so you deal with the possible risks.

Link to comment

Ok since I now have a stable Win 10 VM I trying to tackle the USB issue that I originally opened this ticket for.

 

I can't seem to get any USB drives regognized in the OS. 

 

I have two devices that I am trying to get working.  One is an USB 2.0 APRICORN SATA Wire (http://www.apricorn.com/sata-wire.html) and the other is a USB 3.0 Thermaltake BlackX Duet dock (http://www.thermaltake.com/products-model.aspx?id=C_00001756). 

 

Both of these devices have been passed through using the KVM GUI but nothing shows up in Windows 10.

 

Any suggestions?

 

I will try the suggestion from JonP posted here http://lime-technology.com/forum/index.php?topic=41922.0

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
Reply to this topic...

×   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.