Ah. I see what I did. I inadvertently installed both the open-vm-tools and vmware packages. The page at https://help.ubuntu.com/community/VMware/Tools gives both instructions and I missed the "do one or the other". Sorry 'bout that.
Is there any difference between the open version vs. the vmware versions? I've noticed occasional client networking drop outs ... On Mar 7, 2011, at 9:17 AM, Dmitry Torokhov wrote: > Hi Steven, > > On Friday, March 04, 2011 08:11:16 pm Steven Parkes wrote: >> I suspect this is actually an issue for vmware since this code is not >> actually in the open-vm-tools tar balls, but the vmware_load_module in >> functions doesn't handle the case where a module is in update/dkms >> instead of misc. The trivial fix is to have it check update/dkms before >> misc. Otherwise, vsock may not be loaded (at least for me, under >> Maverick with the latest package from vmware). >> > > I do not believe that our non-open-vm-tools install anything in > update/dkms, so that is the reason for vmware_load_module() not to look > there. > > Could you please describe your issue in more detail? What version of tools > are you installing? Are you using the tar installer or the deb packages > that we produce? > > Thanks, > Dmitry ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ open-vm-tools-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/open-vm-tools-discuss
