VMware Horizon Community
AdamBil
Enthusiast
Enthusiast

Linux VMware View PCoIP client found! (finally)

Hi all -

I (finally) stumbled across a VMware View (PCoIP enabled) linux client. You can download it here:

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12...

It's from HP's site and is part of their T5545 update. I downloaded the executable and extracted it to a temp folder and then SSH'd over the vmware-view-client_4.0.0-215529_i386.deb to my custom Debian build and installed it. Then I PXE booted the new image and see that it in fact has the PCoIP and multi-head components (bonus!). Smiley Happy

Hope this helps everyone. Not sure why this wasn't available in the first place as competitors are more than happy to hand out their connection clients.

Warmest regards,

--Adam

Tags (3)
Reply
0 Kudos
77 Replies
Jt3rry
Contributor
Contributor

Would you mind detailing the steps you took? I'm very interested in getting this working from my Ubuntu 10.10 systems.

Thanks!

Reply
0 Kudos
Flicka
Contributor
Contributor

Same here.  We are running into issues because View v4.6 requires a physical WinOS PC to run on, and we use Macbook Pros.

  • Yes, we can dual-boot, but it's a hassle.
  • No, I am not going to break EULAs and set clients up with unlicensed code for production, but for a POC or demo, a View client in an Ubuntu VM makes sense.

Please detail the PCoIP capable Linux View client you used and the steps you took to get there, or put a link to someone else who did...

