Denuncie   Favoritos   Indicar  

VMWare Player 12.5.1 não inicia após atualizar kernel

1. VMWare Player 12.5.1 não inicia após atualizar kernel

bruno
b15#
(usa Outra)

Enviado em 20/02/2017 - 20:09h

Após atualizar o kernel (atualizações normais, não compilei nem me aventurei em nada) para a versão 4.9.10 o meu VMWare parou de iniciar.
A imagem contendo o erro está no seguinte link: http://imgur.com/a/3Rb0h

E aqui o conteúdo do log:



2017-02-20T20:03:40.062-03:00| vthread-4| I125: Log for VMware Workstation pid=4565 version=12.5.1 build=build-4542065 option=Release

2017-02-20T20:03:40.062-03:00| vthread-4| I125: The process is 64-bit.

2017-02-20T20:03:40.062-03:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8

2017-02-20T20:03:40.062-03:00| vthread-4| I125: Host is Linux 4.9.9-100.fc24.x86_64 Fedora release 24 (Twenty Four)

2017-02-20T20:03:40.009-03:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2017-02-20T20:03:40.009-03:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2017-02-20T20:03:40.062-03:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.

2017-02-20T20:03:40.062-03:00| vthread-4| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2017-02-20T20:03:40.062-03:00| vthread-4| I125: PREF Unable to check permissions for preferences file.

2017-02-20T20:03:40.062-03:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/preferences": No such file or directory.

2017-02-20T20:03:40.062-03:00| vthread-4| I125: PREF Failed to load user preferences.

2017-02-20T20:03:40.074-03:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-4565.log

2017-02-20T20:03:40.088-03:00| vthread-4| I125: Obtaining info using the running kernel.

2017-02-20T20:03:40.088-03:00| vthread-4| I125: Created new pathsHash.

2017-02-20T20:03:40.088-03:00| vthread-4| I125: Setting header path for 4.9.9-100.fc24.x86_64 to "/lib/modules/4.9.9-100.fc24.x86_64/build/include".

2017-02-20T20:03:40.088-03:00| vthread-4| I125: Validating path "/lib/modules/4.9.9-100.fc24.x86_64/build/include" for kernel release "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.088-03:00| vthread-4| I125: Failed to find /lib/modules/4.9.9-100.fc24.x86_64/build/include/linux/version.h

2017-02-20T20:03:40.088-03:00| vthread-4| I125: /lib/modules/4.9.9-100.fc24.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-20T20:03:40.088-03:00| vthread-4| I125: using /bin/gcc for preprocess check

2017-02-20T20:03:40.098-03:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.098-03:00| vthread-4| I125: The header path "/lib/modules/4.9.9-100.fc24.x86_64/build/include" for the kernel "4.9.9-100.fc24.x86_64" is valid.  Whoohoo!

2017-02-20T20:03:40.261-03:00| vthread-4| I125: found symbol version file /lib/modules/4.9.9-100.fc24.x86_64/build/Module.symvers

2017-02-20T20:03:40.261-03:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.9.9-100.fc24.x86_64/build/Module.symvers.

2017-02-20T20:03:40.284-03:00| vthread-4| I125: Read 17898 symbol versions

2017-02-20T20:03:40.285-03:00| vthread-4| I125: Reading in info for the vmmon module.

2017-02-20T20:03:40.285-03:00| vthread-4| I125: Reading in info for the vmnet module.

2017-02-20T20:03:40.285-03:00| vthread-4| I125: Reading in info for the vmblock module.

2017-02-20T20:03:40.285-03:00| vthread-4| I125: Reading in info for the vmci module.

2017-02-20T20:03:40.285-03:00| vthread-4| I125: Reading in info for the vsock module.

2017-02-20T20:03:40.285-03:00| vthread-4| I125: Setting vsock to depend on vmci.

2017-02-20T20:03:40.285-03:00| vthread-4| I125: Invoking modinfo on "vmmon".

2017-02-20T20:03:40.287-03:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-20T20:03:40.287-03:00| vthread-4| I125: Invoking modinfo on "vmnet".

2017-02-20T20:03:40.288-03:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-20T20:03:40.288-03:00| vthread-4| I125: Invoking modinfo on "vmblock".

2017-02-20T20:03:40.290-03:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-20T20:03:40.290-03:00| vthread-4| I125: Invoking modinfo on "vmci".

2017-02-20T20:03:40.291-03:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-20T20:03:40.291-03:00| vthread-4| I125: Invoking modinfo on "vsock".

2017-02-20T20:03:40.294-03:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2017-02-20T20:03:40.305-03:00| vthread-4| I125: to be installed: vmmon status: 0

