VMware tools still not working on newest 2.2.3, can't gracefully shutdown



  • Hey guys,

    What is the matter with Open VMware tools? Still not working, can't reboot of switch of gracefully.

    If you hit any button, it will force a power off, very annoying :/

    I was expecting it to be updated and working since this has been reported ages ago.

    Thanks!


  • Banned

    Have you updated the package?

    Its working here.



  • @Supermule:

    Have you updated the package?

    Its working here.

    just curious
    on which version tools are you on ?



  • @Jamerson:

    @Supermule:

    Have you updated the package?

    Its working here.

    just curious
    on which version tools are you on ?

    It was a fresh install
    new iso, installed vmtools straight from the package manager tab, so I was hoping at least in this way it would be fixed by now. It seems it is still downloading an old verison of the open vm tools



  • @Jamerson:

    @Supermule:

    Have you updated the package?

    Its working here.

    just curious
    on which version tools are you on ?

    it says 1280544_10 on the package version after it is installed, but I noticed when I invoke the installation of the package, it downloads the 1280544_9 instead. So the package info is messed up, or simply it downloads the wrong package. When I uninstall it, I can also see 1280544_9 being uninstalled.

    It seems the latest version of open vmtools is 9.10.2822639 which is a bit different numbering from the package tab, perhaps we just have a very ancient version available for pfsense?
    It needs to be updated on the package repository, someone definitely spelled something wrong while adding the package to the list.


  • Banned

    1280544_10

    @Jamerson:

    @Supermule:

    Have you updated the package?

    Its working here.

    just curious
    on which version tools are you on ?


  • Banned

    And yes. It installs _9 but it says _10

    Its been mentioned and CMB has modified the tools so we didnt get a shitload of .ko errors in the console.



  • @Supermule:

    And yes. It installs _9 but it says _10

    Its been mentioned and CMB has modified the tools so we didnt get a shitload of .ko errors in the console.

    so can you gracefully shutdown the VMs?


  • Banned

    Yes. No problem.

    Just right click the VM and chose shut down guest. THen it shuts down gracefully.



  • @Supermule:

    Yes. No problem.

    Just right click the VM and chose shut down guest. THen it shuts down gracefully.

    Ok, there is definitely something different now. The main console screen of the VM, if you click the stop button it power off the VM instead of invoking shutdown even though if you hover the mouse cursor on tops is says shutdown guest. Before on version 2.2 when the openvm tools last worked fine to shutdown guest, you could click the stop button and it would gracefully shutdown the VM.

    Indeed, going to VM, Power, Shutdown guest work fine as you said. I didn't try that before.

    I tried on a Windows VM, pressing the stop button gracefully shutdown the guest. So I believe there is still something weird with this open vm tools.

    I'mm try to restart a host and see if the host triggers graceful shutdown of pfsense as it used to in the past.


  • Banned

    It will.

    But it depends on how your configure your gueat OS.

    Edit settings -> Options -> Power controls




  • Mine is set up exactly the same. Can you hover the mouse cursor over the stop button, and then click on it to check what message do you get? Mine says guest shutdown when you hover it, but then when you click it says power off. The vmware tools power controls in the options tab are all set up like yours

    Please check the attached images







  • Banned

    I run virtual Machine version 7. That could be the difference.






  • I created a VM7 version here, installed from scratch. Still the same. What ESXi version are you using?

    I'm going to try across a few different clients, but at least across 2, the same issue for me, all ESXi 5 or 5.5 update 1-2


  • Banned

    4.1U3



  • @Supermule:

    1280544_10

    @Jamerson:

    @Supermule:

    Have you updated the package?

    Its working here.

    just curious
    on which version tools are you on ?

    you are running a old VM hardware.
    VMware tools are broke.
    on the new release 2.2.X the vmx drivers are included.


  • Banned

    It works fine here.

    So not broke for me. Despite running on old vmware version. CMB has reprogrammed the tools so the .ko errors went away since the drivers was included in 10.1


  • LAYER 8 Global Moderator

    So what exactly is not working.. I just installed clean pf 2.2.3 64bit clean on esxi 6, latest build 2715540

    Installed the opnevmtools package.. vm is hardware 11 which is default for 6..  I am having no problems - tools show installed 3rd party.. Seems like current version to me if you run the cmd to show version.

    I shut it down twice from vclient – goes down smooth, etc..  So what is the problem exactly??  Are you trying to run some modified shutdown script??  Is you issue that it shows _10 in the package but downloads _9 pbi?  That seems to be cosmetic issue with no real consequence




  • @johnpoz:

    So what exactly is not working.. I just installed clean pf 2.2.3 64bit clean on esxi 6, latest build 2715540

    Installed the opnevmtools package.. vm is hardware 11 which is default for 6..  I am having no problems - tools show installed 3rd party.. Seems like current version to me if you run the cmd to show version.

    I shut it down twice from vclient – goes down smooth, etc..  So what is the problem exactly??  Are you trying to run some modified shutdown script??  Is you issue that it shows _10 in the package but downloads _9 pbi?  That seems to be cosmetic issue with no real consequence

    The problem is just when you open the console and hit the stop button or hit the stop button from the vsphere client when highlighting the VM. If you hover the mouse cursor on top of the button it says guest shutdown, but then when you click on it, it says do you want to power off? then it powers off the VM. The way around is to go to power and then manually select guest shutdown.

    I've tested rebooting the server and it indeed switched off the guest gracefully before rebooting the host.


  • LAYER 8 Global Moderator

    When I push the little red button in my console it does a normal shutdown..

    See 1st attachment.

    My guess is you have it set to power off - see 2nd pic.






  • @johnpoz:

    When I push the little red button in my console it does a normal shutdown..

    See 1st attachment.

    My guess is you have it set to power off - see 2nd pic.

    I've tested this now and managed to isolate do hosts using 5.5 U1, U2 and latest build doesn't suffer from this problem.

    So it seems it is basically a ESXi bug :/



  • https://doc.pfsense.org/index.php/Versions_of_pfSense_and_FreeBSD

    FreeBSD 10.0
    Posted on September 9, 2014 by Guest OS Team

    Support for FreeBSD 10.0 has been introduced for this product:

    ESXi 5.5 Update 2

    For more information about software support, please check the VMware Compatibility Guide



  • @gjaltemba:

    https://doc.pfsense.org/index.php/Versions_of_pfSense_and_FreeBSD

    FreeBSD 10.0
    Posted on September 9, 2014 by Guest OS Team

    Support for FreeBSD 10.0 has been introduced for this product:

    ESXi 5.5 Update 2

    For more information about software support, please check the VMware Compatibility Guide

    good eye!


  • Banned

    But it runs fine on 4.1U3 and dont have the issue and tools working fine.


  • LAYER 8 Global Moderator

    As to it running fine in 4.anything is pure luck.. freebsd 10 was not supported until 5.5u2

    Why anyone would still be running 4 or even 5.x  I don't get - 6 has been out for quite some time.. I can see not going to it the first day it releases in a production setup.  But 2 patches have already been released, etc..  I would think its safe to move too.

    Support for 4.x ended back in 2014.. Over a year ago.. Why would you be using unsupported version?


  • Banned

    Its the only cluster left on 4.1

    The rest of the clusters run 5.5U2 on all the rest running the cloud servers.

    Only the FW cluster run on 4.1 :)


  • LAYER 8 Global Moderator

    Well that makes sense, lets run the latest version of firewall software on the oldest esxi cluster we have..  Yeah that makes sense not to update it, because having more than 1 esxi host makes it very difficult to move vms around to different versions of esxi..  So you can update the other host..  I can see your pain in trying to get off no longer supported version for well over a year.. ;)

    So do you have it on 4.1 because it better at holding off DDOS as well? ROFL ;)


  • Banned

    Does it matter?

    It runs very good and very stable. Since its Enterprise Plus version then a lot is automated. I have better uptime than Amazon at the moment so yes. It works.



  • @johnpoz:

    As to it running fine in 4.anything is pure luck.. freebsd 10 was not supported until 5.5u2

    Why anyone would still be running 4 or even 5.x  I don't get - 6 has been out for quite some time.. I can see not going to it the first day it releases in a production setup.  But 2 patches have already been released, etc..  I would think its safe to move too.

    Support for 4.x ended back in 2014.. Over a year ago.. Why would you be using unsupported version?

    ESXi6 is full of bugs, I use Veeam for several clients and there are many problems involving the latest VMFS 6 as well. I downgraded everything back to 5.5. I don't want my client backups risking to corrupt.



  • @mephisto:

    @johnpoz:

    As to it running fine in 4.anything is pure luck.. freebsd 10 was not supported until 5.5u2

    Why anyone would still be running 4 or even 5.x  I don't get - 6 has been out for quite some time.. I can see not going to it the first day it releases in a production setup.  But 2 patches have already been released, etc..  I would think its safe to move too.

    Support for 4.x ended back in 2014.. Over a year ago.. Why would you be using unsupported version?

    ESXi6 is full of bugs, I use Veeam for several clients and there are many problems involving the latest VMFS 6 as well. I downgraded everything back to 5.5. I don't want my client backups risking to corrupt.

    we are using Veeam on ESXI 6.0 everything is fine no issue noted .
    this forum is about PFSENSE Firewall,
    Make sure your VEEAM is on the latest Path 2U.


  • Banned

    Hve you tested your backups and if ther are working in case of failure?



  • @Supermule:

    Hve you tested your backups and if ther are working in case of failure?

    yes sir,
    everything is running fine,
    just tested a exchange and domain controller, both runs smoothly.
    so patch your back up server.



  • The open vm tools package downloaded from within pfsense is an older version, version 9.4.0 build 1280544. The latest version of open vm tools in gitbhub is 9.10.2 (https://github.com/vmware/open-vm-tools/releases/tag/stable-9.10.2). How can we install packages manually in pfsense? And is it recommended to use the latest version in github for that purpose?



  • Any thoughts here?


  • LAYER 8 Global Moderator

    What features or bug fixes make this newer version pertinent to pfsense/freebsd?  Is this new version in the freebsd ports?  If so then I would think the package maintainer could update the package.

    The current version seems to do what is required of it, allow for shutdown of the vm in a graceful manner - to be honest I can not think of what else you would need the tools for?  So if the old version does this not clear to what you would want in the newer version?



  • Well, it's just that it was recommended by a member in the open vm tools github issues in connection with my issue here: https://github.com/vmware/open-vm-tools/issues/29

    I already solved that issue and apparently it was not caused by the open vm tools installation itself. My disk space in my VM was not enough which caused the issue.

    But I was still interested in installing the latest open vm tools package especially on a freebsd 10.1-based pfsense instance.


  • LAYER 8 Global Moderator

    well what I see here
    http://portsmon.freebsd.org/portoverview.py?category=&portname=open-vm-tools&wildcard=

    The version is current what available.. Once this has been update I would assume the package maintainer will update the package.



  • Got it. Thanks.


Log in to reply