VM lässt sich erst nach Neuinstallation von Workstation starten

[Forentroll]

Host: openSUSE Tumbleweed
Guest: Windows 10 20H1

Nach Installation von Workstation Pro 16.1.1 build-17801498 laufen die VMs völlig normal.
Wird der Rechner jedoch rebooted, wird der Start jeglicher VMs mit folgenden Fehlermeldungen quittiert:

Code: Alles auswählen

Could not open /dev/vmmon: Datei oder Verzeichnis nicht gefunden.
Please make sure that the kernel module `vmmon' is loaded.

Code: Alles auswählen

Failed to initialize monitor device.

Code: Alles auswählen

Unable to change virtual machine power state: Transport (VMDB) error -14: Pipe connection has been broken.

Nach einer weiteren Neuinstallation laufen auch die VMs wieder bis zum nächsten Rechnerneustart.

[~thc]

Die Installation der WS kompiliert (?) und lädt die Kernel-Module korrekt, so dass die VMs funktionieren. Allerdings werden die Module nicht neustartfest im System verankert, so dass sie nach einem Neustart nicht mehr geladen sind. Das ist im Prinzip ein Fehler des Installers - ich würde die Meldungen oder Logs des Installationsprozesses darauf abklopfen.

[Forentroll]

Code: Alles auswählen

dmesg | grep -i vmware
[    4.503794] systemd-sysv-generator[653]: SysV service '/etc/init.d/vmware' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.

Die Datei '/etc/init.d/vmware' hat die Zugriffsrechte 755 und gehört root/root. Auch eine Erweiterung der Rechte auf 777 brachte keinen Erfolg.

Auffällig ist bei der Installation, dass nach einem Pfad gefragt wird und '/etc/init.d/' vorgeschlagen wird.
Bei früheren Installern wurde der Vorschlag mit Enter übernommen; hier musste er explizit eingetippt werden.

Code: Alles auswählen

journalctl | grep -i vmware
Apr 18 15:45:11 ORION-PC baloo_file[2772]: 202707346676318981 "/home/orion/Vorlagen/VMware/VMware-Workstation-Full-16.1.0-17198959.x86_64.bundle" renaming "VMware-Workstation-Full-16.1.0-17198959.x86_64.bundle.crdownload" to "VMware-Workstation-Full-16.1.0-17198959.x86_64.bundle"
Apr 18 15:46:00 ORION-PC systemd[2535]: Started /home/orion/Vorlagen/VMware/VMware-Workstation-Full-16.1.0-17198959.x86_64.bundle.
Apr 18 15:46:01 ORION-PC systemd[2535]: app-\x2fhome\x2forion\x2fVorlagen\x2fVMware\x2fVMware\x2dWorkstation\x2dFull\x2d16.1.0\x2d17198959.x86_64.bundle-1ab77b6038fe41798dd22aca9de6eaa5.scope: Succeeded.
Apr 18 15:46:01 ORION-PC systemd[2535]: app-\x2fhome\x2forion\x2fVorlagen\x2fVMware\x2fVMware\x2dWorkstation\x2dFull\x2d16.1.0\x2d17198959.x86_64.bundle-1ab77b6038fe41798dd22aca9de6eaa5.scope: Consumed 1.204s CPU time.
Apr 28 17:17:46 ORION-PC baloo_file[2750]: 202713668868178690 "/home/orion/Vorlagen/VMware/VMware-Workstation-Full-16.1.1-17801498.x86_64.bundle" renaming "VMware-Workstation-Full-16.1.1-17801498.x86_64.bundle" to "VMware-Workstation-Full-16.1.1-17801498.x86_64.bundle"
Apr 28 17:24:10 ORION-PC VMware[3884]: /usr/sbin/vmware-authdlauncher: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Apr 28 17:24:25 ORION-PC VMware[5340]: /usr/sbin/vmware-authdlauncher: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Apr 28 17:24:30 ORION-PC VMware[5534]: /usr/sbin/vmware-authdlauncher: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Apr 28 17:24:36 ORION-PC VMware[5715]: /usr/sbin/vmware-authdlauncher: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Apr 28 17:24:59 ORION-PC systemd[2531]: Started VMware Workstation.
Apr 28 17:25:00 ORION-PC at-spi-bus-launcher[2656]: dbus-daemon[2656]: Activating service name='org.a11y.atspi.Registry' requested by ':1.19' (uid=1000 pid=5737 comm="/usr/lib/vmware/bin/vmware ")
Apr 28 17:25:36 ORION-PC polkit-kde-authentication-agent-1[2755]: Message of action:  "Legitimierung ist erforderlich, um »/usr/lib/vmware/bin/vmware-setup-helper« als Superuser auszuführen"
Apr 28 17:25:39 ORION-PC polkitd[1249]: Operator of unix-session:1 successfully authenticated as unix-user:root to gain ONE-SHOT authorization for action org.freedesktop.policykit.exec for unix-process:5737:48423 [/usr/lib/vmware/bin/vmware] (owned by unix-user:orion)
Apr 28 17:25:39 ORION-PC pkexec[5883]: orion: Executing command [USER=root] [TTY=unknown] [CWD=/home/orion] [COMMAND=/usr/lib/vmware/bin/vmware-setup-helper -e -o -u yes -c yes -n VMware Workstation -v 16.0 -s 41616-4GJ9L-M82JA-002RK-39F45]
Apr 28 17:32:20 ORION-PC dbus-daemon[2549]: [session uid=1000 pid=2549] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.48' (uid=1000 pid=5737 comm="/usr/lib/vmware/bin/vmware ")
Apr 28 17:32:20 ORION-PC dbus-daemon[2549]: [session uid=1000 pid=2549] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.48' (uid=1000 pid=5737 comm="/usr/lib/vmware/bin/vmware ")
Apr 28 17:32:20 ORION-PC dbus-daemon[2549]: [session uid=1000 pid=2549] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.48' (uid=1000 pid=5737 comm="/usr/lib/vmware/bin/vmware ")
Apr 28 17:32:20 ORION-PC dbus-daemon[2549]: [session uid=1000 pid=2549] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.48' (uid=1000 pid=5737 comm="/usr/lib/vmware/bin/vmware ")
Apr 28 17:32:20 ORION-PC dbus-daemon[2549]: [session uid=1000 pid=2549] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.48' (uid=1000 pid=5737 comm="/usr/lib/vmware/bin/vmware ")
Apr 28 17:32:20 ORION-PC dbus-daemon[1242]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.89' (uid=1000 pid=5737 comm="/usr/lib/vmware/bin/vmware ")
Apr 28 17:32:52 ORION-PC dbus-daemon[1242]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.92' (uid=1000 pid=5737 comm="/usr/lib/vmware/bin/vmware ")
Apr 28 18:04:21 ORION-PC dbus-daemon[1242]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.104' (uid=1000 pid=5737 comm="/usr/lib/vmware/bin/vmware ")
Apr 28 21:15:21 ORION-PC dbus-daemon[1242]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.135' (uid=1000 pid=5737 comm="/usr/lib/vmware/bin/vmware ")
Apr 28 21:20:22 ORION-PC plasmashell[2759]: Arrived mimeData (QUrl("file:///usr/local/share/applications/vmware-workstation.desktop")) ("text/uri-list") at 1802 ,  673
Apr 28 21:20:27 ORION-PC plasmashell[2759]: Arrived mimeData (QUrl("file:///usr/local/share/applications/vmware-player.desktop")) ("text/uri-list") at 1533 ,  535
Apr 28 21:20:32 ORION-PC plasmashell[2759]: Arrived mimeData (QUrl("file:///usr/local/share/applications/vmware-netcfg.desktop")) ("text/uri-list") at 2184 ,  557
Apr 28 21:20:43 ORION-PC plasmashell[2759]: plasma.containments.desktop.folder.foldermodel: clearing drop target positions after timeout: QHash(("vmware-workstation.desktop", QPoint(1944,1333))("vmware-netcfg.desktop", QPoint(2218,1309))("vmware-player.desktop", QPoint(1722,1350)))
Apr 28 21:21:04 ORION-PC systemd[2531]: Started /usr/lib/vmware/bin/vmware.
Apr 28 21:21:04 ORION-PC systemd[2531]: app-\x2fusr\x2flib\x2fvmware\x2fbin\x2fvmware-31b51badd36b4ae187a07a64df559d42.scope: Succeeded.
Apr 28 21:21:08 ORION-PC dbus-daemon[1242]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.140' (uid=1000 pid=5737 comm="/usr/lib/vmware/bin/vmware ")
Apr 28 22:36:48 ORION-PC dbus-daemon[1242]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.166' (uid=1000 pid=5737 comm="/usr/lib/vmware/bin/vmware ")
Apr 28 23:31:49 ORION-PC systemd[2531]: app-vmware\x2dworkstation-0cec82796c1d448c9439b2e4c090913e.scope: Succeeded.
Apr 28 23:31:49 ORION-PC systemd[2531]: app-vmware\x2dworkstation-0cec82796c1d448c9439b2e4c090913e.scope: Consumed 6h 9min 51.935s CPU time.
Apr 29 08:22:58 ORION-PC systemd-sysv-generator[650]: SysV service '/etc/init.d/vmware' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Apr 29 08:35:22 ORION-PC systemd[5762]: Started VMware Workstation.
Apr 29 08:35:23 ORION-PC at-spi-bus-launcher[5889]: dbus-daemon[5889]: Activating service name='org.a11y.atspi.Registry' requested by ':1.15' (uid=1000 pid=6858 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 08:35:28 ORION-PC dbus-daemon[5780]: [session uid=1000 pid=5780] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.44' (uid=1000 pid=6858 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 08:35:28 ORION-PC dbus-daemon[5780]: [session uid=1000 pid=5780] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.44' (uid=1000 pid=6858 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 08:35:28 ORION-PC dbus-daemon[5780]: [session uid=1000 pid=5780] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.44' (uid=1000 pid=6858 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 08:35:28 ORION-PC dbus-daemon[5780]: [session uid=1000 pid=5780] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.44' (uid=1000 pid=6858 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 08:35:28 ORION-PC dbus-daemon[5780]: [session uid=1000 pid=5780] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.44' (uid=1000 pid=6858 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 08:35:28 ORION-PC dbus-daemon[1242]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.73' (uid=1000 pid=6858 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 08:38:30 ORION-PC systemd[5762]: Started VMware Workstation.
Apr 29 08:39:51 ORION-PC dbus-daemon[1242]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.79' (uid=1000 pid=7373 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 08:40:39 ORION-PC systemd[5762]: app-vmware\x2dworkstation-14fc8741654a46a5bff910f806ad279e.scope: Succeeded.
Apr 29 08:40:39 ORION-PC systemd[5762]: app-vmware\x2dworkstation-14fc8741654a46a5bff910f806ad279e.scope: Consumed 6.192s CPU time.
Apr 29 09:05:27 ORION-PC systemd-sysv-generator[9957]: SysV service '/etc/init.d/vmware' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Apr 29 09:05:31 ORION-PC systemd-sysv-generator[11336]: SysV service '/etc/init.d/vmware' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Apr 29 09:24:05 ORION-PC systemd[5762]: app-vmware\x2dworkstation-ad70e5d0ae014bcd800b8d0f67717808.scope: Succeeded.
Apr 29 09:24:05 ORION-PC systemd[5762]: app-vmware\x2dworkstation-ad70e5d0ae014bcd800b8d0f67717808.scope: Consumed 9.470s CPU time.
Apr 29 09:24:07 ORION-PC VMware[14282]: /usr/sbin/vmware-authdlauncher: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Apr 29 09:26:29 ORION-PC VMware[14720]: /usr/sbin/vmware-authdlauncher: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Apr 29 09:26:43 ORION-PC VMware[16179]: /usr/sbin/vmware-authdlauncher: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Apr 29 09:26:48 ORION-PC VMware[16368]: /usr/sbin/vmware-authdlauncher: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Apr 29 09:26:53 ORION-PC VMware[16538]: /usr/sbin/vmware-authdlauncher: error while loading shared libraries: libssl.so.1.0.2: cannot open shared object file: No such file or directory
Apr 29 09:27:02 ORION-PC systemd[5762]: Started VMware Workstation.
Apr 29 09:27:12 ORION-PC polkit-kde-authentication-agent-1[5995]: Message of action:  "Legitimierung ist erforderlich, um »/usr/lib/vmware/bin/vmware-setup-helper« als Superuser auszuführen"
Apr 29 09:27:15 ORION-PC polkitd[1249]: Operator of unix-session:1 successfully authenticated as unix-user:root to gain ONE-SHOT authorization for action org.freedesktop.policykit.exec for unix-process:16553:384874 [/usr/lib/vmware/bin/vmware] (owned by unix-user:orion)
Apr 29 09:27:15 ORION-PC pkexec[16681]: orion: Executing command [USER=root] [TTY=unknown] [CWD=/home/orion] [COMMAND=/usr/lib/vmware/bin/vmware-setup-helper -e -o -c yes]
Apr 29 09:28:01 ORION-PC dbus-daemon[1242]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.114' (uid=1000 pid=16553 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 13:02:27 ORION-PC systemd[5762]: app-vmware\x2dworkstation-af3a677ed04a47cf8db8cc246fea084c.scope: Succeeded.
Apr 29 13:02:27 ORION-PC systemd[5762]: app-vmware\x2dworkstation-af3a677ed04a47cf8db8cc246fea084c.scope: Consumed 2h 33min 48.884s CPU time.
Apr 29 15:44:56 ORION-PC systemd-sysv-generator[653]: SysV service '/etc/init.d/vmware' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Apr 29 18:29:18 ORION-PC systemd[2537]: Started VMware Workstation.
Apr 29 18:29:19 ORION-PC at-spi-bus-launcher[2661]: dbus-daemon[2661]: Activating service name='org.a11y.atspi.Registry' requested by ':1.26' (uid=1000 pid=18183 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 18:29:21 ORION-PC dbus-daemon[2555]: [session uid=1000 pid=2555] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.82' (uid=1000 pid=18183 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 18:29:21 ORION-PC dbus-daemon[2555]: [session uid=1000 pid=2555] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.82' (uid=1000 pid=18183 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 18:29:21 ORION-PC dbus-daemon[2555]: [session uid=1000 pid=2555] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.82' (uid=1000 pid=18183 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 18:29:21 ORION-PC dbus-daemon[2555]: [session uid=1000 pid=2555] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.82' (uid=1000 pid=18183 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 18:29:21 ORION-PC dbus-daemon[2555]: [session uid=1000 pid=2555] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.82' (uid=1000 pid=18183 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 18:29:21 ORION-PC dbus-daemon[1252]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.104' (uid=1000 pid=18183 comm="/usr/lib/vmware/bin/vmware ")
Apr 29 18:52:21 ORION-PC systemd[2537]: Started VMware Workstation.
Apr 29 18:57:33 ORION-PC systemd[2537]: app-vmware\x2dworkstation-83b2fe6946fb4d5caa6d93063625b805.scope: Succeeded.
Apr 29 18:57:33 ORION-PC systemd[2537]: app-vmware\x2dworkstation-83b2fe6946fb4d5caa6d93063625b805.scope: Consumed 8.509s CPU time.
Apr 29 18:58:30 ORION-PC systemd[2537]: Started VMware Workstation.
Apr 29 19:37:39 ORION-PC systemd[2537]: app-vmware\x2dworkstation-0411c073179b4666bf54a9a3e1336148.scope: Succeeded.
Apr 29 19:37:39 ORION-PC systemd[2537]: app-vmware\x2dworkstation-0411c073179b4666bf54a9a3e1336148.scope: Consumed 1min 9.223s CPU time.
Apr 29 19:54:58 ORION-PC systemd[2537]: Started VMware Workstation.

[Dayworker]

Das Problem ist, daß VMware immer noch mit "System-V" als Startdamon hantiert und die meisten Distris sich seit längerem für "systemd" entschieden haben. Ich würde daher das Problem direkt im VMTN posten, damit VMware langsam mal eine "native systemd unit" generiert und mitliefert.

[Forentroll]

Danke für die bisherige Hilfe.

Hab das jetzt mal im VMTN gepostet.

https://communities.vmware.com/t5/VMware-Workstation-Pro/VM-ain-t-to-play-after-rebooting-host/td-p/2844763

[Saurier74]

Eine Neuinstallation von Workstation ist nicht notwendig. Für openSUSE Leap 15.3 habe ich folgende Lösung gefunden.
Über Yast -System - Dienste-Verwaltung zu "vmware" scrollen und markieren. Anschließend links unten den Button "Starten" drücken und vmware aktivieren. Das genügt.
Die Funktion Startmodus "beim Systemstart" geht leider nicht.
Dr. Karl-Eberhard Wagner