On 06/05/2010 01:06, Joshua Daniel Franklin wrote: > Is it worth using open-vm-tools 2010.02.23 on lucid?
Yes it is worth it. I don't know what went wrong at your side, but here last night's kernel update worked fine and triggered building of all the right modules, which also actually worked. I have to admit that I did not actually used the vmxnet module that you're referring to, but vmxnet3. However, vmxnet /was/ generated by dkms, and I can manually load that module without problems. This Ubuntu LTS is the first one that out-of-the-box provides a compatible combination of kernel, linux-headers, and open-vm-tools, which is achieved trough the dkms mechanism. You will have up-to-date kernels, with working vmware modules, without manual fiddling/intervention. So Lucid will stick with 2.6.32 and 2010.02.23-236320, which will keep working even through ABI bumps such as last night's 2.6.32-21 -> 2.6.32-22. I just updated https://confluence.terena.org/display/~visser/open-vm-tools+in+Ubuntu+Lucid with ESX4 info and some pics. BTW, I see that you're using the 'generic-pae' kernel flavor, but since you're on a VM anyway, you might as well use the slimmer 'virtual' flavor. Saves tons of hardware modules that you will never use. Dick
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------
_______________________________________________ open-vm-tools-discuss mailing list open-vm-tools-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-vm-tools-discuss