If anyone has an update on View v4.6 client with PCoIP running on OSX, please let me know.  (The open source OSX client only has RDP, which doesn't work well across most WAN connections and is therefore worthless for client demos...)

Reply
0 Kudos
befrenchy
Contributor
Contributor

Follow this howto on setting up your LTSP environment:

http://edin.no-ip.com/blog/hswong3i/ltsp-ubuntu-intrepid-mini-howto

Then setup your client environment. Download the HP view client packages from the HP thinpro download page, you will need version 4 and 4.5. Version  4 includes  hptc-rdesktopwhich you need in order to install the view client 4.5.

Chroot to /opt/ltsp/i386

Install the following packages:

     libpcsclite1, libqtcore4

Install hptc-rdesktop_1.6.0-1.27_i386.deb (this package is included with version 4)

Install vmware-view-client_4.5.0-293049-1_i386.deb

Create symbolic link /etc/vmware/usb.link -> /usr/lib/vmware/vmware-view-usb (You need for usb redirection to work with PCoIP)

Chmod 4755 /etc/vmware/usb.link

Chmod 4755 /usr/lib/vmware/vmware-view-usb

Update the client image

Setup your screen script for vmware view by following step 2 in this document:

https://help.ubuntu.com/community/UbuntuLTSP/VMWareViewVDI

My ltsp.conf looks like this:

[default]
        CONSOLE_KEYMAP="en"
        VMVIEW_SERVERURL="http://view_connection_server"
        VMVIEW_OPTIONS="--fullscreen --domainName yourdomainname"
        XKBLAYOUT="en"
        SCREEN_03=vmview

Reboot your client

Now we ran into an issue with the screen going black and all you see is the mouse cursor. I can reproduce the problem by switching screens, when i switch back to my view session, screen is black and the only way to recover is to reboot the client. It seems to be a problem with the display settings but I'm not sure exactly how to fix this. If anyone has any idea please let me know and I would be curious to know if anybody else can reproduce this problem. We were testing with a Dell optiplex GX620.

I quickly threw this together so if it's not clear, I apologize in advance. Let me know if you have any more questions.

Reply
0 Kudos
johnsmithgold
Contributor
Contributor

I've installed vmware view 4.0.1-235010 on Fedora 13 using this inctruction: http://sites.google.com/site/linuxvdi/

Unfortunately, PCoIP connection doesn't work for me.

I've got such log:http://pastebin.com/MUyPxdzL

I suppose that the most interesting part is this:

vmware-view| vmware-remotemks-container(16383): Creating VMware Remote MKS interface
vmware-view| vmware-remotemks-container(16383): NOT_REACHED /build/mts/release/bora-234939/bora/mks/remote/mksRemoteMain.c:427
vmware-view| vmware-remotemks-container(16383): vmdbPipe_Streams: Couldn't read
vmware-view| vmware-remotemks-container(16383): Vmdb_AddConnection2Ex: failed, code -32
vmware-view| vmware-remotemks-container(16383): Unable to create remote MKS interface.
vmware-view| vmware-remotemks-container(16383) died.

I can't understand what it means and what to do with it.

I tried to connect using PCoIP from Windows host to the same server, and it worked without problems.

Have anyone met with such problem?

Reply
0 Kudos
anonimous
Enthusiast
Enthusiast

I've installed vmware-view-client_4.5.0-293049-1 on Centos 5.6.

RDP works well, but it doesn't work using PCoIP and here is the Log:

May 07 17:10:19.997: vmware-view| Host codepage=UTF-8 encoding=UTF-8
May 07 17:10:19.998: vmware-view| Using locale directory /usr/share/locale
May 07 17:10:20.004: vmware-view| Command line: /usr/bin/vmware-view --protocol=PCOIP
May 07 17:10:20.004: vmware-view| Using gtk+ version 2.10.4
May 07 17:10:20.012: vmware-view| Using Metacity window manager
May 07 17:10:23.215: vmware-view| Busy: Initializing connection...
May 07 17:10:23.216: vmware-view| Initializing connection to broker https://mydomain.net:443
May 07 17:10:24.178: vmware-view| Auth Info: Name: windows-password, result: ok
May 07 17:10:29.571: vmware-view| Busy: Logging in...
May 07 17:10:30.963: vmware-view| Auth Info: Name: , result: ok
May 07 17:10:30.963: vmware-view| Executing secure HTTP tunnel: /usr/bin/vmware-view-tunnel
May 07 17:10:30.963: vmware-view| Starting child: /usr/bin/vmware-view-tunnel 'https://mydomain.net:443'
May 07 17:10:30.965: vmware-view| Number of monitors on this screen is 1.
May 07 17:10:30.966: vmware-view| Current window manager does not support _NET_WM_FULLSCREEN_MONITORS message.
May 07 17:10:30.992: vmware-view| vmware-view-tunnel(4785): Connecting to tunnel server 'mydomain.net:443' over HTTPS.
May 07 17:10:30.992: vmware-view| vmware-view-tunnel(4785): SOCKET creating new socket, connecting to X.X.X.X:443 (mydomain.net)
May 07 17:10:30.993: vmware-view| Gtk: gtk_widget_size_allocate(): attempt to allocate widget with width 460 and height -9
May 07 17:10:31.437: vmware-view| vmware-view-tunnel(4785): TUNNEL READY
May 07 17:10:33.053: vmware-view| Transitioning: Connecting to the desktop...
May 07 17:10:35.959: vmware-view| vmware-view-tunnel(4785): SOCKET creating new listening socket on port 0
May 07 17:10:35.959: vmware-view| vmware-view-tunnel(4785): Creating new listener "Port2" on 127.0.0.1:55554 to server 192.168.1.13:32111.
May 07 17:10:35.998: vmware-view| Desktop connect successful.  Starting desktop using PCOIP...
May 07 17:10:35.998: vmware-view| Transitioning: Connecting to the desktop...
May 07 17:10:36.002: vmware-view| Connecting to desktop with total geometry 1680x1050.
May 07 17:10:36.002: vmware-view| Starting usb redirection to '127.0.0.1:55554' with ticket '69f8a406-9ef7-41f8-944d-0bf37d813666'.
May 07 17:10:36.002: vmware-view| Starting child: /usr/bin/vmware-view-usb '-a' '127.0.0.1' '-p' '55554' '-u' '[omitted]'
May 07 17:10:36.005: vmware-view| Connecting to desktop CN=CH3PRO,OU=Applications,DC=vdi,DC=vmware,DC=int: PCOIP://myusername@X.X.X.X:4172
May 07 17:10:36.005: vmware-view| Starting child: vmware-remotemks-container 'pcoip_client' 'mksvchanclient' '[omitted]' '1680x1050' '20974536'
May 07 17:10:36.015: vmware-view| vmware-view-usb(4787): A previous instance of vmware-view-usb is already running
May 07 17:10:36.015: vmware-view| vmware-view-usb(4787) died.
May 07 17:10:36.015: vmware-view| vmware-view-usb(4787) exited with status: 1
May 07 17:10:36.113: vmware-view| vmware-remotemks-container(4788): Creating VMware Remote MKS interface
May 07 17:10:36.125: vmware-view| Attempting to fullscreen window using _NET_WM_STATE_FULLSCREEN hint.
May 07 17:10:36.163: vmware-view| vmware-remotemks-container(4788): NOT_REACHED /build/mts/release/bora-340165/bora/mks/remote/mksRemoteMain.c:450
May 07 17:10:36.163: vmware-view| vmware-remotemks-container(4788): vmdbPipe_Streams: Couldn't read
May 07 17:10:36.163: vmware-view| vmware-remotemks-container(4788): Vmdb_AddConnection2Ex: failed, code -32
May 07 17:10:36.163: vmware-view| vmware-remotemks-container(4788): Unable to create remote MKS interface.
May 07 17:10:36.163: vmware-view| vmware-remotemks-container(4788) died.
May 07 17:10:36.163: vmware-view| vmware-remotemks-container(4788) exited with status: 1

May 07 17:10:36.163: vmware-view| Busy: Connecting to desktop...
May 07 17:10:36.163: vmware-view| Transitioning: Connecting to the desktop...
May 07 17:10:38.552: vmware-view| vmware-view-tunnel(4785): SOCKET creating new listening socket on port 0
May 07 17:10:38.552: vmware-view| vmware-view-tunnel(4785): Creating new listener "Port4" on 127.0.0.1:40795 to server 192.168.1.13:32111.
May 07 17:10:38.592: vmware-view| Desktop connect successful.  Starting desktop using PCOIP...
May 07 17:10:38.592: vmware-view| Transitioning: Connecting to the desktop...
May 07 17:10:38.596: vmware-view| Connecting to desktop with total geometry 1680x1050.
May 07 17:10:38.596: vmware-view| Starting usb redirection to '127.0.0.1:40795' with ticket 'e64d54af-da47-4e9f-86d9-b0b59d47e2d0'.
May 07 17:10:38.596: vmware-view| Starting child: /usr/bin/vmware-view-usb '-a' '127.0.0.1' '-p' '40795' '-u' '[omitted]'
May 07 17:10:38.597: vmware-view| Connecting to desktop CN=CH3PRO,OU=Applications,DC=vdi,DC=vmware,DC=int: PCOIP://myusername@X.X.X.X:4172
May 07 17:10:38.598: vmware-view| Starting child: vmware-remotemks-container 'pcoip_client' 'mksvchanclient' '[omitted]' '1680x1050' '20974690'
May 07 17:10:38.609: vmware-view| vmware-view-usb(4792): A previous instance of vmware-view-usb is already running
May 07 17:10:38.609: vmware-view| vmware-view-usb(4792) died.
May 07 17:10:38.609: vmware-view| vmware-view-usb(4792) exited with status: 1
May 07 17:10:38.732: vmware-view| vmware-remotemks-container(4793): Creating VMware Remote MKS interface
May 07 17:10:38.745: vmware-view| Attempting to fullscreen window using _NET_WM_STATE_FULLSCREEN hint.
May 07 17:10:38.782: vmware-view| vmware-remotemks-container(4793): NOT_REACHED /build/mts/release/bora-340165/bora/mks/remote/mksRemoteMain.c:450
May 07 17:10:38.782: vmware-view| vmware-remotemks-container(4793): vmdbPipe_Streams: write failed, draining reads
May 07 17:10:38.782: vmware-view| vmware-remotemks-container(4793): vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF
May 07 17:10:38.782: vmware-view| vmware-remotemks-container(4793): vmdbPipe_Streams: Couldn't initiate write
May 07 17:10:38.782: vmware-view| vmware-remotemks-container(4793): Vmdb_AddConnection2Ex: failed, code -31
May 07 17:10:38.782: vmware-view| vmware-remotemks-container(4793): Unable to create remote MKS interface.
May 07 17:10:38.782: vmware-view| vmware-remotemks-container(4793) died.

May 07 17:10:38.783: vmware-view| vmware-remotemks-container(4793) exited with status: 1
May 07 17:10:38.783: vmware-view| Busy: Connecting to desktop...
May 07 17:10:38.783: vmware-view| Transitioning: Connecting to the desktop...
May 07 17:10:41.160: vmware-view| vmware-view-tunnel(4785): SOCKET creating new listening socket on port 0
May 07 17:10:41.161: vmware-view| vmware-view-tunnel(4785): Creating new listener "Port6" on 127.0.0.1:33515 to server 192.168.1.13:32111.
May 07 17:10:41.240: vmware-view| Desktop connect successful.  Starting desktop using PCOIP...
May 07 17:10:41.240: vmware-view| Transitioning: Connecting to the desktop...
May 07 17:10:41.243: vmware-view| Connecting to desktop with total geometry 1680x1050.
May 07 17:10:41.244: vmware-view| Starting usb redirection to '127.0.0.1:33515' with ticket '7f567575-feab-4c61-b935-d4f53688e65a'.
May 07 17:10:41.244: vmware-view| Starting child: /usr/bin/vmware-view-usb '-a' '127.0.0.1' '-p' '33515' '-u' '[omitted]'
May 07 17:10:41.246: vmware-view| Connecting to desktop CN=CH3PRO,OU=Applications,DC=vdi,DC=vmware,DC=int: PCOIP://myusername@X.X.X.X:4172
May 07 17:10:41.246: vmware-view| Starting child: vmware-remotemks-container 'pcoip_client' 'mksvchanclient' '[omitted]' '1680x1050' '20974849'
May 07 17:10:41.255: vmware-view| vmware-view-usb(4797): A previous instance of vmware-view-usb is already running
May 07 17:10:41.255: vmware-view| vmware-view-usb(4797) died.
May 07 17:10:41.256: vmware-view| vmware-view-usb(4797) exited with status: 1
May 07 17:10:41.353: vmware-view| vmware-remotemks-container(4798): Creating VMware Remote MKS interface
May 07 17:10:41.365: vmware-view| Attempting to fullscreen window using _NET_WM_STATE_FULLSCREEN hint.
May 07 17:10:41.401: vmware-view| vmware-remotemks-container(4798): NOT_REACHED /build/mts/release/bora-340165/bora/mks/remote/mksRemoteMain.c:450
May 07 17:10:41.401: vmware-view| vmware-remotemks-container(4798): vmdbPipe_Streams: write failed, draining reads
May 07 17:10:41.401: vmware-view| vmware-remotemks-container(4798): vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF
May 07 17:10:41.401: vmware-view| vmware-remotemks-container(4798): vmdbPipe_Streams: Couldn't initiate write
May 07 17:10:41.401: vmware-view| vmware-remotemks-container(4798): Vmdb_AddConnection2Ex: failed, code -31
May 07 17:10:41.401: vmware-view| vmware-remotemks-container(4798): Unable to create remote MKS interface.
May 07 17:10:41.401: vmware-view| vmware-remotemks-container(4798) died.

May 07 17:10:41.401: vmware-view| vmware-remotemks-container(4798) exited with status: 1
May 07 17:10:41.401: vmware-view| Cancelling 0 broker XML requests.
May 07 17:10:42.931: vmware-view| User cancelled.
May 07 17:10:42.931: vmware-view| Busy: Loading desktops...
May 07 17:10:42.931: vmware-view| Number of monitors on this screen is 1.
May 07 17:10:42.931: vmware-view| Current window manager does not support _NET_WM_FULLSCREEN_MONITORS message.

Knows someone howto solve this problem?

Reply
0 Kudos
ealaqqad
Enthusiast
Enthusiast

Hi,

I  believe VMware View PCoIP Client for Linux is a work in progress,  though I have managed to extract the client from a published HP  executable. I have done this just to prove its possible, & you  should not use it in production unless if you get a consent or agreement  with HP and other parties involved. Though if you are curious to try it  just as I did on my Ubuntu machine, you could look at:

VMware View PCoIP Client on Ubuntu is finally here

This post show a video of using the PCoIP Client on Ubuntu 11.04 and the background behind it.

VMware View PCoIP on Ubuntu How to

This  post show how I have acheived PCoIP running Client on Ubuntu. Its just  interesting to find out how simple it was to acheive and repeat the  process. I have streamed the process so anyone using Ubuntu can repeat it with ease.

Warning: If you want to use this commercially things or anything beside testing you will need to remember:

              - This is totally not supported

              - You might run in legal trouble.

Please reward points if this help.

Regards,

Eiad Al-Aqqad

Technology Consultant @ VMware

b: http://www.VirtualizationTeam.com

b: http://www.TSMGuru.com

Regards, Eiad Al-Aqqad Technology Consultant @ VMware b: http://www.VirtualizationTeam.com b: http://www.TSMGuru.com
Reply
0 Kudos
Jt3rry
Contributor
Contributor

What does your xorg.conf look like? I'm not able to see the gray title bar once connected in the View client (running Ubuntu 10.10 32bit) If I hover over the upper area of the screen with the mouse the View title bar (the one with the "Connect USB device", and "options" tabs) is missing...

I'm assuming my xorg is configured incorrectly, I'm on an older Dell P4 desktop with a Mx440 AGP card which probably doesn't help matters. I have Twin View configured correctly and running well with an XP Pro VM, dual screens/all screens (I've been running this way for a number of months). I just currently have no USB redirection or any clean way to exit the View client, so I've been kicking my self out by connecting in from another (native Microsoft) View client (running in VM workstation 7).

