On Thu, May 6, 2010 at 2:26 AM, Dick Visser wrote: > On 06/05/2010 01:06, Joshua Daniel Franklin wrote: > > 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.
Yeah, I still have to support ESXi 3.5 which doesn't have vmxnet3. Strangely, I found that after rebooting vmxnet works fine again. I'm rebuilding via kickstart right now to see if I can reproduce that. > 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. In theory! This is definitely my hope. > 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. Yeah, I had trouble but now see this bug: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/509865 I guess you did too based on your inclusion of linux-headers-virtual in your page! ------------------------------------------------------------------------------ _______________________________________________ open-vm-tools-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/open-vm-tools-discuss
