Gns3-gui: The VMWware Tools power-on script did not run successfully

[jtorri]

Windows 10 Prof 64bit. VMWare Workstation 14.1.2 build-8497320
Did full clone of GNS3 2.1.6 and upgraded it to 2.1.8 via provided upgrade menu option.
Also modified .gns3 project files and gns3 application ini files from 2.1.6 to 2.1.8
The process has worked successfully since GNS3 1.5

All projects seems to be working fine but when GNS3 VM starts the following modal dialog appears.
"The VMWware Tools power-on script did not run successfully
in this virtual machine. If you have configured a custom
power-on script in this virtual machine, make sure
that it contains no errors.....'
When I close this dialog the GNS3 VM completes loading.

When I close GNS3 application a similar modal dialog appears. Closing that dialog closed the VM and the GNS3 application.
Bottom line, based on cursory testing it appears not to be a show stopper but just a curiosity.
Hope my explanation makes sense. Thanks!

[jtorri]

Not sure if significant but this behavior does not occur with GNS3 2.1.7

[e1ext]

I'm having the same issue after upgrading from 2.1.6 to 2.1.8, also I already tried the workaround from https://github.com/GNS3/gns3-gui/issues/2511 hoping that it would have different result on me.

Not only powering it on but powering off is also having issue

Is there any workaround to fix it?

Here's error when I close gns3 and vmware tried to shutdown the gns3 vm

"The request to power off this virtual machine failed because the corresponding VMWare tools script did not run successfully"

[JonathanFourie]

My two coppers worth here...

The difference between 2.1.6 and 2.1.8...
2.1.6 contains the following files
in directory /etc/vmware-tools;
_poweroff-vm-default
poweron-vm-default
suspend-vm-default
tools.conf.dpkg-new
vm-support
poweroff-vm-default.dpkg-new
resume-vm-default
statechange.subr
tools.conf
tools.conf.old_
/etc/vmware-tools/scripts/vmware
_network
network.dpkg-new_

2.1.8 only contains the directories, no files
According to this thread, it may be a packaging bug in Ubuntu
https://github.com/vmware/open-vm-tools/issues/43

[JonathanFourie]

Stopped getting error after copying files from 2.1.6 VM to 2.1.8 with WINSCP, and changing permissions and executables

gns3@gns3vm:/etc/vmware-tools$ ls -lhR
.:
total 64K
-rwxr-xr-x 1 root root 4.3K Jun 23 22:17 poweroff-vm-default
-rwxrwxr-x 1 root root 4.3K Feb 21 11:57 poweroff-vm-default.dpkg-new
-rwxr-xr-x 1 root root 4.3K Jun 23 22:17 poweron-vm-default
-rwxr-xr-x 1 root root 4.3K Jun 23 22:17 resume-vm-default
drwxr-xr-x 3 root root 4.0K Jun 23 21:11 scripts
-rwxrwxr-x 1 root root 1.5K Jun 17 2014 statechange.subr
-rwxr-xr-x 1 root root 4.3K Jun 23 22:17 suspend-vm-default
-rw-rw-r-- 1 root root 0 Apr 21 2017 tools.conf
-rw-rw-r-- 1 root root 518 Feb 21 11:58 tools.conf.dpkg-new
-rw-rw-r-- 1 root root 20 Jun 17 2014 tools.conf.old
-rwxr-xr-x 1 root root 7.5K Jun 23 22:17 vm-support

./scripts:
total 4.0K
drwxr-xr-x 2 root root 4.0K Jun 23 22:17 vmware

./scripts/vmware:
total 24K
-rwxr-xr-x 1 root root 8.5K Jun 23 22:17 network
-rwxr-xr-x 1 root root 8.5K Jun 23 22:17 network.dpkg-new
gns3@gns3vm:/etc/vmware-tools$

GNS3 client still not seeing GNS3 VM though

[jtorri]

Thanks JonathanFourie. That seemed to do the trick!

[e1ext]

Hi JonathanFourie,

You are right, the vmware-tools folder only contain folders, and I did as you suggested and it did the trick as jtorri said, no more power-on and off error

Thanks

[grossmj]

I reverted https://github.com/GNS3/gns3-vm/commit/0f9811cf8933b21f1cb2f9dd66d9536adf21a9ec which seems to have created this issue.

Hopefully everything will be fine for next release. Sorry for that.

[sajith-kumar]

I had the same issue with GNS3.VM.Workstation (2.1.9). But I followed the instruction given by @JonathanFourie , great it works.

[JBSecvrity]

Reinstall VMtools is the solution.

Tested in 2.1.9 version.

Open a console into the VM Gns3 machine:

_sudo su_

_apt-get remove open-vm-tools_

_apt-get autoremove_

_apt-get purge open-vm-tools_

_apt-get install open-vm-tools_

The problem should already be solved.

[sajith-kumar]

Thanks @jbsecvrity

[benvision1]

Thanks @JBSecvrity

[av8rgeek]

Just in case someone like me runs into a similar problem where the upgrade fails on an opem-vm-tools error, follow the instructions above to remove open-vm-tools, run sudo apt-get update, and then re-run the update menu item. Prior to doing this, it always erred out on a vmtoolsd error (versions 2.1.5, 2.1.6, 2.1.11). I am running VMWare Workstation 12.

[arys123]

thanks @JBSecvrity
it works