Also the title bar is missing even if I run the View client in large screen mode, full screen mode or all screen modes...

thanks!

Reply
0 Kudos
ealaqqad
Enthusiast
Enthusiast

Hi Jt3rry,

It seems missing here too after my last update though I am running Ubuntu 11.04 64-bit. I though I had it seen it before. I am pretty sure I did as I got my USB to work once before. Either way this is just experimental usage and still for me much better than RDP even without USB access.

Please reward points if this help.

Regards,

Eiad Al-Aqqad

Technology Consultant @ VMware

b: http://www.VirtualizationTeam.com

b: http://www.TSMGuru.com

Regards, Eiad Al-Aqqad Technology Consultant @ VMware b: http://www.VirtualizationTeam.com b: http://www.TSMGuru.com
Reply
0 Kudos
anonimous
Enthusiast
Enthusiast

BTW has anyone running this client on Centos 5.6 successfully?

It doesn't work over PCoIP and I have this problem:

July 27 17:10:36.163: vmware-view| vmware-remotemks-container(4788): NOT_REACHED /build/mts/release/bora-340165/bora/mks/remote/mksRemoteMain.c:450
July 27 17:10:36.163: vmware-view| vmware-remotemks-container(4788): vmdbPipe_Streams: Couldn't read
July 27 17:10:36.163: vmware-view| vmware-remotemks-container(4788): Vmdb_AddConnection2Ex: failed, code -32
July 27 17:10:36.163: vmware-view| vmware-remotemks-container(4788): Unable to create remote MKS interface.
July 27 17:10:36.163: vmware-view| vmware-remotemks-container(4788) died.
July 27 17:10:36.163: vmware-view| vmware-remotemks-container(4788) exited with status: 1