2017-02-20T20:03:40.305-03:00| vthread-4| I125: to be installed: vmnet status: 0

2017-02-20T20:03:40.316-03:00| vthread-4| I125: Obtaining info using the running kernel.

2017-02-20T20:03:40.316-03:00| vthread-4| I125: Setting header path for 4.9.9-100.fc24.x86_64 to "/lib/modules/4.9.9-100.fc24.x86_64/build/include".

2017-02-20T20:03:40.316-03:00| vthread-4| I125: Validating path "/lib/modules/4.9.9-100.fc24.x86_64/build/include" for kernel release "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.316-03:00| vthread-4| I125: Failed to find /lib/modules/4.9.9-100.fc24.x86_64/build/include/linux/version.h

2017-02-20T20:03:40.316-03:00| vthread-4| I125: /lib/modules/4.9.9-100.fc24.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-20T20:03:40.316-03:00| vthread-4| I125: using /bin/gcc for preprocess check

2017-02-20T20:03:40.322-03:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.323-03:00| vthread-4| I125: The header path "/lib/modules/4.9.9-100.fc24.x86_64/build/include" for the kernel "4.9.9-100.fc24.x86_64" is valid.  Whoohoo!

2017-02-20T20:03:40.484-03:00| vthread-4| I125: found symbol version file /lib/modules/4.9.9-100.fc24.x86_64/build/Module.symvers

2017-02-20T20:03:40.484-03:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.9.9-100.fc24.x86_64/build/Module.symvers.

2017-02-20T20:03:40.508-03:00| vthread-4| I125: Read 17898 symbol versions

2017-02-20T20:03:40.508-03:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.9.9-100.fc24.x86_64/build/include

2017-02-20T20:03:40.508-03:00| vthread-4| I125: Update kernel header path to /lib/modules/4.9.9-100.fc24.x86_64/build/include

2017-02-20T20:03:40.508-03:00| vthread-4| I125: Validating path "/lib/modules/4.9.9-100.fc24.x86_64/build/include" for kernel release "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.508-03:00| vthread-4| I125: Failed to find /lib/modules/4.9.9-100.fc24.x86_64/build/include/linux/version.h

2017-02-20T20:03:40.508-03:00| vthread-4| I125: /lib/modules/4.9.9-100.fc24.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-20T20:03:40.508-03:00| vthread-4| I125: using /bin/gcc for preprocess check

2017-02-20T20:03:40.514-03:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.514-03:00| vthread-4| I125: The header path "/lib/modules/4.9.9-100.fc24.x86_64/build/include" for the kernel "4.9.9-100.fc24.x86_64" is valid.  Whoohoo!

2017-02-20T20:03:40.515-03:00| vthread-4| I125: Found compiler at "/bin/gcc"

2017-02-20T20:03:40.517-03:00| vthread-4| I125: Got gcc version "6.3.1".

2017-02-20T20:03:40.517-03:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-20T20:03:40.517-03:00| vthread-4| I125: Using user supplied compiler "/bin/gcc".

2017-02-20T20:03:40.520-03:00| vthread-4| I125: Got gcc version "6.3.1".

2017-02-20T20:03:40.520-03:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-20T20:03:40.522-03:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.522-03:00| vthread-4| I125: No matching PBM set was found for kernel "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.522-03:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-20T20:03:40.522-03:00| vthread-4| I125: Validating path "/lib/modules/4.9.9-100.fc24.x86_64/build/include" for kernel release "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.522-03:00| vthread-4| I125: Failed to find /lib/modules/4.9.9-100.fc24.x86_64/build/include/linux/version.h

2017-02-20T20:03:40.522-03:00| vthread-4| I125: /lib/modules/4.9.9-100.fc24.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-20T20:03:40.522-03:00| vthread-4| I125: using /bin/gcc for preprocess check

2017-02-20T20:03:40.528-03:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.528-03:00| vthread-4| I125: The header path "/lib/modules/4.9.9-100.fc24.x86_64/build/include" for the kernel "4.9.9-100.fc24.x86_64" is valid.  Whoohoo!

2017-02-20T20:03:40.529-03:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-20T20:03:40.529-03:00| vthread-4| I125: Validating path "/lib/modules/4.9.9-100.fc24.x86_64/build/include" for kernel release "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.529-03:00| vthread-4| I125: Failed to find /lib/modules/4.9.9-100.fc24.x86_64/build/include/linux/version.h

2017-02-20T20:03:40.529-03:00| vthread-4| I125: /lib/modules/4.9.9-100.fc24.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-20T20:03:40.529-03:00| vthread-4| I125: using /bin/gcc for preprocess check

