Tengo un lenny 686 con vmware server 2.0.1 instalado, y no termina de ir del todo fino, amén de que no funcionan algunas cosillas. Al realizar la instalación preparé todo siguiendo las instrucciones del proveedor del software y funcionó casi todo bien salvo la inserción de un módulo llamado vsock. Pongo la salida lo último, porque si no alguien leerá y pensará que no he hecho todo lo obvio: googlear, reinstalar, probar soluciones que han funcionado en otras versiones, etc...
Todo lo necesario para que funcione está, por lo que yo he podido comprobar, instalado, y las versiones de gcc y g++ son congruentes con las cabeceras del núcleo.
¿A nadie más le sale esto al instalar?
Extracting the sources of the vsock module.
Building the vsock module.
Using 2.6.x kernel build system. make: se ingresa al directorio `/tmp/vmware-config0/vsock-only' make -C /lib/modules/2.6.26-2-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: se ingresa al directorio `/usr/src/linux-headers-2.6.26-2-686' 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 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]: se sale del directorio `/usr/src/linux-headers-2.6.26-2-686' cp -f vsock.ko ./../vsock.o make: se sale del directorio `/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.
¿Alguien lo ha conseguido solucionar sin tener que recompilar nucleo?
Hola a tod@s
Tengo un lenny 686 con vmware server 2.0.1 instalado, y no termina de ir del todo fino, amén de que no funcionan algunas cosillas. Al realizar la instalación preparé todo siguiendo las instrucciones del proveedor del software y funcionó casi todo bien salvo la inserción de un módulo llamado vsock. Pongo la salida lo último, porque si no alguien leerá y pensará que no he hecho todo lo obvio: googlear, reinstalar, probar soluciones que han funcionado en otras versiones, etc...
Todo lo necesario para que funcione está, por lo que yo he podido comprobar, instalado, y las versiones de gcc y g++ son congruentes con las cabeceras del núcleo.
¿A nadie más le sale esto al instalar?
Extracting the sources of the vsock module.Building the vsock module.
Using 2.6.x kernel build system.
make: se ingresa al directorio `/tmp/vmware-config0/vsock-only'
make -C /lib/modules/2.6.26-2-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: se ingresa al directorio `/usr/src/linux-headers-2.6.26-2-686'
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
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]: se sale del directorio `/usr/src/linux-headers-2.6.26-2-686'
cp -f vsock.ko ./../vsock.o
make: se sale del directorio `/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.
¿Alguien lo ha conseguido solucionar sin tener que recompilar nucleo?
Saludos y gracias