Create a new VMWare Appliance from existing one

I use VMware player to run Maemo SDK environment. Recently Maemo released the latest version of its SDK – Diablo. So, I decided to upgrade Chinook VMware Appliance to Diablo. I copied maemo-sdk.vmdk (virtual disk) and maemo-sdk.vmx (definitions) to the new directory, modified title in the definition and run VMware player. But after booting I found that there is no eth0. Just lo.

To solve that problem the file /etc/udev/rules.d/70-persistent-net.rules should be deleted. It contains the virtual MAC address of Ethernet card. After reboot everything should be ok.

VMWare and kernel 2.6.24.X

Last week I upgrade my Fedora Core 8 to the latest stable kernel 2.6.24.3-12. As result the compilation of VMWare module vmmon gave that error:
/tmp/vmware-config1/vmmon-only/./include/compat_wait.h:60: error: conflicting types for ‘poll_initwait’
include/linux/poll.h:65: error: previous declaration of ‘poll_initwait’ was here
/tmp/vmware-config1/vmmon-only/linux/driver.c:172: warning: initialization from incompatible pointer type
/tmp/vmware-config1/vmmon-only/linux/driver.c:176: warning: initialization from incompatible pointer type
make[2]: *** [/tmp/vmware-config1/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config1/vmmon-only] Error 2
make[1]: Leaving directory /usr/src/kernels/2.6.24.3-12.fc8-i686'
make: *** [vmmon.ko] Error 2
make: Leaving directory
/tmp/vmware-config1/vmmon-only'
Unable to build the vmmon module.

Solution is to use vmware-any-any-update116.
In my case I manually copied patched vmmon.tar, vmblock.tar and vmnet.tar to the /usr/lib/vmware/modules/source because script from vmware-any-any-update116 crashed by some reason.