Antes de executar o VMware, vários módulos devem ser compilados

0

Estou tentando executar o VMware no kali linux, mas quando tento executá-lo, mostro a mensagem que Before you can run VMware several modules must be compiled and loaded into the running kernel

Aqui está o log:

2018-04-23T20:11:48.254+04:30| vthread-1| I125: Log for VMware Workstation pid=8508 version=14.1.0 build=build-7370693 option=Release
2018-04-23T20:11:48.254+04:30| vthread-1| I125: The process is 64-bit.
2018-04-23T20:11:48.254+04:30| vthread-1| I125: Host codepage=UTF-8 encoding=UTF-8
2018-04-23T20:11:48.254+04:30| vthread-1| I125: Host is Linux 4.15.0-2-amd64 Kali GNU/Linux Rolling
2018-04-23T20:11:48.254+04:30| vthread-1| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2018-04-23T20:11:48.254+04:30| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2018-04-23T20:11:48.254+04:30| vthread-1| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2018-04-23T20:11:48.254+04:30| vthread-1| I125: DictionaryLoad: Cannot open file "/home/linux/.vmware/config": No such file or directory.
2018-04-23T20:11:48.254+04:30| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/linux/.vmware/config": No such file or directory.
2018-04-23T20:11:48.254+04:30| vthread-1| I125: PREF Optional preferences file not found at /home/linux/.vmware/config. Using default values.
2018-04-23T20:11:48.254+04:30| vthread-1| I125: DictionaryLoad: Cannot open file "/home/linux/.vmware/preferences": No such file or directory.
2018-04-23T20:11:48.254+04:30| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/linux/.vmware/preferences": No such file or directory.
2018-04-23T20:11:48.254+04:30| vthread-1| I125: PREF Optional preferences file not found at /home/linux/.vmware/preferences. Using default values.
2018-04-23T20:11:48.326+04:30| vthread-1| W115: Logging to /tmp/vmware-root/vmware-8508.log
2018-04-23T20:11:48.340+04:30| vthread-1| I125: Obtaining info using the running kernel.
2018-04-23T20:11:48.340+04:30| vthread-1| I125: Created new pathsHash.
2018-04-23T20:11:48.340+04:30| vthread-1| I125: Setting header path for 4.15.0-2-amd64 to "/lib/modules/4.15.0-2-amd64/build/include".
2018-04-23T20:11:48.340+04:30| vthread-1| I125: Validating path "/lib/modules/4.15.0-2-amd64/build/include" for kernel release "4.15.0-2-amd64".
2018-04-23T20:11:48.340+04:30| vthread-1| I125: Failed to find /lib/modules/4.15.0-2-amd64/build/include/linux/version.h
2018-04-23T20:11:48.340+04:30| vthread-1| I125: /lib/modules/4.15.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2018-04-23T20:11:48.340+04:30| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check
2018-04-23T20:11:48.348+04:30| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.0-2-amd64".
2018-04-23T20:11:48.348+04:30| vthread-1| I125: The header path "/lib/modules/4.15.0-2-amd64/build/include" for the kernel "4.15.0-2-amd64" is valid.  Whoohoo!
2018-04-23T20:11:48.571+04:30| vthread-1| I125: found symbol version file /lib/modules/4.15.0-2-amd64/build/Module.symvers
2018-04-23T20:11:48.571+04:30| vthread-1| I125: Reading symbol versions from /lib/modules/4.15.0-2-amd64/build/Module.symvers.
2018-04-23T20:11:48.597+04:30| vthread-1| I125: Read 20056 symbol versions
2018-04-23T20:11:48.597+04:30| vthread-1| I125: Reading in info for the vmmon module.
2018-04-23T20:11:48.597+04:30| vthread-1| I125: Reading in info for the vmnet module.
2018-04-23T20:11:48.597+04:30| vthread-1| I125: Reading in info for the vmblock module.
2018-04-23T20:11:48.597+04:30| vthread-1| I125: Reading in info for the vmci module.
2018-04-23T20:11:48.597+04:30| vthread-1| I125: Reading in info for the vsock module.
2018-04-23T20:11:48.597+04:30| vthread-1| I125: Setting vsock to depend on vmci.
2018-04-23T20:11:48.597+04:30| vthread-1| I125: Invoking modinfo on "vmmon".
2018-04-23T20:11:48.600+04:30| vthread-1| I125: "/sbin/modinfo" exited with status 256.
2018-04-23T20:11:48.600+04:30| vthread-1| I125: Invoking modinfo on "vmnet".
2018-04-23T20:11:48.602+04:30| vthread-1| I125: "/sbin/modinfo" exited with status 256.
2018-04-23T20:11:48.602+04:30| vthread-1| I125: Invoking modinfo on "vmblock".
2018-04-23T20:11:48.604+04:30| vthread-1| I125: "/sbin/modinfo" exited with status 256.
2018-04-23T20:11:48.604+04:30| vthread-1| I125: Invoking modinfo on "vmci".
2018-04-23T20:11:48.606+04:30| vthread-1| I125: "/sbin/modinfo" exited with status 256.
2018-04-23T20:11:48.606+04:30| vthread-1| I125: Invoking modinfo on "vsock".
2018-04-23T20:11:48.608+04:30| vthread-1| I125: "/sbin/modinfo" exited with status 0.
2018-04-23T20:11:48.623+04:30| vthread-1| I125: to be installed: vmmon status: 0
2018-04-23T20:11:48.623+04:30| vthread-1| I125: to be installed: vmnet status: 0
2018-04-23T20:11:48.639+04:30| vthread-1| I125: Obtaining info using the running kernel.
2018-04-23T20:11:48.639+04:30| vthread-1| I125: Setting header path for 4.15.0-2-amd64 to "/lib/modules/4.15.0-2-amd64/build/include".
2018-04-23T20:11:48.639+04:30| vthread-1| I125: Validating path "/lib/modules/4.15.0-2-amd64/build/include" for kernel release "4.15.0-2-amd64".
2018-04-23T20:11:48.639+04:30| vthread-1| I125: Failed to find /lib/modules/4.15.0-2-amd64/build/include/linux/version.h
2018-04-23T20:11:48.639+04:30| vthread-1| I125: /lib/modules/4.15.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2018-04-23T20:11:48.639+04:30| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check
2018-04-23T20:11:48.646+04:30| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.0-2-amd64".
2018-04-23T20:11:48.646+04:30| vthread-1| I125: The header path "/lib/modules/4.15.0-2-amd64/build/include" for the kernel "4.15.0-2-amd64" is valid.  Whoohoo!
2018-04-23T20:11:48.867+04:30| vthread-1| I125: found symbol version file /lib/modules/4.15.0-2-amd64/build/Module.symvers
2018-04-23T20:11:48.867+04:30| vthread-1| I125: Reading symbol versions from /lib/modules/4.15.0-2-amd64/build/Module.symvers.
2018-04-23T20:11:48.892+04:30| vthread-1| I125: Read 20056 symbol versions
2018-04-23T20:11:48.893+04:30| vthread-1| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.15.0-2-amd64/build/include
2018-04-23T20:11:48.893+04:30| vthread-1| I125: Update kernel header path to /lib/modules/4.15.0-2-amd64/build/include
2018-04-23T20:11:48.893+04:30| vthread-1| I125: Validating path "/lib/modules/4.15.0-2-amd64/build/include" for kernel release "4.15.0-2-amd64".
2018-04-23T20:11:48.893+04:30| vthread-1| I125: Failed to find /lib/modules/4.15.0-2-amd64/build/include/linux/version.h
2018-04-23T20:11:48.893+04:30| vthread-1| I125: /lib/modules/4.15.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2018-04-23T20:11:48.893+04:30| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check
2018-04-23T20:11:48.900+04:30| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.0-2-amd64".
2018-04-23T20:11:48.900+04:30| vthread-1| I125: The header path "/lib/modules/4.15.0-2-amd64/build/include" for the kernel "4.15.0-2-amd64" is valid.  Whoohoo!
2018-04-23T20:11:48.902+04:30| vthread-1| I125: Found compiler at "/usr/bin/gcc"
2018-04-23T20:11:48.906+04:30| vthread-1| I125: Got gcc version "7".
2018-04-23T20:11:48.906+04:30| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.
2018-04-23T20:11:48.910+04:30| vthread-1| I125: Got gcc version "7".
2018-04-23T20:11:48.910+04:30| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.
2018-04-23T20:11:48.912+04:30| vthread-1| I125: Trying to find a suitable PBM set for kernel "4.15.0-2-amd64".
2018-04-23T20:11:48.912+04:30| vthread-1| I125: No matching PBM set was found for kernel "4.15.0-2-amd64".
2018-04-23T20:11:48.912+04:30| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.
2018-04-23T20:11:48.912+04:30| vthread-1| I125: Validating path "/lib/modules/4.15.0-2-amd64/build/include" for kernel release "4.15.0-2-amd64".
2018-04-23T20:11:48.912+04:30| vthread-1| I125: Failed to find /lib/modules/4.15.0-2-amd64/build/include/linux/version.h
2018-04-23T20:11:48.912+04:30| vthread-1| I125: /lib/modules/4.15.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2018-04-23T20:11:48.912+04:30| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check
2018-04-23T20:11:48.922+04:30| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.0-2-amd64".
2018-04-23T20:11:48.922+04:30| vthread-1| I125: The header path "/lib/modules/4.15.0-2-amd64/build/include" for the kernel "4.15.0-2-amd64" is valid.  Whoohoo!
2018-04-23T20:11:48.925+04:30| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.
2018-04-23T20:11:48.925+04:30| vthread-1| I125: Validating path "/lib/modules/4.15.0-2-amd64/build/include" for kernel release "4.15.0-2-amd64".
2018-04-23T20:11:48.925+04:30| vthread-1| I125: Failed to find /lib/modules/4.15.0-2-amd64/build/include/linux/version.h
2018-04-23T20:11:48.925+04:30| vthread-1| I125: /lib/modules/4.15.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2018-04-23T20:11:48.925+04:30| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check
2018-04-23T20:11:48.937+04:30| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.0-2-amd64".
2018-04-23T20:11:48.937+04:30| vthread-1| I125: The header path "/lib/modules/4.15.0-2-amd64/build/include" for the kernel "4.15.0-2-amd64" is valid.  Whoohoo!
2018-04-23T20:11:48.937+04:30| vthread-1| I125: Using temp dir "/tmp".
2018-04-23T20:11:48.940+04:30| vthread-1| I125: Obtaining info using the running kernel.
2018-04-23T20:11:48.940+04:30| vthread-1| I125: Setting header path for 4.15.0-2-amd64 to "/lib/modules/4.15.0-2-amd64/build/include".
2018-04-23T20:11:48.940+04:30| vthread-1| I125: Validating path "/lib/modules/4.15.0-2-amd64/build/include" for kernel release "4.15.0-2-amd64".
2018-04-23T20:11:48.940+04:30| vthread-1| I125: Failed to find /lib/modules/4.15.0-2-amd64/build/include/linux/version.h
2018-04-23T20:11:48.940+04:30| vthread-1| I125: /lib/modules/4.15.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2018-04-23T20:11:48.940+04:30| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check
2018-04-23T20:11:48.951+04:30| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.0-2-amd64".
2018-04-23T20:11:48.951+04:30| vthread-1| I125: The header path "/lib/modules/4.15.0-2-amd64/build/include" for the kernel "4.15.0-2-amd64" is valid.  Whoohoo!
2018-04-23T20:11:49.171+04:30| vthread-1| I125: found symbol version file /lib/modules/4.15.0-2-amd64/build/Module.symvers
2018-04-23T20:11:49.171+04:30| vthread-1| I125: Reading symbol versions from /lib/modules/4.15.0-2-amd64/build/Module.symvers.
2018-04-23T20:11:49.196+04:30| vthread-1| I125: Read 20056 symbol versions
2018-04-23T20:11:49.196+04:30| vthread-1| I125: Invoking modinfo on "vmmon".
2018-04-23T20:11:49.200+04:30| vthread-1| I125: "/sbin/modinfo" exited with status 256.
2018-04-23T20:11:49.200+04:30| vthread-1| I125: Invoking modinfo on "vmnet".
2018-04-23T20:11:49.203+04:30| vthread-1| I125: "/sbin/modinfo" exited with status 256.
2018-04-23T20:11:49.594+04:30| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/4.15.0-2-amd64/misc/vmmon.ko".
2018-04-23T20:11:49.595+04:30| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".
2018-04-23T20:11:49.606+04:30| vthread-1| I125: Successfully extracted the vmmon source.
2018-04-23T20:11:49.606+04:30| vthread-1| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-stxrjw/vmmon-only auto-build HEADER_DIR=/lib/modules/4.15.0-2-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2018-04-23T20:11:52.158+04:30| vthread-1| W115: Failed to build vmmon.  Failed to execute the build command.
2018-04-23T20:11:52.161+04:30| vthread-1| I125: Setting destination path for vmnet to "/lib/modules/4.15.0-2-amd64/misc/vmnet.ko".
2018-04-23T20:11:52.161+04:30| vthread-1| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
2018-04-23T20:11:52.170+04:30| vthread-1| I125: Successfully extracted the vmnet source.
2018-04-23T20:11:52.170+04:30| vthread-1| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-stxrjw/vmnet-only auto-build HEADER_DIR=/lib/modules/4.15.0-2-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2018-04-23T20:11:56.805+04:30| vthread-1| I125: Successfully built vmnet.  Module is currently at "/tmp/modconfig-stxrjw/vmnet.o".
2018-04-23T20:11:56.805+04:30| vthread-1| I125: Found the vmnet symvers file at "/tmp/modconfig-stxrjw/vmnet-only/Module.symvers".
2018-04-23T20:11:56.805+04:30| vthread-1| I125: Installing vmnet from /tmp/modconfig-stxrjw/vmnet.o to /lib/modules/4.15.0-2-amd64/misc/vmnet.ko.
2018-04-23T20:11:56.809+04:30| vthread-1| I125: Registering file "/lib/modules/4.15.0-2-amd64/misc/vmnet.ko".
2018-04-23T20:11:57.108+04:30| vthread-1| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.
2018-04-23T20:11:57.109+04:30| vthread-1| I125: Registering file "/usr/lib/vmware/symvers/vmnet-4.15.0-2-amd64".
2018-04-23T20:11:57.404+04:30| vthread-1| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

