From: AnErrupTion <AnErrupTion@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [Package Request] VMWare
Date: Mon, 08 May 2023 21:39:09 +0200 [thread overview]
Message-ID: <20230508193909.jcSRCu5DVX2fiuj7tuTPV1AFnRPtKcbUyOkYlyFJAyk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33557@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]
New comment by AnErrupTion on void-packages repository
https://github.com/void-linux/void-packages/issues/33557#issuecomment-1538937175
Comment:
Running ``vmware-modconfig`` manually won't work either as it requires systemd. However, I've found a workaround to all of this which allows VMware Workstation to run without systemd. Here are the steps:
1. Download and run the VMware Workstation installer:
``# ./VMware-Workstation-Full-17.0.0-20800274.x86_64.bundle``
If it doesn't detect systemd, the installer will put shell scripts under ``/etc/init.d/``.
2. Now, we need to compile the kernel modules. Fortunately, someone has made a GitHub repository with the source code for each version of VMware Workstation, starting from version 12.5.x. We can then compile the kernel modules like so:
```
$ git clone https://github.com/mkubecek/vmware-host-modules -b workstation-17.0.2
$ cd vmware-host-modules
$ make
# make install
```
Note that the kernel modules will not be using DKMS, so you'll have to recompile them manually after each kernel update.
3. Reboot so the kernel modules can load.
4. Finally, we need to start the vmware and vmware-USBArbitrator services, like so (you may start them automatically at boot):
```
# sh /etc/init.d/vmware start
# sh /etc/init.d/vmware-USBArbitrator start
```
6. And we're done! You should now be able to launch and use VMware Workstation. :D
prev parent reply other threads:[~2023-05-08 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 7:57 [ISSUE] " Animeshz
2021-12-20 14:43 ` Codythedragonrude
2023-05-08 19:37 ` AnErrupTion
2023-05-08 19:38 ` AnErrupTion
2023-05-08 19:39 ` AnErrupTion [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230508193909.jcSRCu5DVX2fiuj7tuTPV1AFnRPtKcbUyOkYlyFJAyk@z \
--to=anerruption@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).