Reply
0 Kudos
Alph4d0g007
Contributor
Contributor

I just managed to Install the HP client on Backtrack 5 (Ubuntu 10.04), dont know if that helps ...

Reply
0 Kudos
Jt3rry
Contributor
Contributor

Yes, but for those of you who have a "working" install, is the View title/USB bar functional? Theres a lot of functionality thats lost with out it...

Attached is an example screen shot, the only way I can get View to work fully in Linux is if I first use VM workstation to run another windows VM, with the view client installed, so its not the most efficient.

I fully understand this is experimental, it just be good if we can get this one last part figured out...

Thanks!

Reply
0 Kudos
Alph4d0g007
Contributor
Contributor

you're right there's no bar, but the USB redirection works.

I dont know if there's a way to reset your desktop like on the windows client -.-

Reply
0 Kudos
Jt3rry
Contributor
Contributor

Interesting. How is it that you have a USB device connected to the physical PC that gets passed to the virtual with out some how telling the view client to pass that device over? Is there some manual config editing that maps a specific USB device?

Reply
0 Kudos
Alph4d0g007
Contributor
Contributor

don't know ... just let me have a look ...

Reply
0 Kudos
Alph4d0g007
Contributor
Contributor

cant find any configuration file for the client ...

but you could start the client with arguments:

