Difference between revisions of "VMware"

From ArchWiki
Jump to: navigation, search
m (Removed systemdctl examples)
m (Installation)
(36 intermediate revisions by 6 users not shown)
Line 5: Line 5:
 
[[zh-CN:VMware]]
 
[[zh-CN:VMware]]
 
{{Article summary start}}
 
{{Article summary start}}
{{Article summary text|This article will explain how to install and configure VMware Workstation/Player in Arch.}}
+
{{Article summary text|This article will explain how to install and configure VMware Workstation/Player (Plus) in Arch.}}
 
{{Article summary heading|Related}}
 
{{Article summary heading|Related}}
 
{{Article summary wiki|Installing Arch Linux in VMware}}
 
{{Article summary wiki|Installing Arch Linux in VMware}}
Line 16: Line 16:
  
 
This article is about installing VMware in Arch Linux; you may also be interested in [[Installing Arch Linux in VMware]].
 
This article is about installing VMware in Arch Linux; you may also be interested in [[Installing Arch Linux in VMware]].
{{Note|This article supports '''only''' the latest major VMware versions, meaning VMware Workstation 9 and VMware Player 5.}}
+
{{Note|This article supports '''only''' the latest major VMware versions, meaning VMware Workstation 10 and VMware Player (Plus) 6.}}
  
 
== Installation ==
 
== Installation ==
  
{{Note| VMware Workstation/Player will '''not''' be manageable with pacman as the files are not installed with it.}}
+
{{Note|VMware Workstation/Player (Plus) will '''not''' be manageable with pacman as the files are not installed with it.}}
  
'''1.''' Download the latest  [http://www.vmware.com/products/workstation/overview.html VMware Workstation] or [http://www.vmware.com/products/player/overview.html VMware Player] (you may also try the [http://communities.vmware.com/community/vmtn/beta testing (Beta/RC) versions]).
+
'''1.''' Download the latest  [http://www.vmware.com/products/workstation VMware Workstation] or [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 VMware Player (Plus)] (you may also try the [https://communities.vmware.com/community/vmtn/beta testing (Beta/RC) versions]).
  
 
'''2.''' Start the installation ({{Ic|--console}} uses terminal instead of the GUI):
 
'''2.''' Start the installation ({{Ic|--console}} uses terminal instead of the GUI):
Line 28: Line 28:
 
  # ./VMware-''edition''-''version''.''release''.''architecture''.bundle --console
 
  # ./VMware-''edition''-''version''.''release''.''architecture''.bundle --console
  
'''3.''' Read and accept the EULA to continue.
+
{{Note|To ignore fatal errors use {{ic|--ignore-errors}} or {{ic|-I}}.}}
  
'''4.''' Set {{ic|System service scripts directory}} to {{ic|/etc/init.d}}.
+
'''3.''' Read and accept the main application and the [https://www.vmware.com/support/developer/ovf/ OVF Tool component] EULAs to continue.
  
'''5.''' (Optional) If Eclipse is installed, enter the directory path to the Integrated Virtual Debugger.
+
'''4.''' (optional) Enter license key.
  
'''6.''' You will now get an error about the {{ic|"rc*.d style init script directories"}} not being set. This can, however, be safely ignored.
+
'''5.''' During the install you will get an error about {{ic|"No rc*.d style init script directories"}} being given to the installer. This can, however, be safely ignored since Arch now uses [[systemd]].
  
 
== Configuration ==
 
== Configuration ==
Line 41: Line 41:
  
 
{{Note|Ensure you have installed the correct headers required for building the modules ({{Pkg|linux}} from {{ic|[core]}} uses {{Pkg|linux-headers}}).}}
 
{{Note|Ensure you have installed the correct headers required for building the modules ({{Pkg|linux}} from {{ic|[core]}} uses {{Pkg|linux-headers}}).}}
 
=== Module tool paths ===
 
 
{{Note|
 
* This is for people who don't have {{Pkg|filesystem}} [https://mailman.archlinux.org/pipermail/arch-dev-public/2013-May/024908.html 2013.05-1].
 
* Before updating make sure you have [[#Uninstallation|removed any deprecated symlinks from /sbin]].}}
 
 
'''7.''' Until {{Pkg|filesystem}} is updated to ''2013.05-1'' the {{ic|module tool paths}} of certain Workstation scripts need to be pointed to {{ic|/usr/bin/}} instead of {{ic|/sbin/}}. These include the service script in {{ic|/etc/init.d/}} and some other ones in {{ic|/usr/bin/}}.
 
 
* For Workstation:
 
# perl -p -i -e 's|/sbin/(?!modprobe)|/usr/bin/|g' /etc/init.d/vmware /usr/bin/vm-support /usr/bin/vmplayer /usr/bin/vmware /usr/bin/vmware-hostd /usr/bin/vmware-wssc-adminTool
 
 
* For Player:
 
# perl -p -i -e 's|/sbin/(?!modprobe)|/usr/bin/|g' /etc/init.d/vmware /usr/bin/vm-support /usr/bin/vmplayer
 
  
 
=== VMware module patches and installation ===
 
=== VMware module patches and installation ===
  
VMware Workstation 9 and Player 5 both support kernels up to 3.9.
+
VMware Workstation 10 and Player (Plus) 6 support kernels up to 3.11.
{{Note|
+
* This section is currently useful only for VMware Workstation and Player lower than 9.0.2 and 5.0.2, respectively.
+
* Due to different VMware versions, you may need to set the {{ic|vmreqver}} or {{ic|plreqver}} variable for VMware Workstation or Player respectively in the {{ic|patch-modules_3.X.0.sh}} script.
+
}}
+
 
+
The following patches will also install the modules afterwards by executing {{ic|# vmware-modconfig --console --install-all}}.
+
 
+
==== 3.7 kernels and up ====
+
 
+
With the arrival of 3.7 the directory structure of the uapi sources (and thus the headers) has [http://lkml.org/lkml/2012/10/14/281 changed]. The missing kernel header {{ic|version.h}} can be [http://rglinuxtech.com/?p=562 symlinked] with:
+
# ln -s /usr/src/linux-'''$(uname -r)'''/include/generated/uapi/linux/version.h /usr/src/linux-'''$(uname -r)'''/include/linux/
+
You can replace "'''{{ic|$(uname -r)}}'''" with any kernel not currently running.
+
{{Note|You will need to redo this upon every kernel update.}}
+
 
+
==== 3.8 / 3.9 kernels ====
+
 
+
In addition to the header symlink outlined above 3.8/3.9 kernels also need [http://communities.vmware.com/thread/432897 this] (packaged together with the script in [https://github.com/willysr/SlackHacks/tree/master/vmware/vmware-3.8 here]):
+
 
+
$ cd /tmp
+
$ curl -O https://raw.github.com/willysr/SlackHacks/master/vmware/vmware-3.8/vmware9.0.1_kernel3.8.zip
+
$ bsdtar -xvf vmware9.0.1_kernel3.8.zip
+
# ./patch-modules_3.8.0.sh
+
 
+
==== 3.5 / 3.6 / 3.7 kernels ====
+
 
+
A change in the format of the kernel exception table introduced back in [http://repo.or.cz/w/linux-2.6.git/commit/706276543b699d80f546e45f8b12574e7b18d952 April] affecting the {{ic|vmmon}} module is known to cause crashes in [http://communities.vmware.com/thread/400616 Fedora guests]. The patch [http://communities.vmware.com/message/2092356#2092356 here] creates a portable exception table (packaged together with the script [http://communities.vmware.com/message/2103172#2103172 in here], which will also reload the {{ic|vmmon}} module):
+
 
+
$ cd /tmp
+
$ curl -O http://communities.vmware.com/servlet/JiveServlet/download/2103172-94260/vmware9_kernel35_patch.tar.bz2
+
$ tar -xvf --strip-components=1 vmware9_kernel35_patch.tar.bz2  # The "--strip-components=1" flag extracts the files only
+
# ./patch-modules_3.5.0.sh
+
  
 
=== Systemd service ===
 
=== Systemd service ===
  
'''8.''' (Optional) Instead of using {{ic|<nowiki># /etc/init.d/vmware {start|stop|status|restart}</nowiki>}} directly to manage the services you may also create a {{ic|.service}} file (or [http://communities.vmware.com/docs/DOC-20855 files]):
+
'''6.''' (Optional) Instead of using {{ic|<nowiki># /etc/init.d/vmware {start|stop|status|restart}</nowiki>}} directly to manage the services you may also create a {{ic|.service}} file (or [http://communities.vmware.com/docs/DOC-20855 files]):
  
 
{{hc|/etc/systemd/system/vmware.service|
 
{{hc|/etc/systemd/system/vmware.service|
Line 110: Line 65:
 
}}
 
}}
  
To start the [[daemon]] on boot, enable the [[systemd]] service '''vmware'''.
+
To start the [[daemon]] on boot, enable the [[systemd]] service {{ic|vmware}}.
  
 
== Launching the application ==
 
== Launching the application ==
  
'''9.''' Now, open your VMware Workstation ({{Ic|vmware}} in the console) or VMware Player ({{Ic|vmplayer}} in the console) to configure & use!
+
'''7.''' Now, open your VMware Workstation ({{Ic|vmware}} in the console) or VMware Player (Plus) ({{Ic|vmplayer}} in the console) to configure & use!
  
{{Tip|To (re)build the modules, use:
+
{{Tip|To (re)build the modules from terminal, use:
 
  # vmware-modconfig --console --install-all
 
  # vmware-modconfig --console --install-all
 
}}
 
}}
Line 122: Line 77:
 
== Tips and tricks ==
 
== Tips and tricks ==
  
=== Entering the Workstation License Key from terminal ===
+
=== Entering the Workstation License Key ===
 +
 
 +
==== From terminal ====
  
 
  # /usr/lib/vmware/bin/vmware-vmx-debug --new-sn XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
 
  # /usr/lib/vmware/bin/vmware-vmx-debug --new-sn XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
  
 
Where {{ic|XXXXX-XXXXX-XXXXX-XXXXX-XXXXX}} is your license key.
 
Where {{ic|XXXXX-XXXXX-XXXXX-XXXXX-XXXXX}} is your license key.
 +
 +
{{Note|The {{ic|-debug}} binary informs the user of an incorrect license.}}
 +
 +
==== From GUI ====
 +
 +
If the above doesn't work, you can try:
 +
 +
# /usr/lib/vmware/bin/vmware-enter-serial
  
 
=== Extracting the VMware BIOS ===
 
=== Extracting the VMware BIOS ===
Line 218: Line 183:
  
 
all: $(LOCAL_MODULES)
 
all: $(LOCAL_MODULES)
        mkdir -p modules/
+
mkdir -p modules/
        mv *.ko modules/
+
mv *.ko modules/
        rm -rf $(DEST)
+
rm -rf $(DEST)
        depmod
+
depmod
  
/usr/src/linux-$(KERNEL)/include/linux/version.h:
+
/usr/src/linux-$(KERNEL)/include/linux/version.h:
        ln -s /usr/src/linux-$(KERNEL)/include/generated/uapi/linux/version.h /usr/src/linux-$(KERNEL)/include/linux/
+
ln -s /usr/src/linux-$(KERNEL)/include/generated/uapi/linux/version.h /usr/src/linux-$(KERNEL)/include/linux/
  
 
%.ko: /usr/src/linux-$(KERNEL)/include/linux/version.h
 
%.ko: /usr/src/linux-$(KERNEL)/include/linux/version.h
        vmware-modconfig --console --build-mod -k $(KERNEL) $* $(GCC) $(HEADERS) vmware/
+
vmware-modconfig --console --build-mod -k $(KERNEL) $* $(GCC) $(HEADERS) vmware/
        cp -f $(DEST)/$*.ko .
+
cp -f $(DEST)/$*.ko .
  
 
clean:
 
clean:
        rm -rf modules/
+
rm -rf modules/
 +
 
 +
 
 
}}
 
}}
  
Line 258: Line 225:
 
  Please make sure that the kernel module `vmmon' is loaded.
 
  Please make sure that the kernel module `vmmon' is loaded.
  
This means that at least the {{Ic|vmmon}} VMware service is not running. If using the service file from [[#Systemd_service|step 8.]] all VMware services can be started with:
+
This means that at least the {{Ic|vmmon}} VMware service is not running. If using the [[systemd]] service from [[#Systemd_service|step 8.]] it should be restarted.
# systemctl start vmware
+
  
 
=== Kernel headers for version 3.x-xxxx were not found. If you installed them[...] ===
 
=== Kernel headers for version 3.x-xxxx were not found. If you installed them[...] ===
Line 270: Line 236:
  
 
{{Tip|Also handled by {{AUR|vmware-patch}}.}}
 
{{Tip|Also handled by {{AUR|vmware-patch}}.}}
 
==== 1) The {{ic|vmware-USBArbitrator}} script is missing ====
 
  
 
For some reason, some installations are missing the {{ic|vmware-USBArbitrator}} script. To readd it manually see [https://bbs.archlinux.org/viewtopic.php?pid=1003117#p1003117 this forum post].
 
For some reason, some installations are missing the {{ic|vmware-USBArbitrator}} script. To readd it manually see [https://bbs.archlinux.org/viewtopic.php?pid=1003117#p1003117 this forum post].
Line 278: Line 242:
 
  $ ./VMware-''edition''-''version''.''release''.''architecture''.bundle --extract /tmp/vmware-bundle
 
  $ ./VMware-''edition''-''version''.''release''.''architecture''.bundle --extract /tmp/vmware-bundle
 
  # cp /tmp/vmware-bundle/vmware-usbarbitrator/etc/init.d/vmware-USBArbitrator /etc/init.d/
 
  # cp /tmp/vmware-bundle/vmware-usbarbitrator/etc/init.d/vmware-USBArbitrator /etc/init.d/
 
==== 2) The {{ic|vmware-usbarbitrator}} binary is segfaulting ====
 
 
This could also mean that the {{ic|vmware-usbarbitrator}} binary called in the script is [https://bbs.archlinux.org/viewtopic.php?pid=1156789 segfaulting]:
 
{{hc|# vmware-usbarbitrator|
 
Pipe unexpectedly closed.
 
}}
 
{{hc|# vmware-usbarbitrator --info -f|
 
VTHREAD initialize main thread 2 "usbArb" pid 6426
 
Segmentation fault
 
}}
 
 
This is caused by an empty {{ic|/etc/arch-release}} (owned by {{pkg|filesystem}}). It is used by the service to alter its behavior based on the distribution's release version.
 
 
To fix it, add a version string in the form of {{ic|''year''.''month''(.''day'')}} (e.g. {{ic|[https://www.archlinux.org/download/ 2013.04.01]}}).
 
 
=== process XXXX: Attempt to remove filter function [...] ===
 
 
The full error is, for example:
 
process 6094: Attempt to remove filter function 0xadcc96f0 user data 0xb795aba0, but no such filter has been added
 
  D-Bus not built with -rdynamic so unable to print a backtrace
 
Aborted
 
 
This means that the hal daemon is not running. Install {{AUR|hal}} from the [[AUR]] and start the daemon with:
 
# hald
 
  
 
=== The installer fails to start ===
 
=== The installer fails to start ===
Line 311: Line 250:
 
=== Incorrect login/password when trying to access VMware remotely ===
 
=== Incorrect login/password when trying to access VMware remotely ===
  
VMware Workstation 9 provides the possibility to remotely manage Shared VMs through the {{ic|vmware-workstation-server}} service. However, this will fail with the error {{ic|"incorrect username/password"}} due to incorrect PAM configuration of the {{ic|vmware-authd}} service. To fix it, edit {{ic|/etc/pam.d/vmware-authd}} like this:
+
VMware Workstation 10 provides the possibility to remotely manage Shared VMs through the {{ic|vmware-workstation-server}} service. However, this will fail with the error {{ic|"incorrect username/password"}} due to incorrect PAM configuration of the {{ic|vmware-authd}} service. To fix it, edit {{ic|/etc/pam.d/vmware-authd}} like this:
  
 
{{hc|/etc/pam.d/vmware-authd|
 
{{hc|/etc/pam.d/vmware-authd|
 
#%PAM-1.0
 
#%PAM-1.0
auth    required      pam_unix.so
+
auth    ''required      pam_unix.so''
account  required      pam_unix.so
+
account  ''required      pam_unix.so''
password required      pam_permit.so
+
password ''required      pam_permit.so''
session  required      pam_unix.so
+
session  ''required      pam_unix.so''
 
}}
 
}}
  
and restart ''vmware'' [[systemd]] service.
+
and restart the {{ic|vmware}} [[systemd]] service.
  
 
Now you can connect to the server with the credentials provided during the installation.
 
Now you can connect to the server with the credentials provided during the installation.
Line 336: Line 275:
 
# Open the {{ic|''Virtual machine name''.vmx}} config file of the VM in a text editor, located under {{ic|~/vmware/''Virtual machine name''/}}, and edit the {{ic|sound.fileName}} field, e.g.: {{ic|1=sound.fileName="surround51:CARD=Live,DEV=0"}}. Ensure that it also reads {{ic|1=sound.autodetect="FALSE"}}.
 
# Open the {{ic|''Virtual machine name''.vmx}} config file of the VM in a text editor, located under {{ic|~/vmware/''Virtual machine name''/}}, and edit the {{ic|sound.fileName}} field, e.g.: {{ic|1=sound.fileName="surround51:CARD=Live,DEV=0"}}. Ensure that it also reads {{ic|1=sound.autodetect="FALSE"}}.
 
# Resume/Power on the VM.
 
# Resume/Power on the VM.
 +
 +
=== Kernel-based Virtual Machine (KVM) is running ===
 +
To disable {{ic|KVM}} on boot, you can use something like:
 +
       
 +
{{hc|/etc/modprobe.d/vmware.conf|
 +
blacklist kvm
 +
blacklist kvm-amd  # For AMD CPUs
 +
blacklist kvm-intel # For Intel CPUs
 +
}}
  
 
== Uninstallation ==
 
== Uninstallation ==
  
 
To uninstall VMware you need the product name (either {{ic|vmware-workstation}} or {{ic|vmware-player}}). To list all the installed products:
 
To uninstall VMware you need the product name (either {{ic|vmware-workstation}} or {{ic|vmware-player}}). To list all the installed products:
  # vmware-installer -l
+
  $ vmware-installer -l
  
 
and uninstall with:
 
and uninstall with:
 
  # vmware-installer -u ''vmware-product''
 
  # vmware-installer -u ''vmware-product''
  
Manually included symlinks have to be removed manually in {{ic|/sbin}}:
+
Remember to also disable and remove the {{ic|vmware}} service:
# rm /sbin/insmod /sbin/lsmod /sbin/modinfo /sbin/rmmod
+
 
+
Remember to also disable and remove the '''vmware''' service:
+
 
  # systemctl disable vmware
 
  # systemctl disable vmware
 
  # rm /etc/systemd/system/vmware.service
 
  # rm /etc/systemd/system/vmware.service
  
You may also want to have a look at the kernel directories in {{ic|/usr}} for any leftovers. The now unnecessary [[#3.7 kernels and up]] step leaves header directories in {{ic|/usr/src/}} (full path: {{ic|/usr/src/linux-''[kernel name]''/include/linux/version.h}}).
+
You may also want to have a look at the module directories in {{ic|/usr/lib/modules/''[kernel name]''/misc/}} for any leftovers.
 
+
The module directories can be found in {{ic|/usr/lib/modules/''[kernel name]''/misc/}}.
+

Revision as of 10:43, 5 October 2013

Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary end

This article is about installing VMware in Arch Linux; you may also be interested in Installing Arch Linux in VMware.

Note: This article supports only the latest major VMware versions, meaning VMware Workstation 10 and VMware Player (Plus) 6.

Installation

Note: VMware Workstation/Player (Plus) will not be manageable with pacman as the files are not installed with it.

1. Download the latest VMware Workstation or VMware Player (Plus) (you may also try the testing (Beta/RC) versions).

2. Start the installation (--console uses terminal instead of the GUI):

$ chmod +x VMware-edition-version.release.architecture.bundle
# ./VMware-edition-version.release.architecture.bundle --console
Note: To ignore fatal errors use --ignore-errors or -I.

3. Read and accept the main application and the OVF Tool component EULAs to continue.

4. (optional) Enter license key.

5. During the install you will get an error about "No rc*.d style init script directories" being given to the installer. This can, however, be safely ignored since Arch now uses systemd.

Configuration

Tip: There is also a package called vmware-patchAUR in the AUR with the intention of trying to automate this section (it also supports older VMware versions).
Note: Ensure you have installed the correct headers required for building the modules (linux from [core] uses linux-headers).

VMware module patches and installation

VMware Workstation 10 and Player (Plus) 6 support kernels up to 3.11.

Systemd service

6. (Optional) Instead of using # /etc/init.d/vmware {start|stop|status|restart} directly to manage the services you may also create a .service file (or files):

/etc/systemd/system/vmware.service
[Unit]
Description=VMware daemon

[Service]
ExecStart=/etc/init.d/vmware start
ExecStop=/etc/init.d/vmware stop
PIDFile=/var/lock/subsys/vmware
TimeoutSec=0
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

To start the daemon on boot, enable the systemd service vmware.

Launching the application

7. Now, open your VMware Workstation (vmware in the console) or VMware Player (Plus) (vmplayer in the console) to configure & use!

Tip: To (re)build the modules from terminal, use:
# vmware-modconfig --console --install-all

Tips and tricks

Entering the Workstation License Key

From terminal

# /usr/lib/vmware/bin/vmware-vmx-debug --new-sn XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Where XXXXX-XXXXX-XXXXX-XXXXX-XXXXX is your license key.

Note: The -debug binary informs the user of an incorrect license.

From GUI

If the above doesn't work, you can try:

# /usr/lib/vmware/bin/vmware-enter-serial

Extracting the VMware BIOS

$ objcopy /usr/lib/vmware/bin/vmware-vmx -O binary -j bios440 --set-section-flags bios440=a bios440.rom.Z
$ perl -e 'use Compress::Zlib; my $v; read STDIN, $v, '$(stat -c%s "./bios440.rom.Z")'; $v = uncompress($v); print $v;' < bios440.rom.Z > bios440.rom

Using the modified BIOS

If and when you decide to modify the extracted BIOS you can make your virtual machine use it by moving it to ~/vmware/Virtual machine name:

$ mv bios440.rom ~/vmware/Virtual machine name/

then adding the name to the Virtual machine name.vmx file:

~/vmware/Virtual machine name/Virtual machine name.vmx
bios440.filename = "bios440.rom"

Copy-On-Write (CoW)

CoW comes with some advantages, but can negatively affect performance with large files that have small random writes (e.g. database files and virtual machine images):

$ chattr +C ~/vmware/Virtual machine name/Virtual machine name.vmx
Note: From the chattr man page: "For btrfs, the C flag should be set only on new or empty files. If set on a file which already has data blocks, it is undefined when the blocks assigned to the file will be fully stable. If set on a directory, only new files will be affected."

Using DKMS to manage the modules

The Dynamic Kernel Module Support (DKMS) can be used to manage Workstation modules and to void from re-running vmware-modconfig each time the kernel changes. The following example uses a custom Makefile to compile and install the modules through vmware-modconfig. Afterwards they are removed from the current kernel tree.

Preparation

First install dkms from the official repositories.

Then create a source directory for the Makefile and the dkms.conf:

# mkdir /usr/src/vmware-modules-9/

Build configuration

Fetch the files from Git or use the ones below.

1) Using Git
$ cd /tmp
$ git clone git://github.com/djod4556/dkms-workstation.git
# cp /tmp/dkms-workstation.git/Makefile /tmp/dkms-workstation.git/dkms.conf /usr/src/vmware-modules-9/
2) Manual setup

The dkms.conf describes the module names and the compilation/installation procedure. AUTOINSTALL="yes" tells the modules to be recompiled/installed automatically each time:

/usr/src/vmware-modules-9/dkms.conf
PACKAGE_NAME="vmware-modules"
PACKAGE_VERSION="9"

MAKE[0]="make all"
CLEAN="make clean"

BUILT_MODULE_NAME[0]="vmmon"
BUILT_MODULE_LOCATION[0]="modules"

BUILT_MODULE_NAME[1]="vmnet"
BUILT_MODULE_LOCATION[1]="modules"

BUILT_MODULE_NAME[2]="vmblock"
BUILT_MODULE_LOCATION[2]="modules"

BUILT_MODULE_NAME[3]="vmci"
BUILT_MODULE_LOCATION[3]="modules"

BUILT_MODULE_NAME[4]="vsock"
BUILT_MODULE_LOCATION[4]="modules"

DEST_MODULE_LOCATION[0]="/extra/vmware"
DEST_MODULE_LOCATION[1]="/extra/vmware"
DEST_MODULE_LOCATION[2]="/extra/vmware"
DEST_MODULE_LOCATION[3]="/extra/vmware"
DEST_MODULE_LOCATION[4]="/extra/vmware"

AUTOINSTALL="yes"

and now the Makefile:

/usr/src/vmware-modules-9/Makefile
KERNEL := $(KERNELRELEASE)
HEADERS := /usr/src/linux-$(KERNEL)/include
GCC := $(shell vmware-modconfig --console --get-gcc)
DEST := /lib/modules/$(KERNEL)/vmware

TARGETS := vmmon vmnet vmblock vmci vsock

LOCAL_MODULES := $(addsuffix .ko, $(TARGETS))

all: $(LOCAL_MODULES)
	mkdir -p modules/
	mv *.ko modules/
	rm -rf $(DEST)
	depmod

	/usr/src/linux-$(KERNEL)/include/linux/version.h:
	ln -s /usr/src/linux-$(KERNEL)/include/generated/uapi/linux/version.h /usr/src/linux-$(KERNEL)/include/linux/

%.ko: /usr/src/linux-$(KERNEL)/include/linux/version.h
	vmware-modconfig --console --build-mod -k $(KERNEL) $* $(GCC) $(HEADERS) vmware/
	cp -f $(DEST)/$*.ko .

clean:
	rm -rf modules/

Installation

The modules can then be registered:

# dkms -m vmware-modules -v 9 -k $(uname -r) add

built:

# dkms -m vmware-modules -v 9 -k $(uname -r) build

and installed:

# dkms -m vmware-modules -v 9 -k $(uname -r) install

If everything went well, the modules will now be recompiled automatically the next time the kernel changes.

Troubleshooting

Could not open /dev/vmmon: No such file or directory.

The full error is:

Could not open /dev/vmmon: No such file or directory.
Please make sure that the kernel module `vmmon' is loaded.

This means that at least the vmmon VMware service is not running. If using the systemd service from step 8. it should be restarted.

Kernel headers for version 3.x-xxxx were not found. If you installed them[...]

Install the headers (linux-headers).

Note: Upgrading the kernel and the headers will require you to boot to the new kernel to match the version of the headers. This is a relatively common error.

USB devices not recognized

Tip: Also handled by vmware-patchAUR.

For some reason, some installations are missing the vmware-USBArbitrator script. To readd it manually see this forum post.

You may also manually extract the VMware bundle and copy the vmware-USBArbitrator script from destination folder/vmware-usbarbitrator/etc/init.d/ to /etc/init.d/:

$ ./VMware-edition-version.release.architecture.bundle --extract /tmp/vmware-bundle
# cp /tmp/vmware-bundle/vmware-usbarbitrator/etc/init.d/vmware-USBArbitrator /etc/init.d/

The installer fails to start

If you just get back to the prompt when opening the .bundle, then you probably have a deprecated or broken version of the VMware installer and you should remove it (you may also refer to the uninstallation section of this article):

# rm -r /etc/vmware-installer

Incorrect login/password when trying to access VMware remotely

VMware Workstation 10 provides the possibility to remotely manage Shared VMs through the vmware-workstation-server service. However, this will fail with the error "incorrect username/password" due to incorrect PAM configuration of the vmware-authd service. To fix it, edit /etc/pam.d/vmware-authd like this:

/etc/pam.d/vmware-authd
#%PAM-1.0
auth     required       pam_unix.so
account  required       pam_unix.so
password required       pam_permit.so
session  required       pam_unix.so

and restart the vmware systemd service.

Now you can connect to the server with the credentials provided during the installation.

Note: libxslt may be required for starting virtual machines.

Issues with ALSA output

The following instructions from Bankim Bhavsar's wiki show how to manually adjust the ALSA output device in a VMware .vmx file. This might help with quality issues or with enabling proper HD audio output:

  1. Suspend/Power off the VM.
  2. Run aplay -L
  3. If you are interested in playing 5.1 surround sound from the guest, look for surround51:CARD=vendor-name,DEV=num. If you are experiencing quality issues, look out for a line starting with front.
  4. Open the Virtual machine name.vmx config file of the VM in a text editor, located under ~/vmware/Virtual machine name/, and edit the sound.fileName field, e.g.: sound.fileName="surround51:CARD=Live,DEV=0". Ensure that it also reads sound.autodetect="FALSE".
  5. Resume/Power on the VM.

Kernel-based Virtual Machine (KVM) is running

To disable KVM on boot, you can use something like:

/etc/modprobe.d/vmware.conf
blacklist kvm
blacklist kvm-amd   # For AMD CPUs
blacklist kvm-intel # For Intel CPUs

Uninstallation

To uninstall VMware you need the product name (either vmware-workstation or vmware-player). To list all the installed products:

$ vmware-installer -l

and uninstall with:

# vmware-installer -u vmware-product

Remember to also disable and remove the vmware service:

# systemctl disable vmware
# rm /etc/systemd/system/vmware.service

You may also want to have a look at the module directories in /usr/lib/modules/[kernel name]/misc/ for any leftovers.