I'm running Vmware ESX 4.1 and I have a development VM that I recently upgraded from Ubuntu 10.04 to 11.04. Then I tried to re-install VMware Tools and some of the modules gave me an error and would not compile. As a result I'm having problems with backing up this virtual machine now and I suspect VMware tools is the reason. I installed latest patches for VMware host, that included an update to VMware Tools (v8.3.7 build-381511) but I'm still getting the same error.
The error I'm getting is like this:
...
/tmp/vmware-root/modules/vmhgfs-only/super.c:73:4: error: unknown field \u2018clear_inode\u2019 specified in initializer
make[2]: *** [/tmp/vmware-root/modules/vmhgfs-only/super.o] Error 1
make[1]: *** [_module_/tmp/vmware-root/modules/vmhgfs-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.38-8-generic'
make: *** [vmhgfs.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only'
and also this:
/tmp/vmware-root/modules/vmci-only/vmci_drv.c:91:4: error: unknown field \u2018ioctl\u2019 specified in initializer
/tmp/vmware-root/modules/vmci-only/vmci_drv.c:91:4: warning: initialization from incompatible pointer type
/tmp/vmware-root/modules/vmci-only/vmci_drv.c: In function \u2018vmci_init\u2019:
/tmp/vmware-root/modules/vmci-only/vmci_drv.c:151:4: error: implicit declaration of function \u2018init_MUTEX\u2019
make[2]: *** [/tmp/vmware-root/modules/vmci-only/vmci_drv.o] Error 1
make[1]: *** [_module_/tmp/vmware-root/modules/vmci-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.38-8-generic'
make: *** [vmci.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Any ideas?
My guess would be that you have the wrong version of the kernel headers. Unless you need some specific feature that is only available in the version of vmware tools you are trying to build (hint: You probably don't) you can save yourself a lot of pain by removing the hand-installed version and use the open-vm-tools package in ubuntu:
It is also possible to pull the latest version of the tools directly from vmware, but then you need to mess a little with apt:
It seems that after migration of our VMware ESXi servers to version 5.0 this problem goes away. Apparently, it was a problem with VMware tools that was eventually fixed by VMware.
Prior to this we were running VMware tools from Ubuntu repository as per @pehrs suggestion and they were working okay with exception that they were shown as "Unmanaged" in VMware vCenter and they cannot be upgraded from VMware vCenter console if new version is available. Instead, someone would need to login to the Ubuntu machine as root and check for updates. It was a working short term solution though.