2017-02-20T20:03:40.535-03:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.535-03:00| vthread-4| I125: The header path "/lib/modules/4.9.9-100.fc24.x86_64/build/include" for the kernel "4.9.9-100.fc24.x86_64" is valid.  Whoohoo!

2017-02-20T20:03:40.535-03:00| vthread-4| I125: Using temp dir "/tmp".

2017-02-20T20:03:40.537-03:00| vthread-4| I125: Obtaining info using the running kernel.

2017-02-20T20:03:40.537-03:00| vthread-4| I125: Setting header path for 4.9.9-100.fc24.x86_64 to "/lib/modules/4.9.9-100.fc24.x86_64/build/include".

2017-02-20T20:03:40.537-03:00| vthread-4| I125: Validating path "/lib/modules/4.9.9-100.fc24.x86_64/build/include" for kernel release "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.537-03:00| vthread-4| I125: Failed to find /lib/modules/4.9.9-100.fc24.x86_64/build/include/linux/version.h

2017-02-20T20:03:40.537-03:00| vthread-4| I125: /lib/modules/4.9.9-100.fc24.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-20T20:03:40.537-03:00| vthread-4| I125: using /bin/gcc for preprocess check

2017-02-20T20:03:40.543-03:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.9.9-100.fc24.x86_64".

2017-02-20T20:03:40.543-03:00| vthread-4| I125: The header path "/lib/modules/4.9.9-100.fc24.x86_64/build/include" for the kernel "4.9.9-100.fc24.x86_64" is valid.  Whoohoo!

2017-02-20T20:03:40.706-03:00| vthread-4| I125: found symbol version file /lib/modules/4.9.9-100.fc24.x86_64/build/Module.symvers

2017-02-20T20:03:40.706-03:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.9.9-100.fc24.x86_64/build/Module.symvers.

2017-02-20T20:03:40.729-03:00| vthread-4| I125: Read 17898 symbol versions

2017-02-20T20:03:40.729-03:00| vthread-4| I125: Invoking modinfo on "vmmon".

2017-02-20T20:03:40.731-03:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-20T20:03:40.731-03:00| vthread-4| I125: Invoking modinfo on "vmnet".

2017-02-20T20:03:40.733-03:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-20T20:03:40.875-03:00| vthread-4| I125: Setting destination path for vmmon to "/lib/modules/4.9.9-100.fc24.x86_64/misc/vmmon.ko".

2017-02-20T20:03:40.883-03:00| vthread-4| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2017-02-20T20:03:40.935-03:00| vthread-4| I125: Successfully extracted the vmmon source.

2017-02-20T20:03:40.935-03:00| vthread-4| I125: Building module with command "/bin/make -j4 -C /tmp/modconfig-zOp5Sk/vmmon-only auto-build HEADER_DIR=/lib/modules/4.9.9-100.fc24.x86_64/build/include CC=/bin/gcc IS_GCC_3=no"

2017-02-20T20:03:43.795-03:00| vthread-4| W115: Failed to build vmmon.  Failed to execute the build command.

2017-02-20T20:03:43.796-03:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/4.9.9-100.fc24.x86_64/misc/vmnet.ko".

2017-02-20T20:03:43.796-03:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2017-02-20T20:03:43.818-03:00| vthread-4| I125: Successfully extracted the vmnet source.

2017-02-20T20:03:43.818-03:00| vthread-4| I125: Building module with command "/bin/make -j4 -C /tmp/modconfig-zOp5Sk/vmnet-only auto-build HEADER_DIR=/lib/modules/4.9.9-100.fc24.x86_64/build/include CC=/bin/gcc IS_GCC_3=no"

2017-02-20T20:03:45.493-03:00| vthread-4| W115: Failed to build vmnet.  Failed to execute the build command.


Alguma ideia de como posso resolver isso?




att