Eu tentei pesquisar no Google, mas não consegui encontrar uma postagem relevante

Obrigado antecipadamente

    
por Raakh 23.04.2018 / 18:16

1 resposta

3

Problema na mão

Você está relatando que não consegue executar o VMware no Kali Linux. De acordo com os erros que você postou seu sistema operacional está faltando os módulos VMware necessários para ser executado.

Aproveito este momento para salientar que o Kali Linux não é um de uso geral. Sistema . Você pode continuar a se deparar com esses tipos de erros usando um software não projetado para o Kali Linux. A execução de software de virtualização ou hipervisor não é uma função planejada do Kali Linux. Uma possível solução para o seu problema seria rodar seu software de virtualização no Ubuntu, Debian ou qualquer outro sistema operacional de propósito geral.

Se você deseja continuar usando o Kali Linux ou encontrar o mesmo erro em um sistema operacional diferente, as etapas a seguir podem funcionar como uma possível solução para o erro acima.

Soluções possíveis

Eu irei referenciar este post como contém algumas correções possíveis diferentes.

Primeiro, experimente e execute este comando:

sudo vmware-modconfig --console --install-all

Isso deve instalar todos os módulos do VMware. Agora você deve conseguir executar o VMware conforme o esperado. Veja esta postagem do fórum VMware , pois eles abrangem scripts adicionais que você pode precisar executar para verificar o processo de instalação.

