Support

Dear Michael,

Sorry if this has Been asked before, but using search i couldnt find the Solution:

Since V2.0 virtualhere Looks like supporting powerpc. Does it work on synology ds213+ which is a powerpc CPU (qoriq)? As in the other thread here about the ts 251, which IS also Not explicitely mentioned under supported devices, i dare to ask if ds213+ is supported :)

Thanks!

Dear Michael et al.

am curious to try your product and plan on buying a NAS to be running it on a Qnap TS-251, which is Bay-Trail x86 SOC. So shouldnt the x86 version work on that NAS? Because it is not listed in your list of supported NAS's.

Thanks and kind regards!

<p>Hello,
</p>
<p>After running some exhaustive test with raspberry pi and virtualhere server, eventually, I got it crashed. This is the log:
</p>
<p>Thu Jul 9 08:51:43 2015 LOG_INFO >>> Starting v2.3.6 (Built: Jul 8 2015, 12:03:54)<<<<br />
Thu Jul 9 08:51:43 2015 LOG_INFO Using configuration /etc/virtualhere/config.ini<br />
Thu Jul 9 08:51:43 2015 LOG_ERR Parsing config encountered error 22, (Invalid argument)<br />

<p>Hello,
</p>
<p>docker@boot2docker:~$ vhclient -t LIST<br />
VirtualHere IPC, below are the available devices:<br />
(Number in brackets = address, * = Auto-Use)
</p>
<p>B17 (remotehub:7575)<br />
*--> TTL232R-3V3 (4294967410) (In-use by you)<br />
*--> Olimex OpenOCD JTAG ARM-USB-OCD-H (4294967408) (In-use by you)
</p>
<p>Auto-Find currently off<br />
Auto-Use All currently on<br />
Reverse Lookup currently off<br />

<p>Hello,
</p>
<p>I might be trying to push it too hard here, but currently within our organization we are evaluating VirtualHere server performance w.r.t. usage in our testing systems for embedded devices. The use of Raspberry PI with VirtualHere looks very desirable and is quite affordable.
</p>
<p>Ultimately, the usecase here is to flash an embedded device with USB-connected JTAG adapter using OpenOCD. The setup we are having is as follows:
</p>

<p>Hello,
</p>
<p>I am trying to call "vhclient -t EXIT" to finalize a running client daemon instance, but the process does not really shut down:
</p>
<p>docker@boot2docker:~$ vhclient --help<br />
VirtualHere Client 2.9.9, Use USB devices over a network<br />
Usage: vhclient [-h] [-c <str>] [-a] [-t <str>] [-r <str>] [-l <str>] [-m] [-n]<br />
-h, --help Display this help<br />

<p>Hello,
</p>
<p>I have installed init.d service to launch the VirtualHere service on boot up in Raspberry Pi. It works quite well, but the time it takes to stop it is 30 seconds:
</p>
<p>pi@raspberrypi ~ $ sudo service vhusbdpin start<br />
pi@raspberrypi ~ $ time sudo service vhusbdpin stop
</p>
<p>real 0m30.111s<br />
user 0m0.730s<br />
sys 0m2.100s
</p>

Hope anyone has any tips with my issue.

This issue happens on Ubuntu 14.04 and Xbmcbuntu, on the same hardware. OS i fully patched, and I experience this on two identical computers (Intel NUC DIY3217U). I have tried this with a few different versions of the server and client. Same thing always happens.

I successfully run vhusbdx86_64, connect USB device and successfully attach it to a Win8 client.
Problem is that as soon as I access the USB-device, the server computer will freeze (full freeze).

Hi Michael,

sorry to say but I found another bug, which occurs time-to-time after sleep mode.
The symptoms: the devices is disconnected after few sec. The app is running fine, able to connect to server, user is able to assign device, however, after few seconds the devices is unbounded

Server log:
Jun 26 08:40:20 localhost vhusbdi386: Device 2131 BOUND to connection 81
Jun 26 08:40:25 localhost vhusbdi386: Device 2131 UNBOUND from connection 81

getting checksum errors when files are uploaded to the Arduino with usb connected to Pi 2. Also have another very odd problem. With VirtualHere driver pack installed my USB's see new device plugged into them (on the client) but they show up as unknown and I have to manually install them. once I uninstall the driver packs everything is fine, plug in a device and it installs drivers accordingly. and when the Arduino is plugged into the Raspberry Pi the device shows something like 0ff4 or something to that effect. Raspberry Pi is connected wired.