--usb=<options>

but there isn't any referenc doc for the options ...

Reply
0 Kudos
Jt3rry
Contributor
Contributor

So for USB redirection to work I'd have to start the View client with some additional --usb= cli argurments, of which the syntax isn't known?

Reply
0 Kudos
Jt3rry
Contributor
Contributor

I've also found this http://blog.offenders.org/?p=75 I need to spend some time and try that install method

Reply
0 Kudos
Alph4d0g007
Contributor
Contributor

try this one (Page 3 of this post)

http://communities.vmware.com/message/1729567#1729567

the only thing you should do is to take the packages from:

ftp://ftp.hp.com/pub/tcdebian/pool/thinpro32/

there are some in the main and some in the non-free folder.

install the hptc-rdesktop directly do not install the Version 4 of the view ... makes it much easier Smiley Wink

Reply
0 Kudos
admin
Immortal
Immortal

I too have the same issue on RHEL 6 as shown below.  It works fine when selecting the RDP protocol though.

I've successfully got it working on Debian 6 without issue though.  I'm not sure how to get around this with RHEL 6 so if anyone has any ideas they'd be greatly appreciated.

Sep 09 12:38:47.090: vmware-view| Starting child: vmware-remotemks-container 'pcoip_client' 'mksvchanclient' '[omitted]' '1680x1050' '75504642'
Sep 09 12:38:47.165: vmware-view| vmware-remotemks-container(18668): Creating VMware Remote MKS interface
Sep 09 12:38:47.168: vmware-view| Attempting to fullscreen window using _NET_WM_STATE_FULLSCREEN hint.
Sep 09 12:38:47.177: vmware-view| vmware-remotemks-container(18668): NOT_REACHED /build/mts/release/bora-234939/bora/mks/remote/mksRemoteMain.c:427
Sep 09 12:38:48.177: vmware-view| vmware-remotemks-container(18668): vmdbPipe_Streams: Couldn't read
Sep 09 12:38:48.177: vmware-view| vmware-remotemks-container(18668): Vmdb_AddConnection2Ex: failed, code -32
Sep 09 12:38:48.177: vmware-view| vmware-remotemks-container(18668): Unable to create remote MKS interface.
Sep 09 12:38:48.178: vmware-view| vmware-remotemks-container(18668) died.
Sep 09 12:38:48.178: vmware-view| vmware-remotemks-container(18668) exited with status: 1

Reply
0 Kudos
admin
Immortal
Immortal

I just wanted to share that I got PCoIP working on RHEL 6.1 32bit.  After doing an strace and finding that I was failing on libcrypto.so.0.9.8 I started googling.  I found this website: http://blog.offenders.org/?cat=17 which in turn led me to find and install the newer thin client version (4.6).  PCoIP now runs without error.  If the link changes you can likely find the newer version just by searching for "HP ThinPro Add-On (VMware View Broker".

To convert the debian package to an rpm I ran this a mentioned by a prior poster.

alien --to-rpm vmware-view-client*.rpm

rpm -Uvh --force --nodeps vmware-view-client*.rpm

Enjoy PCoIP on RHEL!

Reply
0 Kudos