Install client drivers on Windows Server 2008 R2 (x64) running as KVM

Submitted by amatveev on #1

Trying to get working client on Windows Server 2008 R2 (x64)
Client starts, connects to server and even starts using the remote USB key (USB key with files).
I can see new storage device but when trying to access this disk an Explorer can not open the drive.

Have noticed that threre are no SimplyCore devices in device manager that are existing on Windows 7 x64 notebook (without virtualization layer)

Could you please clarify whether it possible to use VirtualHere in virtualizated environment (manly with Windows Server 2008 R2 and 2012 R2 servers) ?

Thank you in advance,

Submitted by amatveev on Fri, 2015/08/07 - 00:25

#2

Same story with Windows 7 x86 running as KVM

In server log (Debian 7 x64):

Aug 6 17:23:03 usbgate kernel: [ 1952.279873] usb 1-1.3.1.2: device descriptor read/64, error -110
Aug 6 17:23:03 usbgate kernel: [ 1952.455835] usb 1-1.3.1.2: reset high-speed USB device number 7 using ehci_hcd
Aug 6 17:23:03 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:03 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:06 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:06 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:09 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:09 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:12 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:12 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:15 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:15 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:18 usbgate kernel: [ 1967.524534] usb 1-1.3.1.2: device descriptor read/64, error -110
Aug 6 17:23:18 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:18 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:21 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:21 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:24 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:24 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:27 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:27 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:30 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:30 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:33 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:33 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:33 usbgate kernel: [ 1982.697231] usb 1-1.3.1.2: device descriptor read/64, error -110
Aug 6 17:23:33 usbgate kernel: [ 1982.873187] usb 1-1.3.1.2: reset high-speed USB device number 7 using ehci_hcd
Aug 6 17:23:36 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:36 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:39 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:39 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:42 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:42 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:44 usbgate kernel: [ 1993.278538] usb 1-1.3.1.2: device not accepting address 7, error -110
Aug 6 17:23:44 usbgate kernel: [ 1993.350932] usb 1-1.3.1.2: reset high-speed USB device number 7 using ehci_hcd
Aug 6 17:23:45 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:45 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:48 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:48 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:51 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:51 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:54 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:54 usbgate vhusbdx86_64: tx:t=11,a=0,s=0
Aug 6 17:23:54 usbgate vhusbdx86_64: Error -1 resetting device 0x03f0/0xf707 for capture
Aug 6 17:23:54 usbgate kernel: [ 2003.756232] usb 1-1.3.1.2: device not accepting address 7, error -110
Aug 6 17:23:54 usbgate kernel: [ 2003.757809] usb 1-1.3.1.2: USB disconnect, device number 7
Aug 6 17:23:54 usbgate kernel: [ 2003.828529] usb 1-1.3.1.2: new high-speed USB device number 8 using ehci_hcd
Aug 6 17:23:57 usbgate vhusbdx86_64: rx:t=10,a=0,s=0
Aug 6 17:23:57 usbgate vhusbdx86_64: tx:t=11,a=0,s=0

Linux usbgate 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u2 x86_64 GNU/Linux

Config:
It=1438848647
License=unlicensed,1,MCACDkn0jww6R5WOIjFqU/apAg4Um+mDkU2TBcC7fA1FrA==
PingTimeout=9
TraceMsgs=1
TCPNoDelay=1
AutoAttachToKernel=1
TCPPort=7575
PingInterval=4
UseAVAHI=0
CompressionLimit=384
ServerName=Desktop Hub
IgnoredDevices=03f0/1024,046d/c05b

Submitted by amatveev on Fri, 2015/08/07 - 00:39

#3

It seems the problem is that client machine is virtualized(((
Checked with Windows 2012 Server (bare metal) - works like a charm

Any ideas how to get it working on Windows as KVM guest (I use Proxmox VE)?

Thank you in advance!

Submitted by Michael on Fri, 2015/08/07 - 16:50

#4

VirtualHere works well on vmware, xen, virtualbox etc based vms when running as a client. The VirtualHere server can also run fine inside a server vm.

I havent tried on proxmox, so i tried just then and it just sat there when i tried to load a disk.

I think that proxmox is not implementing the bios correctly in their KVM module in linux or something like that.

VirtualHere doesn't use any special routines other than what is already in standard windows. so i think that KVM has the bug

Submitted by amatveev on Fri, 2015/08/07 - 17:27

#5

Hi, Michael

Thanks for your reply.
Could you please check how it does stand with linux client on Proxmox (I don't have any Linux virtual machine in my environment)

Thanks in advance!

Submitted by amatveev on Fri, 2015/08/07 - 18:15

#6

On the other hand your competitor (USB Redirector) works well

Any chance to get VirtualHere working?

Submitted by Michael on Fri, 2015/08/07 - 18:32

#7

I tested the client running in xubuntu 15.04 under proxmox and it works fine.

I could take another look at my client, if their stuff works under proxmox mine should too! :) Will let you know if i can fix it...

Submitted by Michael on Fri, 2015/08/07 - 20:20

#9

I installed win7 x86 in proxmox again and ran virtualhere, it installed the driver but was quite slow (im running proxmox inside a vmware vm virtualizing the VT instructions e.g 3 vms deep, which is probably why it was slow)

Anyway once the virtualhere drivers installed i was indeed able to use a disk in the proxmox vm,. i just had to make sure I waited longer than i did the first time i tested a few posts back.

Regarding windows 2012, are you running in an RDP session or just directly logging into the box via the vnc interface in proxmox? YOu would need to run virualhere on the root session, not an rdp session

Submitted by amatveev on Fri, 2015/08/07 - 20:38

#10

Actually I do run VirtualHere as a service (with SYSTEM account) so it should be true "root session"
I perform all my tests on Windows Server 2008 R2

Submitted by amatveev on Fri, 2015/08/07 - 20:40

#11

Have you tried to "Use" / "Stop using" / "Use again" ?

One or two time (if i'm correct - on fresh booted system) I got luck to see the content of my usb stick but after I disconnect USB and connect it again (via client) - it never worked again

Submitted by Michael on Fri, 2015/08/07 - 20:59

#12

I notice in your log in the top post, your server is not registered, you cannot connect to the server with the client running as a service, if you havent purchased it..

Submitted by amatveev on Fri, 2015/08/07 - 21:04

#13

Hmm... I thought "TRIAL" 1 usb device means any client...
How could I test though?

Ready to buy a license but what to be sure software works in my evironment

Submitted by amatveev on Fri, 2015/08/07 - 21:40

#16

Connected with mstsc /admin /v: ...

No luck((( Detected new device but can not open any content.

Do you have chance to try Windows Server 2008 R2 on your side?

Submitted by Michael on Fri, 2015/08/07 - 21:45

#17

You must run virtualhere in the root session not a terminal services session... it does work if you do that, ive tested a while ago, i dont have 2008 anymore to test with

Submitted by amatveev on Fri, 2015/08/07 - 22:43

#18

Tried to run from hypervisor console (100% root session) - no difference(

Submitted by Michael on Sat, 2015/08/08 - 20:11

#19

I downloaded a trial Windows Server 2008 R2 Standard edition and installed under proxmox and it also works fine with virtualhere. Not sure about your setup or your security settings, but virtualhere needs to install two drivers, if they can be installed then it should work...

Submitted by jkutianski on Wed, 2015/08/12 - 04:15

#20

Probably is caused on the server side. I've the similars with a TP-link TL-MR3020 as server.

Submitted by amatveev on Thu, 2015/08/20 - 01:37

#21

I've installed fresh Windows 2012R2 as KVM guest. VirtualHere works like a charm