VMware tools still not working on newest 2.2.3, can't gracefully shutdown
-
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?
-
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 :)
-
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 ;)
-
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.
-
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.
-
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. -
Hve you tested your backups and if ther are working in case of failure?
-
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?
-
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.
-
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.
