2008/11/21 Roger Searle <[EMAIL PROTECTED]>:
That and vmware-server
not working with the current kernel is a show stopper with intrepid for me.
Cheers,
Roger
Then Kerry said:
I have vmware server working under intrepid, both server and desktop.
What issues are you having?
An installation goes well until, in vmware-config.pl, the build of the
vsock module as per the output from my machine below. The message about
gcc, binutils, kernel headers, is not correct, they are installed. This
link is typical of those I have seen, no solutions found so far.
http://ph.ubuntuforums.com/showthread.php?p=6161702
While a machine will start and run, it is slow and I can't actually
interact with it.
None of the pre-built vsock modules for VMware Server is suitable for your
running kernel. Do you want this program to try to build the vsock
module for
your system (you need to have a C compiler installed on your system)? [yes]
Extracting the sources of the vsock module.
Building the vsock module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vsock-only'
make -C /lib/modules/2.6.27-7-generic/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.27-7-generic'
CC [M] /tmp/vmware-config0/vsock-only/linux/af_vsock.o
CC [M] /tmp/vmware-config0/vsock-only/linux/driverLog.o
CC [M] /tmp/vmware-config0/vsock-only/linux/util.o
/tmp/vmware-config0/vsock-only/linux/util.c: In function ‘VSockVmciLogPkt’:
/tmp/vmware-config0/vsock-only/linux/util.c:157: warning: format not a
string literal and no format arguments
CC [M] /tmp/vmware-config0/vsock-only/linux/vsockAddr.o
LD [M] /tmp/vmware-config0/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "VMCIDatagram_CreateHnd"
[/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd"
[/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_GetContextID" [/tmp/vmware-config0/vsock-only/vsock.ko]
undefined!
WARNING: "VMCIDatagram_Send" [/tmp/vmware-config0/vsock-only/vsock.ko]
undefined!
CC /tmp/vmware-config0/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-config0/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.27-7-generic'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-config0/vsock-only'
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config0/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.
[ Press the Enter key to continue.]
