linux guest too small ("fit guest now" disabled) - sporadic

dec1 commented 7 years ago

Hello, I have VMware Workstation 12 Pro (Windows 10 Host) running a Linux OpenSuse Leap 42.2 Guest. It regularly happens when I start the guest that it is too small and can't be resized bigger until I shutdown and restart both the guest and vmware. In the Linux guest I have "open-vm-tools", and "open-vm-tools-desktop" version 10.0.7-1.1-x86_64 (vendor opensuse).

I can't see any pattern to when this sizing problem occurs, and I cant seem to find a way to fix it without having to reboot guest and restart vmware. Any ideas?

Thanks in Advance

oliverkurth commented 7 years ago

Thank you for reporting. I have created an internal bug for this issue, I hope you will hear back from us soon.

ghost commented 7 years ago

@dec1 could you attach a screenshot taken from the host so we can see what you mean? Is it the guest's resolution that is too small, or the DPI that is wrong? Attaching the logs from both the VMX running on the host and from tools also couldn't hurt: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007873 for more information on how to setup tools logging in the guest.

dec1 commented 7 years ago

Ok. When the problem arises again.

If I enable logging in the guest will the log file grow indefinitely? Where do I find the host log?

dec1 commented 7 years ago

vmware_small wmware_logs.zip

dec1 commented 7 years ago

Hello, above a screenshot and the logs from the guest. I don't know where the host logs are.

dec1 commented 7 years ago

vmsupport-2017-03-23-10-47.zip

dec1 commented 7 years ago

Above also the result of "help"->"support" -> "collect support data" in my vmware workstation 12.5.4

dec1 commented 7 years ago

vmware_normal

dec1 commented 7 years ago

Above how it should look. The only way I can achieve this is by restarting both the guest and vmware

microcoder commented 7 years ago

Hello, I have a similar problem on VMWare Player 12.5.5 (Windows 10 Host) running a Kubuntu 17.04 (KDE 5.9). Under Ubuntu 17.04 this problem is not observed, only under KDE and installed package open-vm-tools, open-vm-tools-desktop v10.1.5. If i removing packages open-vm-tools (v10.1.5) and after installing vmware tools from main menu: Player->Manage->Install VMWare Tools (v10.1.6) then this problem is not observed, resolution guest OS changing, drag-n-drop, etc working! Need build package open-vm-tools v.10.1.6 :)

oliverkurth commented 7 years ago

@microcoder , in the non-working case (KDE), can you please check with the command:

ps awx | grep vmtoolsd

if there is a process running with the "-n vmusr" option?

microcoder commented 7 years ago

@oliverkurth, not there is a process on Kubuntu 17.04 (up-to-date):

$ ps awx | grep vmtoolsd 981 ? Ssl 0:00 /usr/bin/vmtoolsd 1935 pts/1 S+ 0:00 grep --color=auto vmtoolsd

vmware-logs.tar.gz

oliverkurth commented 7 years ago

Thanks. The vmusr process is needed for resolutions settings and copy/paste.

Does it work when you run: /usr/bin/vmware-user-suid-wrapper ? This should be done automatically when KDE starts, from the file /etc/xdg/autostart/vmware-user.desktop .

microcoder commented 7 years ago

Yes, it working:

$ /usr/bin/vmware-user-suid-wrapper vmware-user: could not open /proc/fs/vmblock/dev

$ ps awx | grep vmtoolsd 981 ? Ssl 0:02 /usr/bin/vmtoolsd 6245 pts/1 S 0:00 /usr/bin/vmtoolsd -n vmusr 6247 pts/1 S+ 0:00 grep --color=auto vmtoolsd

file /etc/xdg/autostart/vmware-user.desktop:

[Desktop Entry] Type=Application Encoding=UTF-8 Exec=/usr/bin/vmware-user-suid-wrapper Name=VMware User Agent # KDE bug 190522: KDE does not autostart items with NoDisplay=true... # NoDisplay=true X-KDE-autostart-phase=1

Then I restarted the system and the service running:

$ ps awx | grep vmtoolsd 877 ? Ss 0:00 /usr/bin/vmtoolsd 1944 ? Sl 0:00 /usr/bin/vmtoolsd -n vmusr 2912 pts/2 S+ 0:00 grep --color=auto vmtoolsd