0 0
  • Quote

    •   


    2. Re: VMWare Player 12.5.1 não inicia após atualizar kernel

    Mauriciodez
    Mauriciodez
    (usa Debian)

    Enviado em 20/02/2017 - 20:13h

    [quote]b15# escreveu:
    Alguma ideia de como posso resolver isso?
    [quote]

    Algumas idéias
    1° - Reinstalar o vmware
    2° - Atualizar o Vmware
    3° - Fazer o dowgrade do kernel
    _______________________________________________________________
    " Nem sempre é amigo aquele que te tira do buraco !!! ( Saddam Hussein )"

    0 0
  • Quote

    • 3. Re: VMWare Player 12.5.1 não inicia após atualizar kernel

    bruno
    b15#
    (usa Outra)

    Enviado em 20/02/2017 - 20:16h

    Mauriciodez escreveu:

    [quote]b15# escreveu:
    Alguma ideia de como posso resolver isso?
    [quote]

    Algumas idéias
    1° - Reinstalar o vmware
    2° - Atualizar o Vmware
    3° - Fazer o dowgrade do kernel
    _______________________________________________________________
    " Nem sempre é amigo aquele que te tira do buraco !!! ( Saddam Hussein )"



    Esqueci de dizer, o 1º e 2º já fiz e não resolveu, o terceiro não sei se vale a pena fazer o downgrade apenas por causa do VMWare, não teria uma outra solução?



    0 0
  • Quote

    • 4. VMWare Player 12.5.1 não inicia após atualizar kernel

    Edwal F. Paiva Filho
    nicolo
    (usa Ubuntu)

    Enviado em 20/02/2017 - 20:19h

    Fail to build vmet

    O vmware compila um módulo para o kernel rodante.
    Isso significa que ele precisa do pacote de compilação que nem sempre é uma instalação default.

    Quando você instalou outro kernel precisa recompilar o módulo do kernel para o novo kernel rodante.
    O pacote de compilação foi atualizado?

    Sugestão:
    Verificar o pacote de compilação.
    e/ou
    Instalar a versão mais recente do vmware.

    0 0
  • Quote

    • 5. Re: VMWare Player 12.5.1 não inicia após atualizar kernel

    bruno
    b15#
    (usa Outra)

    Enviado em 20/02/2017 - 20:22h

    nicolo escreveu:

    Fail to build vmet

    O vmware compila um módulo para o kernel rodante.
    Isso significa que ele precisa do pacote de compilação que nem sempre é uma instalação default.

    Quando você instalou outro kernel precisa recompilar o módulo do kernel para o novo kernel rodante.
    O pacote de compilação foi atualizado?

    Sugestão:
    Verificar o pacote de compilação.
    e/ou
    Instalar a versão mais recente do vmware.


    "Verificar o pacote de compilação."
    Não sei fazer isso, poderia me auxiliar?

    E o VMWare está instalado na última versão disponível...



    0 0
  • Quote

    • 6. Re: VMWare Player 12.5.1 não inicia após atualizar kernel

    Mauriciodez
    Mauriciodez
    (usa Debian)

    Enviado em 20/02/2017 - 20:23h

    b15# escreveu:
    o terceiro não sei se vale a pena fazer o downgrade apenas por causa do VMWare, não teria uma outra solução?


    Acho que a pergunta seria outra ... vc precisa do kernel 4.9 ????
    _______________________________________________________________
    " Nem sempre é amigo aquele que te tira do buraco !!! ( Saddam Hussein )"

    0 0
  • Quote

    • 7. Re: VMWare Player 12.5.1 não inicia após atualizar kernel

    Jose Mario
    zezaocapoeira
    (usa Slackware)

    Enviado em 20/02/2017 - 20:38h

    Salve mano.

    Dá uma olhada aqui.

    https://www.vivaolinux.com.br/topico/Slackware/Problema-ao-executar-a-VMWare-Player-no-Slackware-142...

    Obrigado pela atenção , salve!!!

    1 0
  • Quote





    • Patrocínio

    Site hospedado pelo provedor RedeHost.
    Linux banner

    Destaques

    Artigos

    Manutenção de sistemas Linux Debian e derivados com apt-get, apt, aptitude e dpkg

    Criatividade para TI parte 1

    Melhorando o tempo de boot do Fedora e outras distribuições

    Como instalar as extensões Dash To Dock e Hide Top Bar no Gnome 45/46

    E a guerra contra bots continua

    Dicas

    Instalar Google Chrome no Debian e derivados

    Consertando o erro do Sushi e Wayland no Opensuse Leap 15

    Instalar a última versão do PostgreSQL no Lunix mantendo atualizado

    Flathub na sua distribuição Linux e comandos básicos de gerenciamento

    Instalando o FreeOffice no LMDE 6

    Tópicos

    Problemas para conectar à rede no Linux Mint (10)

    Clamav e suas atualizações (15)

    Desenvolvimento de um driver (10)

    Não esta salvando as configurações de usuário. (3)

    Quais Shell Scripts vocês usam? (5)

    Top 10 do mês

    Scripts

    [Shell Script] Script para desinstalar pacotes desnecessários no OpenSuse

    [Shell Script] Script para criar certificados de forma automatizada no OpenVpn

    [Shell Script] Conversor de vídeo com opção de legenda

    [C/C++] BRT - Bulk Renaming Tool

    [Shell Script] Criação de Usuarios , Grupo e instalação do servidor de arquivos samba

    A maior comunidade GNU/Linux da América Latina! Artigos, dicas, tutoriais, fórum, scripts e muito mais. Ideal para quem busca auto-ajuda.

    Site hospedado por: