The Appliance and VM-Tools shows out of date!
-
We just updated our ESX environment with the latest patches and it shows the pfsense appliances with out of date tools status.
I know that the open tools is a different animal with its generic memory support etc. Is this something i should be concerned about? Is anyone else seeing this. I have about 22 of these firewall appliance VM's running. Most of them are 1.2.2 an a few are 123. All of them working flawlessly.
Thanks,
Pat -
Times are allways slipping on the VM's…..Setup the internal NTP server, and make it the reference for the VM's.
-
Thanks for the reply but I don't mean that their dates are off, the VMtools Status shows "OUT OF DATE" meaning that VMware and the vmtools are out of sync or at least they think that they are!
Thanks,
Pat -
It probably just means that since VMware has been updated, a new version of the tools package needs to be made from the tools with the new version of VMware. I'm not sure how much trouble a mismatch might cause, but some people run just fine without the tools installed at all.
-
Thanks for the Reply, Yes I know that the tools are still working but I was just wanting to know if it was because VMware made a big change causing the tools to show out of date. In the past I've had several updates within vmware with not change in the tools status. I'm guessing that vmware made a change big enough to trigger a status change in the tools reporting component. I can just wait until there is an updated Opentools package.
Pat -
They did, the VMware workstation update I had a week or so ago included a new version of the tools for at least Windows, and probably others.
-
How do we tell if someone is working on an update? Is someone?
Since my move to ESXi 4.1, my once perfectly operating pfSense 1.2.3 is now running 100% cpu in the performance monitor, but is 99% idel in the OS while runnign top.
-
I'm fairly certain someone updated the VMware tools package within the last couple weeks. Have you tried reinstalling the package recently?
-
The problem with building in the latest version of vmware tools if if someone wants to load it on a system which is running an older virtual environment can produce problems in and of itself. It would be better if they are slightly dated for compatibility. That being said the ideal would be someway of loading the correct version without the need for all of the extra perl libraries, make, ect which are required to install the "current" version of vmware tools for your given instance. For me, I also run a couple of freebsd servers running as vm's and one of them has all of the extra components available to compile from source the current version, once the binary form is created then pull it down and manually configuring on the other systems….again kind of a work-around but it does keep everything current.
Realistically you won't notice much of a difference if at all between the minor build changes in vmware tools, major version changes I would suspect a bit but the minor changes I wouldn't loose sleep over.
-
Also, doesn't the appliance use the Open Source version of the VMWare tools, not the VMWare released ones.
If so, and memory serves me correct, they always show as "out of date".
Cheers.
