O que esse erro do wmware worstation?

Iniciado por maquiavelho, 19 de Julho de 2008, 22:33

tópico anterior - próximo tópico

maquiavelho

Using 2.6.x kernel build system.
make: Entrando no diretório `/tmp/vmware-config0/vmmon-only'
make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entrando no diretório `/usr/src/linux-2.6.25-omni'
CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:25,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:48:
/tmp/vmware-config0/vmmon-only/./include/vm_basic_types.h:170: erro: conflicting types for 'uintptr_t'
include/linux/types.h:40: erro: previous declaration of 'uintptr_t' was here
No arquivo incluído de /tmp/vmware-config0/vmmon-only/./include/x86.h:23,
de /tmp/vmware-config0/vmmon-only/linux/driver.h:15,
de /tmp/vmware-config0/vmmon-only/linux/driver.c:49:
/tmp/vmware-config0/vmmon-only/./include/x86cpuid.h:381:1: aviso: "BIT_MASK" redefinido
No arquivo incluído de include/linux/kernel.h:15,
de /tmp/vmware-config0/vmmon-only/linux/driver.c:11:
include/linux/bitops.h:7:1: aviso: esta é a localização da definição prévia
No arquivo incluído de /tmp/vmware-config0/vmmon-only/./include/vmci_kernel_defs.h:26,
de /tmp/vmware-config0/vmmon-only/./common/vmciContext.h:19,
de /tmp/vmware-config0/vmmon-only/linux/driver.h:21,
de /tmp/vmware-config0/vmmon-only/linux/driver.c:49:
/tmp/vmware-config0/vmmon-only/./include/compat_wait.h:37:5: aviso: "VMW_HAVE_EPOLL" não éstá definido
/tmp/vmware-config0/vmmon-only/./include/compat_wait.h:43:5: aviso: "VMW_HAVE_EPOLL" não éstá definido
In file included from /tmp/vmware-config0/vmmon-only/./include/vmci_kernel_defs.h:26,
from /tmp/vmware-config0/vmmon-only/./common/vmciContext.h:19,
from /tmp/vmware-config0/vmmon-only/linux/driver.h:21,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:49:
/tmp/vmware-config0/vmmon-only/./include/compat_wait.h:60: erro: conflicting types for 'poll_initwait'
include/linux/poll.h:65: erro: previous declaration of 'poll_initwait' was here
/tmp/vmware-config0/vmmon-only/linux/driver.c:150: aviso: initialization from incompatible pointer type
/tmp/vmware-config0/vmmon-only/linux/driver.c: Na função 'LinuxDriver_Ioctl':
/tmp/vmware-config0/vmmon-only/linux/driver.c:1715: erro: 'struct mm_struct' has no member named 'dumpable'
make[2]: ** [/tmp/vmware-config0/vmmon-only/linux/driver.o] Erro 1
make[1]: ** [_module_/tmp/vmware-config0/vmmon-only] Erro 2
make[1]: Saindo do diretório `/usr/src/linux-2.6.25-omni'
make: ** [vmmon.ko] Erro 2
make: Saindo do diretório `/tmp/vmware-config0/vmmon-only'
Unable to build the vmmon module.

For more information on how to troubleshoot module-related problems, please
visit our Web site at "http://www.vmware.com/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.

O meu kernel é esse 2.6.25 do omnislash.

Obrigado.

Polaco

O problema é o que sempre acontece com o vmware, seu kernel é novo demais e instalador não o reconhece na hora de compilar os módulos.

Recentemente foi adicionado ao patch any-any-update o suporte ao kernel 2.6.25, é só baixar a nova versão e rodar que a compilação do módulo ocorrerá sem problemas, a menos que o kernel omnislash não seja compatível.

http://groups.google.com/group/vmkernelnewbies/files

Baixe e instale a versão 117, não posso confirmar mas li que ela suporta também o 2.6.26.
Ubuntu 10.04 x64 @ Dell Optiplex 740

maquiavelho

Não adiantou. Mesmo asssim obrigado.

Using 2.6.x kernel build system.
make: Entrando no diretório `/tmp/vmware-config1/vmmon-only'
make -C /usr/src/linux/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entrando no diretório `/usr/src/linux-2.6.25-omni'
  CC [M]  /tmp/vmware-config1/vmmon-only/linux/driver.o
  CC [M]  /tmp/vmware-config1/vmmon-only/linux/hostif.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/comport.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/cpuid.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/hash.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/memtrack.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/phystrack.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/task.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/vmciContext.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/vmciDatagram.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/vmciDriver.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/vmciDs.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/vmciGroup.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/vmciHashtable.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/vmciProcess.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/vmciResource.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/vmciSharedMem.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/vmx86.o
  CC [M]  /tmp/vmware-config1/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/vmware-config1/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: "init_mm" [/tmp/vmware-config1/vmmon-only/vmmon.ko] undefined!
  CC      /tmp/vmware-config1/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/vmware-config1/vmmon-only/vmmon.ko
make[1]: Saindo do diretório `/usr/src/linux-2.6.25-omni'
cp -f vmmon.ko ./../vmmon.o
make: Saindo do diretório `/tmp/vmware-config1/vmmon-only'
Unable to make a vmmon module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config1/vmmon.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.

For more information on how to troubleshoot module-related problems, please
visit our Web site at "http://www.vmware.com/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.

Polaco

Aparentemente o problema é com o kernel omnislash mesmo, pelo o que eu entendi da mensagem de erro, o instalador está reclamando que os arquivos de cabeçalho (header files) estão levemente diferentes do que o kernel precisa, e o módulo não pode ser inserido.

Nunca trabalhei com o kernel omnislash, mas você teria como instalar o pacote kernel-headers específico dele? acredito que apenas instalando esse pacote a instalação ocorrerá normalmente.
Ubuntu 10.04 x64 @ Dell Optiplex 740