Linux - Cycle Multiple Monitors doesn't complete correctly.

[jdmac87]

Setup parameters

Host

• OS: Windows 7 Enterprise (x64)
• Hypervisor Software: VMWare Workstation 10.0.7 build-2844087

Guest

• Distro: Arch Linux
• Kernel: 4.4.1-2-ARCH
• Open-VM-Tools: 10.0.7-1 (open-vm-tools 6:10.0.7-1 on arch repos).
• Desktop Environment: Tested with gnome-shell and xfce4 both on Xorg.
• Services Enabled via systemd: vmtoolsd and vmware-vmblock-fuse enabled as services.
• Kernel Modules enabled (confirmed in lsmod):

# lsmod | grep vm
vsock
vmwgfx
vmw_balloon
vmxnet3
vmw_vmci
vmw_pvscsi

Issue Description

Usual features of vmtools working (copy/paste, drag/drop, resize full screen)
Resize without fullscreen mode doesn't still but this isn't the issue being rasied.

When in full screen mode, click the Cycle Multiple Monitors task bar button.
Screen flickers, but remains on primary display.
Guest OS becomes aware of the second display and the correct resolution, but the VMWare workstation software on the host system doesn't span to the second display.

Notably the primary display remains as-is on appearance but when attempting to continue use the mouse cursor is actually upper left of where it is making a selection or 'click'.

Possibly lead on cause found

Wonder if something has changed in Kernel 4.4 as installing the linux-lts kernel of Arch Linux (presently 4.1.18-1-lts) it proceeds to work as expected.
Resize without fullscreen mode doesn't still but this isn't the issue being rasied.

[jdmac87]

Kernel: 4.4.3-1-ARCH has now been added to Arch repos and the same issue is present.

[MaxPower88]

I have the same issue with a Kali Linux as guest system. The active monitor appears the same and the second monitor becomes black. The cursor is visible in both, but nothing is clickable except the fullscreen bar of the VMware player.

[prusswan]

Had this issue on Ubuntu 16.04 using 4.4 kernel. Switching to 3.19 works

[eldamir]

@prusswan I'd like to try switcing to 3.19 as well, but it seems to have been removed from my installation, and is no longer available in the repos. Any tips on where to go from here? Can I grab the deb somewhere?

[eldamir]

As always, I solve the issue right after asking for help 😄

I did

mkdir kernel
cd kernel
wget http://launchpadlibrarian.net/220635919/linux-headers-3.19.0-31-generic_3.19.0-31.36~14.04.1_amd64.deb
wget http://launchpadlibrarian.net/220668669/linux-headers-3.19.0-31_3.19.0-31.36~14.04.1_all.deb
wget http://launchpadlibrarian.net/220635970/linux-image-3.19.0-31-generic_3.19.0-31.36~14.04.1_amd64.deb
sudo dpkg -i linux-*

[jdmac87]

I've gone and retested this on 16.04 with the following kernels.
4.2.0 - Working
4.3.0 - Working
4.3.6 - Working
4.4.0 - Not working.

Seems definitive something changed from 4.3.6 to 4.4.0 that has stopped this working.

[ipe-zi]

I made a similar test as jdmac87 with Manjaro Linux. With kernel 4.1 and 4.2 it works, with 4.4 it doesn't works.

Does anybody have experiences with newer kernels than 4.6 or is there a fix in open-vm-tools or vmware-tool?

[jdmac87]

@ipe-zi I've tested 4.6.4-1-ARCH and it's not working again for me. I've seen no changes to open-vm-tools on github but the version now seems to be 10.0.7-5 from Arch linux repo.
So it remains unclear if Kernel or OVT fixed the issue at this point.

[ipe-zi]

@jdmac87 Thank's for your response. The solution of eldamir to go back to a older kernel wörks for me only at the moment because Manjaro Linux supports the 4.1 LTS Kernel only until mid of 2017. So in the future I should have a solution for this issue. Do you have another solution than going back to an older kernel?

[jdmac87]

@ipe-zi sorry, no other workaround that I can offer right now. As in my original post, i too had been using 4.1 LTS. Have you tested 4.6 in manjaro? Being that it is based on arch i imagine you'll likely get similarly good results.

[ipe-zi]

@jdmac87 I tested in earlier times with 4.6 (I think it was a 4.6.1 or 4.6.2) but it doesn't work correct. As I understand your post it doesn't work for you, too or did I misunderstand you?

[jdmac87]

@ipe-zi sorry i just spotted an autocorrect from my phone. It was meant to say "and it is NOW working for me". So yeah 4.6.4-1 is working but given your reply, I have the impression its not the kernel at fault. What version of open-vm-tools are you currently using? Mine (working) is 10.0.7-5.

I'll see if I can get time today to go back and test 4.2 and 4.4.

[jdmac87]

With (arch linux) 10.0.7-5 open-vm-tools, I've tested the following:
4.6.4-1 = Working
4.4.16-1-lts = Working

Unfortunately, ran out of time for testing right now. Will try to get chance again for some more.
@ipe-zi if you can get chance, see if 10.0.7-5 open-vm-tools is available in manjaro and if it works for you.

[ipe-zi]

@jdmac87 Thank you for your support. I will check it with the 10.0.7-5 open-vm-tools and the both linux kernels

[jdmac87]

