Hello, Community
There is a nice peace of software to use USB devices remotely - VirtualHere. Quite powerful, fast and simple.
It work perfectly well (the client part) on bare metal, XEN, VirtualBox and VmWare but not on Proxmox VE
I wrote to support and got the follwing reply:
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
I tried both kernel 2.6 and 3.10 - no difference.
Clients: Windows 7 x86/x64, 2008 R2, 2012 R2
May be somebody has any ideas on how to tune KVM or debug what is going wrong?
There is a nice peace of software to use USB devices remotely - VirtualHere. Quite powerful, fast and simple.
It work perfectly well (the client part) on bare metal, XEN, VirtualBox and VmWare but not on Proxmox VE
I wrote to support and got the follwing reply:
Quote:
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
Clients: Windows 7 x86/x64, 2008 R2, 2012 R2
May be somebody has any ideas on how to tune KVM or debug what is going wrong?