Adar and all,
I am wondering if this statement below is still true.
We have a slew of CentOS and Ubuntu servers and have a team disagreement
between which tool set is better or supported should we call up VMWare
for support. Whenever there is a linux "issue" my team mates uninstall
the open tools and install the VMWare-tools from the website, then
reboot the server.
The rebooting of the server could erase any kind of issues that we have
on the servers as it is and that is my point.
I guess a main cause of concern is that is the fact that it says
"Unmanaged" inside of VSphere.
The biggest issue so far is that we want to partake on is using the new
vmxnet3 driver for networking, however I want to make our life a little
easier by using the open-vm-tools. I have not seen any issues besides
the start up script in Ubuntu saying that they "failed" when actually
the modules are loaded.
We are running 4.0u1 for the vsphere
>1) The ESX 3.5 Tools contain a few components that haven't been
open-sourced,
>namely the vmdesched module and the Tools auto-upgrader. The former is
>experimental and generally useless to 99.9% of customers, and the latter isn't
>useful in the open-vm-tools, so it's unlikely that you'll care about these.
>2) The ESX 3.5 Tools, as far as I know, don't have a Debian package. So your
>installation experience will likely be less pleasant than if you used the
>open-vm-tools Debian package.
>3) The ESX 3.5 Tools are, at this point in time, quite a bit older than the
>open-vm-tools. The open-vm-tools code base reflects our top-of-tree, usually
>off by a month at most. The ESX 3.5 Tools branched from the top-of-tree almost
>two years ago.
>4) The ESX 3.5 Tools are supported by VMware when used in conjunction with ESX
>3.5 hosts. If it's important to you to get quick support from VMware's support
>organization, you have no choice but to use the ESX 3.5 Tools. The level of
>support you'll get from the open-vm-tools is going to be "best-effort",
>meaning, whomever responds to e-mails like these, bug reports on Sourceforge,
>and bug reports in the Debian package
Please be advised that this email may contain confidential information.
If you are not the intended recipient, please do not read, copy or
re-transmit this email. If you have received this email in error,
please notify us by email by replying to the sender and by telephone
(call us collect at +1 202-828-0850) and delete this message and any
attachments. Thank you in advance for your cooperation and assistance.
In addition, Danaher and its subsidiaries disclaim that the content of
this email constitutes an offer to enter into, or the acceptance of,
any
contract or agreement or any amendment thereto; provided that the
foregoing disclaimer does not invalidate the binding effect of any
digital or other electronic reproduction of a manual signature that is
included in any attachment to this email.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
open-vm-tools-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/open-vm-tools-discuss