Como alternativa, você pode tentar primeiro:

sudo apt-get install build-essential linux-headers-$(uname -r) open-vm-dkms
sudo ln -s /usr/src/linux-headers-$(uname -r)/include/generated/uapi/linux/version.h /usr/src/linux-headers-$(uname -r)/include/linux/version.h 

Depois da execução: sudo vmware-config-tools.pl . Pode ser necessário executar sudo vmware-modconfig --console --install-all novamente depois que isso for concluído.

Começando do zero

Talvez seja necessário começar de novo com uma nova instalação do VMware. Purgue a instalação existente executando sudo vmware-installer -u vmware-player . Em seguida, execute novamente o script do instalador, por exemplo: ./VMware-*.bundle.

Eu também verificaria se os drivers gráficos e todas as outras partes do sistema estão totalmente atualizados.

Conclusão

Mais uma vez, sugiro que você use um sistema operacional diferente do Kali Linux para concluir esta tarefa. Por favor, leia sobre este post em sua totalidade antes de ir com uma possível correção. Lembre-se de que você precisa instalar os cabeçalhos de kernel apropriados para o seu kernel para que isso funcione. Eu também estou incluindo um link para um guia sobre a instalação VMware no Kali Linux . Há até alguns comentários nesse post sobre como solucionar o problema ainda mais.

Eu também estou incluindo um link para a documentação oficial do Kali Linux em como instalar ferramentas VMware, bem como um link para outra postagem de troca de pilha que parece estar relacionada a esse problema.

Por favor, comente se houver alguma dúvida sobre esta resposta. Agradeço as correções de quaisquer equívocos e comentários sobre como melhorar minhas postagens. Melhor da sorte!

    
por 23.04.2018 / 20:09