Update:
I uninstalled the Vmware Server x86-64 rpm; find & deleted all the vmware folders; reinstalled the rpm + the vmkernel module (tools) and dazuko (previously a depend warning/error)
dazuko didn’t make any diff; still got the warning
rpm installed
/usr/bin/vmware-config.pl would not run saying I already had 5 modules installed
had to remove vmkernel module (tools) to get it to run.
Then, during vmware-config.pl I got:
make: Leaving directory `/tmp/vmware-config2/vsock-only’
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting ‘/tmp/vmware-config2/vsock.o’: -1 Unknown symbol in module
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.
The VM communication interface socket family is used in conjunction with the VM
communication interface to provide a new communication path among guests and
host. The rest of this software provided by VMware Server is designed to work
independently of this feature. If you wish to have the VSOCK feature you can
install the driver by running vmware-config.pl again after making sure that
gcc, binutils, make and the kernel sources for your running kernel are
installed on your machine. These packages are available on your distribution’s
installation CD.
After spinning my wheels over that, I found a patch:
--- /usr/bin/vmware-config.pl.orig 2008-11-28 12:06:35.641054086 +0100
+++ /usr/bin/vmware-config.pl 2008-11-28 12:30:38.593304082 +0100
@@ -4121,6 +4121,11 @@
return 'no';
}
+ if ($name eq 'vsock') {
+ print wrap("VMWare config patch VSOCK!
");
+ system(shell_string($gHelper{'mv'}) . ' -vi ' . shell_string($build_dir . '/../Module.symvers') . ' ' . shell_string($build_dir . '/vsock-only/' ));
+ }
+
print wrap('Building the ' . $name . ' module.' . "
", 0);
if (system(shell_string($gHelper{'make'}) . ' -C '
. shell_string($build_dir . '/' . $name . '-only')
@@ -4143,6 +4148,10 @@
if (try_module($name, $build_dir . '/' . $name . '.o', 0, 1)) {
print wrap('The ' . $name . ' module loads perfectly into the running kernel.'
. "
", 0);
+ if ($name eq 'vmci') {
+ print wrap("VMWare config patch VMCI!
");
+ system(shell_string($gHelper{'cp'}) . ' -vi ' . shell_string($build_dir.'/vmci-only/Module.symvers') . ' ' . shell_string($build_dir . '/../'));
+ }
remove_tmp_dir($build_dir);
return 'yes';
}
saved as vmware-config.pl.patch.txt
patched with:
sudo patch /usr/bin/vmware-config.pl /path/to/vmware-config.pl.patch.txt
Now /usr/bin/vmware-config.pl runs to completion & success with no errors.
BTW, I guess that “Unable to make a vsock module” is why it was running so slow @ my 1st install.
I 'm still climbing the learning curve – even with John’s guide
Anyhow, I’m ready to press on:)