Then i do power off and power on virtual machine with starting OS, service not running This is working not stable. Any ideas? Thanks.

oliverkurth commented 7 years ago

If it only happens with Kubuntu 17.04, but not with vanilla Ubuntu 17.04, that looks like a bug in Kubuntu. I can try to reproduce this and file a bug at Kubuntu, or you can and post the bug id here.

When you said it does not happen in Ubuntu 17.04, is that with gnome?

microcoder commented 7 years ago

Please help file a bug at Kubuntu. Thanks. Yes, with Unity/Gnome.

dec1 commented 7 years ago

Were the logs and other information I provided of any help?

oliverkurth commented 7 years ago

I couldn't find anything useful in the logs. @dec1 can you please enable logging for the user process? Put the following lines into /etc/vmware-tools/tools.conf:

# Enable new "vmusr" service logging to a file.
vmusr.level = debug
vmusr.handler = file
vmusr.data = /tmp/vmware-vmusr.${USER}.log

I am not sure if your issue is the same as microcoder's issue - the common factor is KDE, but you say you need to restart WS. Can you please check if there is a user process of vmtoolsd running in the non-working case, as in https://github.com/vmware/open-vm-tools/issues/152#issuecomment-290523016 ? Will it work when you start it manually with:

/usr/bin/vmware-user-suid-wrapper ?

dec1 commented 7 years ago

Hello,

Will do. So next time I have the problem you want me to send you

/tmp/vmware-vmusr.${USER}.log ?

On April 11, 2017 at 7:42 PM Oliver Kurth notifications@github.com wrote:

I couldn't find anything useful in the logs. @dec1 https://github.com/dec1 can you please enable logging for the user process? Put the following lines into /etc/vmware-tools/tools.conf:

# Enable new "vmusr" service logging to a file.
vmusr.level = debug
vmusr.handler = file
vmusr.data = /tmp/vmware-vmusr.${USER}.log

I am not sure if your issue is the same as microcoder's issue - the common factor is KDE, but you say you need to restart WS. Can you please check if there is a user process of vmtoolsd running in the non-working case, as in
#152 (comment) https://github.com/vmware/open-vm-tools/issues/152#issuecomment-290523016 ? Will it work when you start it manually with:

/usr/bin/vmware-user-suid-wrapper ?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/vmware/open-vm-tools/issues/152#issuecomment-293362659 , or mute the thread https://github.com/notifications/unsubscribe-auth/AFr8fYVvvVpX4SzVUOldoM2FDUx5k-wdks5ru8mdgaJpZM4MgVPl .

oliverkurth commented 7 years ago

Yes, please, in addition to checking if the vmtoolsd user process is running.

Please also attach the vmware.log file. This should be in the same directory where the data of the VM are stored.

Thanks!

dec1 commented 7 years ago

Hello Oliver.

> ps awx | grep vmtoolsd
 1219 ?        Sl     0:00 /usr/bin/vmtoolsd
 2552 pts/0    S+     0:00 grep --color=auto vmtoolsd

> /usr/bin/vmware-user-suid-wrapper

guest resized properly ..thanks now I dont need to restart (sometimes multiple times) each time!

> ps awx | grep vmtoolsd

 1219 ?        Sl     0:00 /usr/bin/vmtoolsd
 2656 pts/0    Sl     0:00 /usr/bin/vmtoolsd -n vmusr
 2932 pts/0    S+     0:00 grep --color=auto vmtoolsd

dec1 commented 7 years ago

The logs as requested

vmware-vmusr.declan.zip vmware.zip

microcoder commented 7 years ago

Hello, Oliver!

Did you registered a bug at Kubuntu, or not? Thanks.

oliverkurth commented 7 years ago

Sorry @microcoder , I wasn't able to create a setup yet to reproduce. I was out last week, and when I tried a fresh installation for 17.04-beta1 didn't work for me. I need to try again.

oliverkurth commented 7 years ago

@microcoder , I was able to reproduce the issue, and reported a bug on Launchpad: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1682647 . Feel free to comment there.

oliverkurth commented 7 years ago

@dec, thank you for the log files. We are going to analyze them.

vmware / open-vm-tools

linux guest too small ("fit guest now" disabled) - sporadic #152