Проблема первого запуска VMware Workstation Pro 15.1.0 в Debian 10.1

0

1

Доброго всем времени!

Какая-то трабла с VMware Workstation Pro 15.1.0. Ось Debian 10. Прога установлена корректно, но при первом запуске ругается на строчку «Virtual machine monitor - failed»:

/usr/bin/vmware
[AppLoader] Use shipped Linux kernel AIO access library.
An up-to-date "libaio" or "libaio1" package from your system is preferred.
Stopping VMware services:
   VMware Authentication Daemon                                        done
   VM communication interface socket family                            done
   Virtual machine communication interface                             done
   Virtual machine monitor                                             done
   Blocking file system                                                done
make: вход в каталог «/tmp/modconfig-6GBrYJ/vmmon-only»
/usr/bin/make -C /lib/modules/5.2.0-2-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: вход в каталог «/usr/src/linux-headers-5.2.0-2-amd64»
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/linux/driver.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/linux/hostif.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/common/memtrack.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/common/apic.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/common/vmx86.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/common/cpuid.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/common/task.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/common/comport.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/common/phystrack.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/vmcore/moduleloop.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/bootstrap/monLoaderVmmon.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/bootstrap/monLoader.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/bootstrap/vmmblob.o
  CC [M]  /tmp/modconfig-6GBrYJ/vmmon-only/bootstrap/bootstrap.o
make[1]: выход из каталога «/usr/src/linux-headers-5.2.0-2-amd64»
make: выход из каталога «/tmp/modconfig-6GBrYJ/vmmon-only»
Starting VMware services:
   Virtual machine monitor                                            failed
   Virtual machine communication interface                             done
   VM communication interface socket family                            done
   Blocking file system                                                done
   Virtual ethernet                                                    done
   VMware Authentication Daemon                                        done

В логах вот такие записи:

2019-09-16T13:05:49.245+12:00| host-12025| I125: Log for VMware Workstation pid=12025 version=15.1.0 build=build-13591040 option=Release
2019-09-16T13:05:49.245+12:00| host-12025| I125: The process is 64-bit.
2019-09-16T13:05:49.245+12:00| host-12025| I125: Host codepage=UTF-8 encoding=UTF-8
2019-09-16T13:05:49.245+12:00| host-12025| I125: Host is Linux 5.2.0-2-amd64 Debian GNU/Linux bullseye/sid
2019-09-16T13:05:49.245+12:00| host-12025| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": Нет такого файла или каталога.
2019-09-16T13:05:49.245+12:00| host-12025| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": Нет такого файла или каталога.
2019-09-16T13:05:49.245+12:00| host-12025| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2019-09-16T13:05:49.245+12:00| host-12025| I125: DictionaryLoad: Cannot open file "/home/egor/.vmware/config": Нет такого файла или каталога.
2019-09-16T13:05:49.245+12:00| host-12025| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/egor/.vmware/config": Нет такого файла или каталога.
2019-09-16T13:05:49.245+12:00| host-12025| I125: PREF Optional preferences file not found at /home/egor/.vmware/config. Using default values.
2019-09-16T13:05:49.245+12:00| host-12025| I125: DictionaryLoad: Cannot open file "/home/egor/.vmware/preferences": Нет такого файла или каталога.
2019-09-16T13:05:49.245+12:00| host-12025| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/egor/.vmware/preferences": Нет такого файла или каталога.
2019-09-16T13:05:49.245+12:00| host-12025| I125: PREF Optional preferences file not found at /home/egor/.vmware/preferences. Using default values.
2019-09-16T13:05:49.399+12:00| host-12025| W115: Logging to /tmp/vmware-root/vmware-12025.log
2019-09-16T13:05:49.462+12:00| host-12025| I125: Obtaining info using the running kernel.
2019-09-16T13:05:49.462+12:00| host-12025| I125: Created new pathsHash.
2019-09-16T13:05:49.462+12:00| host-12025| I125: Setting header path for 5.2.0-2-amd64 to "/lib/modules/5.2.0-2-amd64/build/include".
2019-09-16T13:05:49.462+12:00| host-12025| I125: Validating path "/lib/modules/5.2.0-2-amd64/build/include" for kernel release "5.2.0-2-amd64".
2019-09-16T13:05:49.462+12:00| host-12025| I125: Failed to find /lib/modules/5.2.0-2-amd64/build/include/linux/version.h
2019-09-16T13:05:49.462+12:00| host-12025| I125: /lib/modules/5.2.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2019-09-16T13:05:49.462+12:00| host-12025| I125: using /usr/bin/gcc-8 for preprocess check
2019-09-16T13:05:49.471+12:00| host-12025| I125: Preprocessed UTS_RELEASE, got value "5.2.0-2-amd64".
2019-09-16T13:05:49.471+12:00| host-12025| I125: The header path "/lib/modules/5.2.0-2-amd64/build/include" for the kernel "5.2.0-2-amd64" is valid.  Whoohoo!
2019-09-16T13:05:49.657+12:00| host-12025| I125: found symbol version file /lib/modules/5.2.0-2-amd64/build/Module.symvers
2019-09-16T13:05:49.657+12:00| host-12025| I125: Reading symbol versions from /lib/modules/5.2.0-2-amd64/build/Module.symvers.
2019-09-16T13:05:49.678+12:00| host-12025| I125: Read 20775 symbol versions
2019-09-16T13:05:49.679+12:00| host-12025| I125: Reading in info for the vmmon module.
2019-09-16T13:05:49.679+12:00| host-12025| I125: Reading in info for the vmnet module.
2019-09-16T13:05:49.679+12:00| host-12025| I125: Reading in info for the vmci module.
2019-09-16T13:05:49.679+12:00| host-12025| I125: Reading in info for the vsock module.
2019-09-16T13:05:49.679+12:00| host-12025| I125: Setting vsock to depend on vmci.
2019-09-16T13:05:49.679+12:00| host-12025| I125: Invoking modinfo on "vmmon".
2019-09-16T13:05:49.681+12:00| host-12025| I125: "/sbin/modinfo" exited with status 256.
2019-09-16T13:05:49.681+12:00| host-12025| I125: Invoking modinfo on "vmnet".
2019-09-16T13:05:49.684+12:00| host-12025| I125: "/sbin/modinfo" exited with status 0.
2019-09-16T13:05:49.684+12:00| host-12025| I125: Invoking modinfo on "vmci".
2019-09-16T13:05:49.686+12:00| host-12025| I125: "/sbin/modinfo" exited with status 256.
2019-09-16T13:05:49.686+12:00| host-12025| I125: Invoking modinfo on "vsock".
2019-09-16T13:05:49.689+12:00| host-12025| I125: "/sbin/modinfo" exited with status 0.
2019-09-16T13:05:49.700+12:00| host-12025| I125: to be installed: vmmon status: 0
2019-09-16T13:05:49.724+12:00| host-12025| I125: Obtaining info using the running kernel.
2019-09-16T13:05:49.724+12:00| host-12025| I125: Setting header path for 5.2.0-2-amd64 to "/lib/modules/5.2.0-2-amd64/build/include".
2019-09-16T13:05:49.724+12:00| host-12025| I125: Validating path "/lib/modules/5.2.0-2-amd64/build/include" for kernel release "5.2.0-2-amd64".
2019-09-16T13:05:49.724+12:00| host-12025| I125: Failed to find /lib/modules/5.2.0-2-amd64/build/include/linux/version.h
2019-09-16T13:05:49.724+12:00| host-12025| I125: /lib/modules/5.2.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2019-09-16T13:05:49.724+12:00| host-12025| I125: using /usr/bin/gcc-8 for preprocess check
2019-09-16T13:05:49.730+12:00| host-12025| I125: Preprocessed UTS_RELEASE, got value "5.2.0-2-amd64".
2019-09-16T13:05:49.730+12:00| host-12025| I125: The header path "/lib/modules/5.2.0-2-amd64/build/include" for the kernel "5.2.0-2-amd64" is valid.  Whoohoo!
2019-09-16T13:05:49.916+12:00| host-12025| I125: found symbol version file /lib/modules/5.2.0-2-amd64/build/Module.symvers
2019-09-16T13:05:49.916+12:00| host-12025| I125: Reading symbol versions from /lib/modules/5.2.0-2-amd64/build/Module.symvers.
2019-09-16T13:05:49.934+12:00| host-12025| I125: Read 20775 symbol versions
2019-09-16T13:05:49.942+12:00| host-12025| I125: Kernel header path retrieved from FileEntry: /lib/modules/5.2.0-2-amd64/build/include
2019-09-16T13:05:49.942+12:00| host-12025| I125: Update kernel header path to /lib/modules/5.2.0-2-amd64/build/include
2019-09-16T13:05:49.942+12:00| host-12025| I125: Validating path "/lib/modules/5.2.0-2-amd64/build/include" for kernel release "5.2.0-2-amd64".
2019-09-16T13:05:49.942+12:00| host-12025| I125: Failed to find /lib/modules/5.2.0-2-amd64/build/include/linux/version.h
2019-09-16T13:05:49.942+12:00| host-12025| I125: /lib/modules/5.2.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2019-09-16T13:05:49.942+12:00| host-12025| I125: using /usr/bin/gcc-8 for preprocess check
2019-09-16T13:05:49.951+12:00| host-12025| I125: Preprocessed UTS_RELEASE, got value "5.2.0-2-amd64".
2019-09-16T13:05:49.951+12:00| host-12025| I125: The header path "/lib/modules/5.2.0-2-amd64/build/include" for the kernel "5.2.0-2-amd64" is valid.  Whoohoo!
2019-09-16T13:05:49.953+12:00| host-12025| I125: Found compiler at "/usr/bin/gcc"
2019-09-16T13:05:49.956+12:00| host-12025| I125: Got gcc version "9".
2019-09-16T13:05:49.956+12:00| host-12025| I125: GCC major version 9 does not match Kernel GCC major version 8.
2019-09-16T13:05:49.956+12:00| host-12025| I125: Attempting to use a compiler at location "/usr/bin/gcc-8".
2019-09-16T13:05:49.960+12:00| host-12025| I125: Got gcc version "8".
2019-09-16T13:05:49.960+12:00| host-12025| I125: The GCC version matches the kernel GCC minor version like a glove.
2019-09-16T13:05:49.964+12:00| host-12025| I125: Got gcc version "8".
2019-09-16T13:05:49.964+12:00| host-12025| I125: The GCC version matches the kernel GCC minor version like a glove.
2019-09-16T13:05:49.968+12:00| host-12025| I125: Trying to find a suitable PBM set for kernel "5.2.0-2-amd64".
2019-09-16T13:05:49.968+12:00| host-12025| I125: No matching PBM set was found for kernel "5.2.0-2-amd64".
2019-09-16T13:05:49.968+12:00| host-12025| I125: The GCC version matches the kernel GCC minor version like a glove.
2019-09-16T13:05:49.968+12:00| host-12025| I125: Validating path "/lib/modules/5.2.0-2-amd64/build/include" for kernel release "5.2.0-2-amd64".
2019-09-16T13:05:49.968+12:00| host-12025| I125: Failed to find /lib/modules/5.2.0-2-amd64/build/include/linux/version.h
2019-09-16T13:05:49.968+12:00| host-12025| I125: /lib/modules/5.2.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2019-09-16T13:05:49.968+12:00| host-12025| I125: using /usr/bin/gcc-8 for preprocess check
2019-09-16T13:05:49.980+12:00| host-12025| I125: Preprocessed UTS_RELEASE, got value "5.2.0-2-amd64".
2019-09-16T13:05:49.980+12:00| host-12025| I125: The header path "/lib/modules/5.2.0-2-amd64/build/include" for the kernel "5.2.0-2-amd64" is valid.  Whoohoo!
2019-09-16T13:05:49.981+12:00| host-12025| I125: The GCC version matches the kernel GCC minor version like a glove.
2019-09-16T13:05:49.981+12:00| host-12025| I125: Validating path "/lib/modules/5.2.0-2-amd64/build/include" for kernel release "5.2.0-2-amd64".
2019-09-16T13:05:49.981+12:00| host-12025| I125: Failed to find /lib/modules/5.2.0-2-amd64/build/include/linux/version.h
2019-09-16T13:05:49.981+12:00| host-12025| I125: /lib/modules/5.2.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2019-09-16T13:05:49.981+12:00| host-12025| I125: using /usr/bin/gcc-8 for preprocess check
2019-09-16T13:05:49.992+12:00| host-12025| I125: Preprocessed UTS_RELEASE, got value "5.2.0-2-amd64".
2019-09-16T13:05:49.992+12:00| host-12025| I125: The header path "/lib/modules/5.2.0-2-amd64/build/include" for the kernel "5.2.0-2-amd64" is valid.  Whoohoo!
2019-09-16T13:05:49.992+12:00| host-12025| I125: Using temp dir "/tmp".
2019-09-16T13:05:49.998+12:00| host-12025| I125: Obtaining info using the running kernel.
2019-09-16T13:05:49.998+12:00| host-12025| I125: Setting header path for 5.2.0-2-amd64 to "/lib/modules/5.2.0-2-amd64/build/include".
2019-09-16T13:05:49.998+12:00| host-12025| I125: Validating path "/lib/modules/5.2.0-2-amd64/build/include" for kernel release "5.2.0-2-amd64".
2019-09-16T13:05:49.998+12:00| host-12025| I125: Failed to find /lib/modules/5.2.0-2-amd64/build/include/linux/version.h
2019-09-16T13:05:49.998+12:00| host-12025| I125: /lib/modules/5.2.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2019-09-16T13:05:49.998+12:00| host-12025| I125: using /usr/bin/gcc-8 for preprocess check
2019-09-16T13:05:50.010+12:00| host-12025| I125: Preprocessed UTS_RELEASE, got value "5.2.0-2-amd64".
2019-09-16T13:05:50.010+12:00| host-12025| I125: The header path "/lib/modules/5.2.0-2-amd64/build/include" for the kernel "5.2.0-2-amd64" is valid.  Whoohoo!
2019-09-16T13:05:50.204+12:00| host-12025| I125: found symbol version file /lib/modules/5.2.0-2-amd64/build/Module.symvers
2019-09-16T13:05:50.204+12:00| host-12025| I125: Reading symbol versions from /lib/modules/5.2.0-2-amd64/build/Module.symvers.
2019-09-16T13:05:50.222+12:00| host-12025| I125: Read 20775 symbol versions
2019-09-16T13:05:50.222+12:00| host-12025| I125: Invoking modinfo on "vmmon".
2019-09-16T13:05:50.225+12:00| host-12025| I125: "/sbin/modinfo" exited with status 256.
2019-09-16T13:05:51.617+12:00| host-12025| I125: Setting destination path for vmmon to "/lib/modules/5.2.0-2-amd64/misc/vmmon.ko".
2019-09-16T13:05:51.617+12:00| host-12025| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".
2019-09-16T13:05:51.625+12:00| host-12025| I125: Successfully extracted the vmmon source.
2019-09-16T13:05:51.625+12:00| host-12025| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-6GBrYJ/vmmon-only auto-build HEADER_DIR=/lib/modules/5.2.0-2-amd64/build/include CC=/usr/bin/gcc-8 IS_GCC_3=no"
2019-09-16T13:05:53.460+12:00| host-12025| W115: Failed to build vmmon.  Failed to execute the build command.

