On Wednesday 24 February 2010 11:40:33 am Joel Webb wrote:
> On Wed, 2010-02-24 at 11:14 -0800, Dmitry Torokhov wrote:
> Hi Joel,
> 
> On Tuesday 23 February 2010 01:01:00 pm Joel Webb wrote:
> > 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.
> 
> If you are calling our official support line you need to have installed
>  VMware tools that came with the product. This is the only combination that
>  is officially supported.
> 
> open-vm-tools, at the moment, is a developer preview of the tools software.
> While we strive to maintain high quality of our software there is limited
> amount of testing done on the branch where open-vm-tools are coming from.
>
> Dmitry, thanks for the response.
> 
> The problem is since we maintain several hundred servers, we don't want to
>  have to re-compile or even run the vmware-check-tools program to
>  reconfigure them for each machine.
> 
> We want to have the tools maintained by the vmware community using your own
>  repository using the OSP documentation. Even if we could have the
>  VMWare-tools in that repository, that would be fine.

You might be interested in OSP packages provided by VMware that should 
eliminate the need for running many scripts manually:

        http://www.vmware.com/download/packages.html

These are fully supported (the same level of support as for the tools coming 
directly with the product) and should not require recompiling, just rerunning 
vmwate-config-tools script so that prebuilt kernel modules will be installed 
into proper directory. We expect distributions to maintain certain level of 
compatibility within release and exiting modules to continue working.

Please note that these packages are not the same as open-vm-tools hosted on 
SourceForge or distributed by OpenSUSE or Ubuntu, although their names are 
quite similar (due to unfortunate naming decision). 

> 
> But I found several reasons also to use the open-vm-tool repositories
>  rather than the Supported version.
> 
> 1. Namely ease for the administrator.
> 2. Tested against the distribution packager.
> 3. Not having to compile every-time there is a kernel update.
> 
> http://communities.vmware.com/message/1183616#1183616
> 
> http://communities.vmware.com/message/1091031#1091031
> 
> http://www.mail-archive.com/open-vm-tools-discuss@lists.sourceforge.net/msg
> 00003.html

Yes, we are working towards separating tools from platform releases however 
the work has not been completed yet.

> 
> Our company is paying for the highest support as it is now. Does that mean
>  I would have to uninstall open-vm-tools and then install VMWare-Tools just
>  so I can get support for the issue I am having?

Yes. VMware is currently unable to provide support for tools built from the 
SourceForge repository by either end users or distributions. You are of course 
welcome to ask the questions on this mailing list and we will try to resolve 
them on a best effort basis.

> 
> >  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
> 
> Are you having trouble with vmxnet3 shipped with the product?
>
> No, that works fine, but doing some research, it looks like the vmxnet3
>  toolset isn't included with the open-vm-tools version.
> 
> Thanks,
> 
> Dmitry
> 

------------------------------------------------------------------------------
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
open-vm-tools-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-vm-tools-discuss

Reply via email to