Copying the utsrelease.h for me didn't have any effect also, but the problem can be easily solved by fooling vmware-config-tools.pl into thinking that the path you typed is correct anyway. In order to do so, open the /usr/bin/vmware-config-tools.pl and search for getValidKernelHeadersPath , under that you will see a while(1) { ......
just remove the while(1) keyword without removing the brackets. Afterward your file should look something like this :
....
sub getValidKernelHeadersPath {
my $kh_path = shift;
my $modconfig = shift;
my $appLoaderArgs = shift;
my $answer;
my $query;
my $default;
{
if (system("$modconfig --validate-kernel-headers \"$kh_path\" " .
"$appLoaderArgs >/dev/null 2>&1") == 0) {
$query = "The path \"$kh_path\" appears to be a valid path to the " .
"kernel headers of the running kernel.";
$default = 'no';
} else { .......
.....
you can now save and manually run vmware-config-tools.pl and when asked for kernel headers select yes for changing and give the correct path (in my system /usr/src/kernels/2.6.33.5-124.fc13.i686/include/), it will then compile correctly.
just remove the while(1) keyword without removing the brackets. Afterward your file should look something like this :
....
sub getValidKernelHeadersPath {
my $kh_path = shift;
my $modconfig = shift;
my $appLoaderArgs = shift;
my $answer;
my $query;
my $default;
{
if (system("$modconfig --validate-kernel-headers \"$kh_path\" " .
"$appLoaderArgs >/dev/null 2>&1") == 0) {
$query = "The path \"$kh_path\" appears to be a valid path to the " .
"kernel headers of the running kernel.";
$default = 'no';
} else { .......
.....
you can now save and manually run vmware-config-tools.pl and when asked for kernel headers select yes for changing and give the correct path (in my system /usr/src/kernels/2.6.33.5-124.fc13.i686/include/), it will then compile correctly.
Worked for me!
Detected X.org version 7.7.0.
ReplyDeleteNo drivers for X.org version: 7.7.0.
Skipping X configuration because X drivers are not included.
Creating a new initrd boot image for the kernel.
Checking acpi hot plug [ OK ]
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: [ OK ]
Paravirtual SCSI module: [FAILED]
Guest filesystem driver: [FAILED]
Mounting HGFS shares: [FAILED]
Guest memory manager: [FAILED]
Guest vmxnet fast network device: [FAILED]
VM communication interface: [FAILED]
VM communication interface socket family: [FAILED]
Blocking file system: [FAILED]
File system sync driver: [FAILED]
Guest operating system daemon: [ OK ]
Virtual Printing daemon: [ OK ]
Unable to start services for VMware Tools
Execution aborted.
[root@yingying vmware-tools-distrib]#
It fooled vmware but it did not compile right.
ReplyDelete