@ipe-zi just a heads up, I installed Ubuntu 16.04.1 a few minutes ago and install open-vm-tools-desktop from official canonical/ubuntu repos. It has version 10.0.7-3227872-2ubuntu1 and seems to be working on 4.4.0-31-generic (out of the box).

I will make a caveat, I've since upgraded to WS Pro 12, but I'm not entirely convinced the issue was limited to WS 10.

Interesting that the version is 10.0.7 on ubuntu and arch repos, yet I still only see 10.0.5 as the latest on GitHub... Unless I've missed something?

[asangas]

@jdmac87 I can confirm that kernel 4.3.6 is working on Ubuntu 1604. Really appreciate the workaround.

[prusswan]

Just a heads up, 4.4.0-36.55-generic (Ubuntu's numbering) corresponds to kernel 4.4.16
while 4.4.0-31-generic corresponds to 4.4.13

For the full list, refer to: http://people.canonical.com/~kernel/info/kernel-version-map.html

Anyway, I don't have this issue anymore and am currently using the latest 4.4.0-38

[chrisghill]

@prusswan I'm currently experiencing this issue, and I'm on 4.4.0-38. What version of open-vm-tools are you using?

$ /usr/bin/vmware-toolbox-cmd -v 10.0.7.52125 (build-3227872)
$ uname -r 4.4.0-38-generic

[prusswan]

@chrisghill should be the same as what is available in the official repositories, but I have updated to Workstation 12.5 which supports the current version of Windows 10 (used by the host)

[chrisghill]

Yes, I'm also on Workstation 12.5. Specifically, 12.5.0 build-4352439.

[prusswan]

not sure if it would be relevant, but what is your host OS and graphics card(s)?

I'm currently on Win 10 Anniversary Update (or RS1) with Intel HD4000.

[chrisghill]

I'm on Win 10 Anniversary Edition (specifically version 1607 OS Build 14393.187) and running an nVidia GTX 770. I also just installed new GPU drivers last night thinking that could be the issue, so those are up to date as well (372.90).

I just tried installing an Unbuntu 14.04 VM and updating VM tools and the multiple monitors works.

[chrisghill]

I should also add that I'm running Kubuntu, not Ubuntu. Not sure if KDE could potentially have any affect on this.

[JustonDavies]

I can reproduce this issue. I can resize my guest, up or down, full screen to windowed without any issue. However when I try to toggle 'View'>'Use All Displays in Full Screen' I get a second blank monitor that the guest cannot use OR I get a a mirror of the first desktop window scaled to the size of the second screen. Usually I get the mirrored screen.

I am running a Debian Stretch (9) guest on a Late 2013 Macbook Pro with the following installed:

• Linux Guest:
  • Kernel Linux version 4.9.0-2-amd64 x86_64
  • MATE Desktop version 1.16.1
  • open-vm-tools version 2:10.1.5-5055683-2
  • open-vm-tools-desktop version 2:10.1.5-5055683-2
• macOS Host
  • macOS Sierra version 10.12.3
  • VMWare Fusion version 8.5.9 (5234762)

I cannot reproduce the issue using a Debian Jessie (8) on the same host with the following installed:

• Linux Guest:
  • Kernel Linux version 3.16.0-4-amd64
  • MATE Desktop version 1.8.1
  • open-vm-tools version 2:9.4.6-1770165-8
  • open-vm-tools-desktop version 2:9.4.6-1770165-8
• macOS Host
  • macOS Sierra version 10.12.3
  • VMWare Fusion version 8.5.9 (5234762)

Here's some other output that might be useful:
$ /usr/bin/vmware-toolbox-cmd -v 10.1.5.59732 (build-5055683)
$ uname -r 4.9.0-2-amd64
$ lsmod | grep vm vmw_vsock_vmci_transport 28672 2 vsock 36864 3 vmw_vsock_vmci_transport vmw_balloon 20480 0 vmwgfx 237568 2 vmw_vmci 69632 2 vmw_balloon,vmw_vsock_vmci_transport ttm 98304 1 vmwgfx drm_kms_helper 155648 1 vmwgfx drm 360448 5 vmwgfx,ttm,drm_kms_helper

[tnkr]

Seeing an issue with with open-vm in what appears to be an issue with kernel 4.11.6

┌─[tnkr@parrot]─[~]
└──╼ $ps aux | grep vm
tnkr       1390  0.3  0.3 242612 28048 ?        S    14:40   0:00 /usr/bin/vmtoolsd -n vmusr
tnkr       1542  0.0  0.0  12724   976 pts/0    S+   14:42   0:00 grep --color=auto vm
┌─[tnkr@parrot]─[~]
└──╼ $uname -a
Linux parrot 4.11.0-parrot6-amd64 #1 SMP Parrot 4.11.6-1parrot6 (2017-06-28) x86_64 GNU/Linux

Cannot use cycle monitor as it appears that there is only 1 monitor even though I have 3 attached.

I have seen this issue on all recently updated linux, specifically Debian, variants. Not sure if there is a fix floating around but I haven't found it yet.
This guest is being run on a Windows 10 box running Workstation Pro 12.5.7. Issue does not appear on the premade Kali vmware image from Offensive Security and was not showing up 2 month ago on straight ISO based vmware machines.

I can say that cycle monitors shows available and all monitors appear in the selection menu but the error appears right after: