> 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).
Yes those are the tools that I am referring to. Forgive me if I posted
in the wrong area.
We are using the OSP packages (see below) and want to find out what the
technical differences are between those and the RPM that comes on the
disk. I thought I was posting to the right forum that handles the
packaging for VMware.
The ones below seem to not include the vmxnet3 driver, and the modules
don't provide any info when performing (modinfo modulename)
vmware-open-vm-tools-nox-8.0.2-208167.el5
vmware-open-vm-tools-8.0.2-208167.el5
vmware-open-vm-tools-xorg-drv-mouse-12.4.3.0-0.164009.165940.el5
vmware-tools-common-8.0.2-208167.el5
vmware-open-vm-tools-kmod-8.0.2-208167.el5
vmware-open-vm-tools-common-8.0.2-208167.el5
vmware-open-vm-tools-xorg-utilities-8.0.2-208167.el5
vmware-tools-nox-8.0.2-208167.el5
vmware-open-vm-tools-xorg-drv-display-10.15.2.0-0.164009.165940.el5
vmware-tools-8.0.2-208167.el5
> >
> > 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
> >
>
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
open-vm-tools-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-vm-tools-discuss
