Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Open-VM-Tools don't work well any more on pfsense 2.2+

    Scheduled Pinned Locked Moved Virtualization
    43 Posts 6 Posters 12.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • E
      EMWEE
      last edited by

      Yup when u shutdown from the GUI it stops the packages first. I think it runs /etc/rc.stop_packages and then shuts down.

      So where can i configure a custom script at shutdown? A custom poweroff= entry in tools.conf seems to be ignored.

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        that is not where you put it..

        [2.2.2-RELEASE][root@pfSense.local.lan]/usr/local/bin: vmware-toolbox-cmd help script
        script: control the scripts run in response to power operations
        Usage: /usr/local/bin/vmware-toolbox-cmd script <power|resume|suspend|shutdown><subcommand>[args]

        Subcommands:
          enable: enable the given script and restore its path to the default
          disable: disable the given script
          set <full_path>: set the given script to the given path
          default: print the default path of the given script
          current: print the current path of the given script</full_path></subcommand></power|resume|suspend|shutdown>

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        1 Reply Last reply Reply Quote 0
        • E
          EMWEE
          last edited by

          @johnpoz:

          that is not where you put it..

          [2.2.2-RELEASE][root@pfSense.local.lan]/usr/local/bin: vmware-toolbox-cmd help script
          script: control the scripts run in response to power operations
          Usage: /usr/local/bin/vmware-toolbox-cmd script <power|resume|suspend|shutdown><subcommand>[args]

          Subcommands:
            enable: enable the given script and restore its path to the default
            disable: disable the given script
            set <full_path>: set the given script to the given path
            default: print the default path of the given script
            current: print the current path of the given script</full_path></subcommand></power|resume|suspend|shutdown>

          Running these commands result in a entry in tools.conf, so  its the same thing.

          1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator
            last edited by

            no really no..  Because just editing the file doesn't show up until after its tools have been restarted and it reads tools.conf  If you do this then it makes it active.  And what is the path to your script show if you do current?

            since the default doesn't work

            [2.2.2-RELEASE][root@pfSense.local.lan]/: vmware-toolbox-cmd script power current
            /usr/local/share/vmware-tools/poweron-vm-default

            This not where the script is - the script is here

            [2.2.2-RELEASE][root@pfSense.local.lan]/usr/pbi/open-vm-tools-amd64/local/share/vmware-tools: ls -la
            total 60
            drwxr-xr-x  3 root  wheel  512 Apr 19 07:26 .
            drwxr-xr-x  14 root  wheel  512 Nov 27 16:37 ..
            -r-xr-xr-x  1 root  wheel  4359 Nov 27 16:37 poweroff-vm-default
            -r-xr-xr-x  1 root  wheel  4359 Nov 27 16:37 poweron-vm-default
            -r-xr-xr-x  1 root  wheel  4359 Nov 27 16:37 resume-vm-default
            drwxr-xr-x  3 root  wheel  512 Nov 27 16:37 scripts
            -r-xr-xr-x  1 root  wheel  1473 Nov 27 16:37 statechange.subr
            -r-xr-xr-x  1 root  wheel  4359 Nov 27 16:37 suspend-vm-default
            -rw-r–r--  1 root  wheel    45 Apr 19 07:26 tools.conf
            -r-xr-xr-x  1 root  wheel  7594 Nov 27 16:37 vm-support

            [2.2.2-RELEASE][root@pfSense.local.lan]/usr/pbi/open-vm-tools-amd64/local/share/vmware-tools: vmware-toolbox-cmd script power current
            /usr/pbi/open-vm-tools-amd64/local/share/vmware-tools/poweron-vm-default
            [2.2.2-RELEASE][root@pfSense.local.lan]/usr/pbi/open-vm-tools-amd64/local/share/vmware-tools:

            how did you edit your tools.conf and did you reboot to let the tools load the config?
            [2.2.2-RELEASE][root@pfSense.local.lan]/usr/pbi/open-vm-tools-amd64/local/share/vmware-tools: cat tools.conf
            [powerops]
            poweron-script=/usr/pbi/open-vm-tools-amd64/local/share/vmware-tools/poweron-vm-default

            Also what does your esxi show for which scripts will be run?

            whatdoesesxishow.png_thumb
            whatdoesesxishow.png

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.8, 24.11

            1 Reply Last reply Reply Quote 0
            • S
              Supermule Banned
              last edited by

              This is what I get.

              Not possible to do that via the ESXi GUI apparently….

              esxi-1.PNG
              esxi-1.PNG_thumb
              esxi-2.PNG
              esxi-2.PNG_thumb
              esxi-3.PNG
              esxi-3.PNG_thumb

              1 Reply Last reply Reply Quote 0
              • johnpozJ
                johnpoz LAYER 8 Global Moderator
                last edited by

                well you clearly do not have tools running.

                From pfsense run kldstat

                [2.2.2-RELEASE][root@pfSense.local.lan]/root: kldstat
                Id Refs Address            Size    Name
                1  10 0xffffffff80200000 22d0f80  kernel
                2    1 0xffffffff824d1000 8160    vmblock.ko
                3    1 0xffffffff824da000 13680    vmhgfs.ko
                4    1 0xffffffff824ee000 5630    vmxnet.ko
                5    1 0xffffffff82611000 22f7    vmmemctl.ko

                What does esxi say about the tools?  Oh that it is not installed - here is what it should look like if you have the tools installed openvm package.

                toolsrunning.png
                toolsrunning.png_thumb

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 24.11 | Lab VMs 2.8, 24.11

                1 Reply Last reply Reply Quote 0
                • S
                  Supermule Banned
                  last edited by

                  I uninstalled them and wanted the VmWare one since it gets errors on some .ko files.

                  Installed the package again and getting this…

                  tools_1.PNG
                  tools_1.PNG_thumb
                  tools_2.PNG
                  tools_2.PNG_thumb

                  1 Reply Last reply Reply Quote 0
                  • johnpozJ
                    johnpoz LAYER 8 Global Moderator
                    last edited by

                    your clearly not installing the correct tools.. your just installing the package from package installs right or are you trying to install with pkg install?  Or a file?

                    That error is something wrong - what version of pfsense are you running, and what version of esxi?

                    Im going to do a clean install of 2.2.2 and install the openvm package because you should not be having these problems.

                    edit:  Well I can see why you might be having problems
                    On a clean install of 2.2.2 64bit and trying to install the openvm tools package it just seems to hang on

                    Executing custom_php_install_command()…

                    And yup its still actually downloading _9 vs the package saying its _11, let me give it a bit more time and see if it every finishes, etc.

                    An intelligent man is sometimes forced to be drunk to spend time with his fools
                    If you get confused: Listen to the Music Play
                    Please don't Chat/PM me for help, unless mod related
                    SG-4860 24.11 | Lab VMs 2.8, 24.11

                    1 Reply Last reply Reply Quote 0
                    • S
                      Supermule Banned
                      last edited by

                      pfSense  2.2.2 and ESXi 4.1U3 at test site.

                      I click install on the Open VM package available in the packages menu.

                      1 Reply Last reply Reply Quote 0
                      • johnpozJ
                        johnpoz LAYER 8 Global Moderator
                        last edited by

                        I don't think freebsd 10.1 is supported on esxi 4..  Pretty sure 10.1 was not available until 5.5u2 – did they back port to 4??

                        http://blogs.vmware.com/guestosguide/guest-os/unix-and-others/freebsd

                        An intelligent man is sometimes forced to be drunk to spend time with his fools
                        If you get confused: Listen to the Music Play
                        Please don't Chat/PM me for help, unless mod related
                        SG-4860 24.11 | Lab VMs 2.8, 24.11

                        1 Reply Last reply Reply Quote 0
                        • S
                          Supermule Banned
                          last edited by

                          Its just installed as FreeBSD 64bit. No specific choice of OS.

                          Works fine and runs no issues. I just get the error in the Open Vmtools package.

                          1 Reply Last reply Reply Quote 0
                          • johnpozJ
                            johnpoz LAYER 8 Global Moderator
                            last edited by

                            dude 10.1 is not supported on that version of esxi, it works your lucky..  Run a older version of pfsense if your not going to be current with your esxi version

                            also see this error other than _9 being downloaded vs _11
                            php-fpm[77198]: /pkg_mgr_install.php: Could not open /usr/local/share/vmware-tools/tools.conf for writing

                            If you create the dir and file the pkg installs, shows 3rd party and running in esxi, but the ko's are not loaded when you check kldstat

                            Clearly the package is broken and will have to wait until its fixed.  But again freebsd 10.1 and pfsense 2.2 is not supported on that version of esxi

                            An intelligent man is sometimes forced to be drunk to spend time with his fools
                            If you get confused: Listen to the Music Play
                            Please don't Chat/PM me for help, unless mod related
                            SG-4860 24.11 | Lab VMs 2.8, 24.11

                            1 Reply Last reply Reply Quote 0
                            • S
                              Supermule Banned
                              last edited by

                              2.1.5 vs 2.2.2.

                              Opne Vmtools installed on both  systems. Same version of ESXi. Serving the pfsense clusters.

                              I have attached screendumps.

                              Error began with upgrade to 2.2.2…. 2.1.5 running no issues at all. Open Vm tools shows unmanaged in 2.1.5 and ESXi 4.1U3.

                              2.1.5_dump1.PNG
                              2.1.5_dump1.PNG_thumb
                              2.1.5_dump2.PNG
                              2.1.5_dump2.PNG_thumb
                              2.1.5_dump3.PNG
                              2.1.5_dump3.PNG_thumb
                              2.2.2_dump1.PNG
                              2.2.2_dump1.PNG_thumb
                              2.2.2_dump2.PNG
                              2.2.2_dump2.PNG_thumb

                              1 Reply Last reply Reply Quote 0
                              • D
                                doktornotor Banned
                                last edited by

                                @Supermule:

                                Error began with upgrade to 2.2.2…. 2.1.5 running no issues at all. Open Vm tools shows unmanaged in 2.1.5 and ESXi 4.1U3.

                                Yeah. When you take modules compiled for FreeBSD 8.3 kernel and shove them on FreeBSD 10.1 box, things don't work. Hardly surprising. The errors are damn explicit, cannot believe that totally broken packages are shipped. (Now, at least the breakage resulting from install seems to be mitigated by the fact that it's so badly broken that it actually fails to install altogether, which is a good thing, considering the state of things…  ::))

                                1 Reply Last reply Reply Quote 0
                                • S
                                  Supermule Banned
                                  last edited by

                                  Yes.

                                  But its seems they have corrected the vmxnet.ko file error.

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    doktornotor Banned
                                    last edited by

                                    @Supermule:

                                    But its seems they have corrected the vmxnet.ko file error.

                                    Yeah. By removing the module altogether.

                                    1 Reply Last reply Reply Quote 0
                                    • E
                                      EMWEE
                                      last edited by

                                      Guess ill wait this the package is fixed.

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        Supermule Banned
                                        last edited by

                                        Apparently the driver is present in 10.1 so its not needed in the tools??

                                        @doktornotor:

                                        @Supermule:

                                        But its seems they have corrected the vmxnet.ko file error.

                                        Yeah. By removing the module altogether.

                                        1 Reply Last reply Reply Quote 0
                                        • johnpozJ
                                          johnpoz LAYER 8 Global Moderator
                                          last edited by

                                          freebsd 10.1 has native vmx3 support so you don't need the tools at all really other than to be able to clearly shutdown pfsense from esxi, integration with the console, etc.

                                          I reported that is fully broken in the package thread.. Not sure on who the specific package owner/contributors are - but sure they will fix it up soon enough.

                                          You can run pfsense 2.2.2 just fine on above 5.5u2 of esxi without any issues, and since vmx3 is part of freebsd now you don't really need to install the tools.

                                          An intelligent man is sometimes forced to be drunk to spend time with his fools
                                          If you get confused: Listen to the Music Play
                                          Please don't Chat/PM me for help, unless mod related
                                          SG-4860 24.11 | Lab VMs 2.8, 24.11

                                          1 Reply Last reply Reply Quote 0
                                          • C
                                            cmb
                                            last edited by

                                            Every open issue that existed for open-vm-tools is fixed now.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.