kblaster
Contributor
Contributor

USB redirection on Ubuntu 12.04 LTS

Jump to solution

Hi guys,

On a clean installation of Ubuntu 12.04 LTS I'm installing the VMware Horizon View client (2.1.0).

I open a terminal and fire up /usr/bin/vmware-view, connect to my desktop using PCoiP and I get a spawn of vmware-view-usb failed.

After some searching I tried creating a symlink looking like this => ln -s /usr/lib/vmware/vmware-view-usb /usr/bin/vmware-view-usbd

This will get rid of the error and USB starts creating a log file, only still no USB redirection.

Examining the USB log file I saw that it's looking for a configuration file on different locations all non existing by default, so I created one on /etc/vmware.

I created a view-mandatory-config with the following configuration in it => viewusb.IncludeFamily = "storage" so flash drives would be redirected, still no USB redirection.

Examining the vmware-view.bin log I saw that USB dies in the very second that the client is started.

What am I doing wrong here :smileyconfused:?

0 Kudos
1 Solution

Accepted Solutions
peterbrown05
VMware Employee
VMware Employee

Hi,

thanks for the logs - most useful.

So - I *think* the problem is that you still have the *old* usb binaries on your system. From the log you can see:     

    Starting child: vmware-view-usb '-a' 'ipaddress' '-p' '32111' '-u' '[omitted]'

the binary vmware-view-usb is the old named binary which didnt support the arbitrator component. We kept the support there for this as back compatability and the client will first try to load that (if its available it will) but if not it will then switch to using the new usb binaries.

I presume that when you run;

     sudo ./vmware-usbarbitrator -f --trivia

then launch the usbd:

    sudo ./vmware-view-usbd -o log:trace

that both binaries run up and stay "stable" and the crash only happens once you launch the client.  the logs for the arbitrator look fine - if you waited longer before running "vmware-view" client, I think the usbd logs would also look a bit healthier. and i think its that when the old binaries are launched (which they shouldnt be) then things go wrong...

As such, can you look on your system for the old usb binaries, and remove them. It should then all work fine,

cheers

peterB

View solution in original post

0 Kudos
7 Replies
peterbrown05
VMware Employee
VMware Employee

hi there

have you launched the usb arbitrator?

     sudo ./vmware-usbarbitrator -f --trivia

then launch the usbd:

    sudo ./vmware-view-usbd -o log:trace

finally, launch the view client:

     vmware-view

kblaster
Contributor
Contributor

Hi Peter,

No I haven't done anything with the vmware-usbarbitrator. I will give it a go when I get back to work on Monday.

I'm keeping you updated.

Cheers.

0 Kudos
kblaster
Contributor
Contributor

Peter,

So I launched the vmware-view in the order you suggested but I am still not getting it to work.

I added some log files:

vmware-view-bin
https://www.dropbox.com/s/vnlf516cu51c3fw/vmware-view.bin-7806.log

vmware-view-usbd
https://www.dropbox.com/s/21e1i4r4fkv22of/vmware-view-usbd-7819.log

vmware-usbarbitrator
https://www.dropbox.com/s/1a5bhhqsh1092z1/vmware-usbarbitrator.log

0 Kudos
peterbrown05
VMware Employee
VMware Employee

Hi,

thanks for the logs - most useful.

So - I *think* the problem is that you still have the *old* usb binaries on your system. From the log you can see:     

    Starting child: vmware-view-usb '-a' 'ipaddress' '-p' '32111' '-u' '[omitted]'

the binary vmware-view-usb is the old named binary which didnt support the arbitrator component. We kept the support there for this as back compatability and the client will first try to load that (if its available it will) but if not it will then switch to using the new usb binaries.

I presume that when you run;

     sudo ./vmware-usbarbitrator -f --trivia

then launch the usbd:

    sudo ./vmware-view-usbd -o log:trace

that both binaries run up and stay "stable" and the crash only happens once you launch the client.  the logs for the arbitrator look fine - if you waited longer before running "vmware-view" client, I think the usbd logs would also look a bit healthier. and i think its that when the old binaries are launched (which they shouldnt be) then things go wrong...

As such, can you look on your system for the old usb binaries, and remove them. It should then all work fine,

cheers

peterB

0 Kudos
kblaster
Contributor
Contributor

Hi Peter,

So I got USB redirection working now.

1) I removed the symlink ln -s /usr/lib/vmware/vmware-view-usb /usr/bin/vmware-view-usbd
2) Created a new config file: sudo nano /etc/vmware/config and NOT /etc/vmware/config/view-mandatory-config ( config file only contains => viewusb.InculdeFamily= "storage" )

3) Started sudo /usr/lib/vmware/vmware-usbarbitrator -f --trivia

4) Started sudo /usr/lib/vmware-view-usbd -o log:trace

5) And finally started the vmware view client

Many thanks for giving me the information that I needed!

For those who are interested in any healthy log files, see below:

vmware-usbarb
https://www.dropbox.com/s/8n1uzef3qx4t4c0/vmware-usbarb-5960.log

vmware-usbd
https://www.dropbox.com/s/jvpgrya4s7d7qfw/vmware-view-usbd-5964.log

Cheers.

0 Kudos
peterbrown05
VMware Employee
VMware Employee

excellent! glad to hear you got it working in the end.

and, many thanks for sharing your solution with others on the forum.

cheers

peterB

0 Kudos
zDiesel
Contributor
Contributor

Can someone explain to me how you even got USB redirection enabled on Ubuntu at all?  I've enabled the partner repo and installed the View client, but I don't have the following files at all.  What am I doing wrong?  If it matters, I'm actually using 14.04.

/usr/lib/vmware/vmware-usbarbitrator

/usr/lib/vmware-view-usbd

0 Kudos