I get this error during "vmware-config-tools.pl" near the end, just after the phase of probing X server.
Vmware Workstation is version 10.0.0.2
Host is Debian Wheezy amd64 (kernel 3.13.6, nvidia proprietary drivers), Guest is Debian Squeeze i386 (kernel 3.13.6).
X server seems ok, I see
[code]
Detected X server version 1.7.7
Restarting Hardware abstraction layer: hald.
X is running fine with the new config file.
[/code]
But then:
[code]
Creating a new initrd boot image for the kernel.
Can't exec "-u": No such file or directory at /usr/bin/vmware-config-tools.pl line 6743.
ERROR: " -u -k 3.13.6-g" exited with non-zero status.
Your system currently may not have a functioning init image and may not boot
properly. DO NOT REBOOT! Please ensure that you have enough free space
available in your /boot directory and run this configuration script again.
Execution aborted.
[/code]
I don't understand this error. That guest OS has no initrd, there is lilo that loads directly the kernel.
Why does it try to create an initrd boot image? Who asked for it?
I have to say that, despite this error, X is able to start and the mouse can move between guest and host.
If I give "/etc/init.d/vmware-tools start" it says that vmware tools are installed but are not (correctly) configured
for the current kernel.
If I uninstall vmware-tools, instead, X refuses to start.
Before upgrading the machine from Lenny to Squeeze (the kernel is the same) vmware tools were able to start.
