Support

Hi

I've got a QNAP HS-251 with a licenced VirtualHere server running. I've noticed that since I've added the VirtualHere app, the NAS disks are no longer spinning down. Using the blkdevMonitor.sh script, I've noticed that if VH is not running, then almost no disk activity is happening. Is VH writing to some log files that would stop the disks from spinning down?

Thanks
Loris

I'm setting up a few USBIP servers on a raspberry pi, to share with a linux client on the network. On the rPi I am putting a bunch of Android devices that I will use the linux client to talk to via adb.

Unfortunately I'm running into a few problems, the main of which is that actually getting adb to talk to the devices is exceedingly flaky (last week it was working, today I can't get it to really work at all).

Here's what I'm seeing:

I have the server running on a Raspberry Pi (trial) and a client on Windows 2008R2.
Every couple of minutes the client pops a notification that it's running on a trial server (I know that, no need to keep reminding me...)
And after about 20 notifications it crashes.
Problem signature:
Problem Event Name: APPCRASH
Application Name: vhui64_304.exe
Application Version: 3.0.4.0
Application Timestamp: 55a60479
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18869
Fault Module Timestamp: 556366fd

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>