На Xubuntu LTS при этом ставится без проблем... Куда копать:(?

Ссылка

Стоп, а пакет linux-headers-amd64 у тебя стоит? Если нет, то вот и причина. Ниже тогда не читай.

ЕМНИП, VMware так себе работает на новых ядрах.

Host is Linux 5.2.0-2-amd64 Debian GNU/Linux bullseye/sid

А в Ubuntu 18.04 или 4.15, или 5.0

Подключи репозитории Stretch и поставь оттуда ядро 4.19 для проверки.

Vsevolod-linuxoid ★★★★★
(16.09.19 05:45:39 MSK)
Последнее исправление: Vsevolod-linuxoid 16.09.19 05:50:44 MSK (всего исправлений: 3)

Кстати, https://github.com/mkubecek/vmware-host-modules С учетом того, что и ядра и саму вмваре теперь клепают (и депрекейтят) со скоростью шальной мысли, очень полезный проект.

zendrz ★★
(16.09.19 06:24:51 MSK)

Ответ на: комментарий от Vsevolod-linuxoid 16.09.19 05:45:39 MSK

Да, установлено linux-headers-amd64 самой новой версии (5.2+106).

Баловаться ядрами не буду, ибо ноут боевой, постоянно нужен в работе, и плюс инет неадекватно дорогой со скоростью 50-100 кбит/с. Если тут не получится с советами, то придётся попробовать что-нибудь другое из виртуалок. Надеюсь qemu умеет пробрасывать карту optimus...

~~cheshire_cat~~ ★★
(16.09.19 07:42:56 MSK) автор топика

Ответ на: комментарий от zendrz 16.09.19 06:24:51 MSK

Возможно, но лучше разобраться с тем что есть.

~~cheshire_cat~~ ★★
(16.09.19 07:44:09 MSK) автор топика

Похожие темы