Difference between revisions of "VMware"

From ArchWiki
Jump to: navigation, search
(VMware module patches and installation)
(Installation: clarify that this is only needed when using the --console flag)
 
(347 intermediate revisions by 64 users not shown)
Line 1: Line 1:
[[Category:Virtualization]]
+
[[Category:Hypervisors]]
 
[[it:VMware]]
 
[[it:VMware]]
 +
[[ja:VMware]]
 
[[ru:VMware]]
 
[[ru:VMware]]
 
[[uk:VMware]]
 
[[uk:VMware]]
 
[[zh-CN:VMware]]
 
[[zh-CN:VMware]]
{{Article summary start}}
+
{{Related articles start}}
{{Article summary text|This article will explain how to install and configure VMware Workstation/Player in Arch.}}
+
{{Related|:Category:Hypervisors}}
{{Article summary heading|Related}}
+
{{Related|VMware/Installing Arch as a guest}}
{{Article summary wiki|Installing Arch Linux in VMware}}
+
{{Related|Moving an existing install into (or out of) a virtual machine}}
{{Article summary wiki|VirtualBox}}
+
{{Related articles end}}
{{Article summary wiki|KVM}}
+
{{Article summary wiki|QEMU}}
+
{{Article summary wiki|Xen}}
+
{{Article summary wiki|Moving an existing install into (or out of) a virtual machine}}
+
{{Article summary end}}
+
  
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 [[VMware/Installing Arch as a guest]].
{{Note|This article supports '''only''' the latest major VMware versions, meaning VMware Workstation 9 and VMware Player 5.}}
+
{{Note|
 +
*This article is about the latest major VMware versions, meaning VMware Workstation Pro and Player 12.5.
 +
*For older versions, use the {{AUR|vmware-patch}} package.
 +
}}
  
==Installation==
+
== Installation ==
  
{{Note| VMware Workstation/Player will '''not''' be manageable with pacman as the files are not installed with it.}}
+
[[Install]] the correct dependencies:
 +
*{{pkg|fuse}} - for ''vmware-vmblock-fuse''
 +
*{{pkg|gksu}} - for root operations (memory allocations, registering license, etc.)
 +
*{{pkg|gtkmm}} - for the GUI
 +
*{{pkg|linux-headers}} - for module compilation
 +
*{{AUR|ncurses5-compat-libs}} - needed by the {{ic|--console}} installer
  
'''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]).
+
Download the latest [https://www.vmware.com/go/tryworkstation VMware Workstation Pro] or [https://www.vmware.com/go/downloadplayer Player] (or a [https://communities.vmware.com/community/vmtn/beta beta] version, if available).
  
'''2.''' Ensure the {{Ic|linux-headers}} package from {{Ic|[core]}} is installed using pacman.
+
Start the installation:
 +
# sh VMware-''edition''-''version''.''release''.''architecture''.bundle
  
'''3.''' Start the installation ({{Ic|--console}} uses terminal instead of the GUI):
+
{{Tip|Some useful flags:
$ chmod +x VMware-<edition>-<version>.<release>.<architecture>.bundle
+
*{{ic|--eulas-agreed}} - Skip the EULAs
# ./VMware-<edition>-<version>.<release>.<architecture>.bundle --console
+
*{{ic|--console}} - Use the console UI.
 +
*{{ic|--custom}} - Allows changing the install directory to e.g. {{ic|/usr/local}} (make sure to update the {{ic|vmware-usbarbitrator.service}} paths in [[#systemd services]]).
 +
*{{ic|-I}}, {{ic|--ignore-errors}} - Ignore fatal errors.
 +
*{{ic|1=--set-setting=vmware-workstation serialNumber XXXXX-XXXXX-XXXXX-XXXXX-XXXXX}} - Set the serial number during install (good for scripted installs).
 +
*{{ic|--required}} - Only ask mandatory questions (results in silent install when combined with {{ic|--eulas-agreed}} and {{ic|--console}}).
 +
}}
  
'''4.''' Read & accept the EULA to continue.
+
For the {{ic|System service scripts directory}}, use {{ic|/etc/init.d}} (the default).
  
'''5.''' Set {{Ic|System service scripts directory}} to {{ic|/etc/init.d}}.
+
{{Note|During the installation you will get an error about {{ic|"No rc*.d style init script directories"}} being given. This can be safely ignored, since Arch uses [[systemd]].}}
  
'''6.''' (Optional) If Eclipse is installed, enter the directory path to the Integrated Virtual Debugger.
+
{{Tip|To (re)build the modules from terminal later on, use:
 +
# vmware-modconfig --console --install-all
 +
}}
  
'''7.''' You will now get an error about the {{ic|"rc*.d style init script directories"}} not being set. This can, however, be safely ignored.
+
== Configuration ==
  
==Configuration==
+
=== Kernel modules ===
  
{{Tip|There is also a package called {{AUR|vmware-patch}} in the [[Arch User Repository|AUR]] with the intention of trying to automate this section (it also supports older VMware versions).}}
+
VMware Workstation 12.5 supports kernels up to 4.8 out of the box.
  
===Module tool paths===
+
=== systemd services ===
'''7.''' The {{ic|module tool paths}} of certain Workstation scripts now 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/}}.
+
  
====1) A short-term solution====
+
''(Optional)'' Instead of using {{ic|/etc/init.d/vmware}} ({{ic|<nowiki>start|stop|status|restart</nowiki>}}) and {{ic|/usr/bin/vmware-usbarbitrator}} directly to manage the services, you may also use {{ic|.service}} files (also available in the {{AUR|vmware-systemd-services}} package, and also included in {{AUR|vmware-patch}}):
  
A short-term solution consists of editing the files directly. You will need to redo this upon every update.
+
{{hc|/etc/systemd/system/vmware.service|
 +
2=[Unit]
 +
Description=VMware daemon
 +
Requires=vmware-usbarbitrator.service
 +
Before=vmware-usbarbitrator.service
 +
After=network.target
  
* For Workstation:
+
[Service]
# 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
+
ExecStart=/etc/init.d/vmware start
 +
ExecStop=/etc/init.d/vmware stop
 +
PIDFile=/var/lock/subsys/vmware
 +
RemainAfterExit=yes
  
* For Player:
+
[Install]
# perl -p -i -e 's|/sbin/(?!modprobe)|/usr/bin/|g' /etc/init.d/vmware /usr/bin/vm-support /usr/bin/vmplayer
+
WantedBy=multi-user.target
 +
}}
  
====2) A long-term solution====
+
{{hc|/etc/systemd/system/vmware-usbarbitrator.service|
 +
2=[Unit]
 +
Description=VMware USB Arbitrator
 +
Requires=vmware.service
 +
After=vmware.service
  
You could also just create symlinks with:
+
[Service]
# for i in {ins,ls,rm}mod modinfo; do ln -s /usr/bin/$i /sbin/$i; done
+
ExecStart=/usr/bin/vmware-usbarbitrator
 +
ExecStop=/usr/bin/vmware-usbarbitrator --kill
 +
RemainAfterExit=yes
  
===VMware module patches and installation===
+
[Install]
Both VMware Workstation 9 and Player 5 support kernels up to 3.7. However, the required header {{ic|version.h}} was [http://lkml.org/lkml/2012/10/14/281 relocated] with 3.7 and needs to be [http://rglinuxtech.com/2012/11/18/vmware-9-0-1-not-so-clever-after-all/ symlinked].
+
WantedBy=multi-user.target
 +
}}
  
====3.8 kernels====
+
Add this service as well, if you want to connect to your VMware Workstation installation from another Workstation Server Console:
With the arrival of 3.7 the directory structure of the uapi sources (and thus the headers) has changed. The missing kernel header {{ic|version.h}} can be symlinked with:
+
# ln -s /usr/src/linux-$(uname -r)/include/generated/uapi/linux/version.h /usr/src/linux-$(uname -r)/include/linux/version.h
+
You can replace "{{ic|$(uname -r)}}" with any kernel not currently running.
+
And use [http://communities.vmware.com/thread/432897 this patch.]
+
  
====3.7 kernels====
+
{{hc|/etc/systemd/system/vmware-workstation-server.service|
With the arrival of 3.7 the directory structure of the uapi sources (and thus the headers) has changed. The missing kernel header {{ic|version.h}} can be symlinked with:
+
2=[Unit]
# ln -s /usr/src/linux-$(uname -r)/include/generated/uapi/linux/version.h /usr/src/linux-$(uname -r)/include/linux/version.h
+
Description=VMware Workstation Server
You can replace "{{ic|$(uname -r)}}" with any kernel not currently running.
+
Requires=vmware.service
 +
After=vmware.service
  
====3.5 / 3.6 kernels====
 
{{Note|Required only for VMWare Workstation 9.0.0 and Player 5.0.0}}
 
 
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]) and will also install the modules afterwards by executing {{ic|# vmware-modconfig --console --install-all}} (this 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 --strip-components=1 -xvf vmware9_kernel35_patch.tar.bz2  # The "--strip-components=1" flag extracts the files only
 
# ./patch-modules_3.5.0.sh
 
 
==Finishing up==
 
 
'''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]):
 
 
{{hc|/etc/systemd/system/vmware.service|
 
2=[Unit]
 
Description=VMware daemon
 
 
[Service]
 
[Service]
ExecStart=/etc/init.d/vmware start
+
ExecStart=/etc/init.d/vmware-workstation-server start
ExecStop=/etc/init.d/vmware stop
+
ExecStop=/etc/init.d/vmware-workstation-server stop
PIDFile=/var/lock/subsys/vmware
+
PIDFile=/var/lock/subsys/vmware-workstation-server
TimeoutSec=0
+
 
RemainAfterExit=yes
 
RemainAfterExit=yes
 +
 
[Install]
 
[Install]
 
WantedBy=multi-user.target
 
WantedBy=multi-user.target
 
}}
 
}}
  
To start the {{ic|.service}} on boot:
+
After which you can [[enable]] them on boot.
# systemctl enable vmware
+
  
'''9.''' Now, open your VMware Workstation ({{Ic|vmware}} in the console) or VMware Player ({{Ic|vmplayer}} in the console) to configure & use!
+
== Launching the application ==
  
{{Warning|When upgrading the kernel you '''will''' have to rebuild the VMware modules with the following command:
+
To open VMware Workstation Pro:
  # vmware-modconfig --console --install-all
+
  $ vmware
 +
 
 +
or Player:
 +
$ vmplayer
 +
 
 +
== Tips and tricks ==
  
Failure to do so may result in a system crash upon powering up virtual machines.}}
+
=== Entering the Workstation Pro license key ===
  
==Tips & Tricks==
+
==== 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.
  
===Extracting the VMware BIOS===
+
{{Note|The {{ic|-debug}} binary informs the user of an incorrect license.}}
 +
 
 +
==== From GUI ====
 +
 
 +
If the above does not 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
 
  $ 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
 
  $ 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====
+
=== Extracting the installer ===
If and when you decide to modify the extracted BIOS you can make your virtual machine use it by moving it to {{ic|~/vmware/<Virtual machine name>}}:
+
$ mv bios440.rom ~/vmware/<Virtual machine name>/
+
  
then adding the name to the {{Ic|<Virtual machine name>.vmx}} file:
+
To view the contents of the installer {{ic|.bundle}}:
{{hc|~/vmware/<Virtual machine name>/<Virtual machine name>.vmx|2=bios440.filename = "bios440.rom"}}
+
  
====Copy-On-Write (CoW)====
+
$ sh VMware-''edition''-''version''.''release''.''architecture''.bundle --extract ''/tmp/vmware-bundle/''
CoW comes with some advantages, but can negatively affect performance with large files that have small random writes. It is recomended to disable CoW for database files and virtual machine images. To disable CoW for the whole file system it should be mounted with the {{ic|nodatacow}} flag. To disable CoW for single files/directories:
+
  
$ chattr +C [file/directory path]
+
==== Using the modified BIOS ====
  
{{Note|1=From the [http://www.linuxhowtos.org/manpages/1/chattr.htm?print=-51 chattr man page]: ''"For btrfs, the {{ic|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."''}}
+
If and when you decide to modify the extracted BIOS you can make your virtual machine use it by moving it to {{ic|~/vmware/''Virtual_machine_name''}}:
 +
$ mv bios440.rom ~/vmware/''Virtual_machine_name''/
  
===Using DKMS to manage the modules===
+
then adding the name to the {{ic|''Virtual_machine_name''.vmx}} file:
The Dynamic Kernel Module Support (DKMS) can be used to manage Workstation modules and to void from re-running {{ic|vmware-modconfig}} each time the kernel changes. The following example uses a custom {{ic|Makefile}} to compile and install the modules through {{ic|vmware-modconfig}}. Afterwards they are removed from the current kernel tree.
+
{{hc|~/vmware/''Virtual_machine_name''/''Virtual_machine_name''.vmx|2=bios440.filename = "bios440.rom"}}
  
====Preparation====
+
=== Enable 3D graphics on Intel and Optimus ===
First install {{pkg|dkms}} from the [[Community repository]]:
+
# pacman -S dkms
+
  
then create a source directory for the {{ic|Makefile}} and the {{ic|dkms.conf}}.
+
Some graphics drivers are blacklisted by default, due to poor and/or unstable 3D acceleration. After enabling ''Accelerate 3D graphics'', the log may show something like:
# mkdir /usr/src/vmware-modules-9
+
  
====Build configuration====
+
  Disabling 3D on this host due to presence of Mesa DRI driverSet mks.gl.allowBlacklistedDrivers = TRUE to override.
Gather the files from git or use the ones described below:
+
  $ 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/
+
  
The {{ic|dkms.conf}} describes the module names and the compilation/installation procedure. {{ic|1=AUTOINSTALL="yes"}} tells the modules to be recompiled/installed automatically each time:
+
This means the following:
  
{{hc|/usr/src/vmware-modules-9/dkms.conf|
+
{{hc|~/.vmware/preferences|2=
2=PACKAGE_NAME="vmware-modules"
+
mks.gl.allowBlacklistedDrivers = TRUE
PACKAGE_VERSION="9"
+
}}
  
MAKE[0]="make all"
+
== Troubleshooting ==
CLEAN="make clean"
+
  
BUILT_MODULE_NAME[0]="vmmon"
+
=== /dev/vmmon not found ===
BUILT_MODULE_LOCATION[0]="modules"
+
  
BUILT_MODULE_NAME[1]="vmnet"
+
The full error is:
BUILT_MODULE_LOCATION[1]="modules"
+
  
BUILT_MODULE_NAME[2]="vmblock"
+
Could not open /dev/vmmon: No such file or directory.
BUILT_MODULE_LOCATION[2]="modules"
+
Please make sure that the kernel module `vmmon' is loaded.
  
BUILT_MODULE_NAME[3]="vmci"
+
This means that at least the {{Ic|vmmon}} module is not loaded. See the [[#systemd services]] section for automatic loading.
BUILT_MODULE_LOCATION[3]="modules"
+
  
BUILT_MODULE_NAME[4]="vsock"
+
=== Kernel headers for version 4.x-xxxx were not found. If you installed them[...] ===
BUILT_MODULE_LOCATION[4]="modules"
+
  
DEST_MODULE_LOCATION[0]="/extra/vmware"
+
Install the headers ({{Pkg|linux-headers}}).
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"
+
{{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.}}
}}
+
  
and now the {{ic|Makefile}}:
+
=== USB devices not recognized ===
  
{{hc|/usr/src/vmware-modules-9/Makefile|
+
{{Tip|Also handled by {{AUR|vmware-patch}}.}}
2=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
+
If not using the [[#systemd services|systemd service]] to automatically handle the services, you need to manually start the {{ic|vmware-usbarbitrator}} binary as root each time.
  
LOCAL_MODULES := $(addsuffix .ko, $(TARGETS))
+
To start:
  
all: $(LOCAL_MODULES)
+
# vmware-usbarbitrator
        mkdir -p modules/
+
        mv *.ko modules/
+
        rm -rf $(DEST)
+
        depmod
+
  
/usr/src/linux-$(KERNEL)/include/linux/version.h:
+
To stop:
        ln -s /usr/src/linux-$(KERNEL)/include/generated/uapi/linux/version.h /usr/src/linux-$(KERNEL)/include/linux/version.h
+
  
%.ko: /usr/src/linux-$(KERNEL)/include/linux/version.h
+
# vmware-usbarbitrator --kill
        vmware-modconfig --console --build-mod -k $(KERNEL) $* $(GCC) $(HEADERS) vmware/
+
        cp -f $(DEST)/$*.ko .
+
  
clean:
+
=== The installer fails to start ===
        rm -rf modules/
+
}}
+
  
====Installation====
+
If you just get back to the prompt when opening the {{ic|.bundle}}, then you probably have a deprecated or broken version of the VMware installer and it should removed (you may also refer to the [[#Uninstallation|uninstallation]] section of this article):
The modules can then be registered:
+
# rm -r /etc/vmware-installer/
  
# dkms -m vmware-modules -v 9 -k `uname -r` add
+
=== Unable to download VMware Tools for Guests ===
  
built:
+
If after [[#Preventing crashes and freezes when checking for updates]]{{Broken section link}} you are still unable to download the VMware Tools ISOs, you may either try running {{ic|vmware}} or {{ic|vmplayer}} as ''root'', or downloading them directly from the [http://softwareupdate.vmware.com/cds/vmw-desktop/ VMware repository].
  
# dkms -m vmware-modules -v 9 -k `uname -r` build
+
Navigate to: "''application name'' / ''version'' / ''build ID'' / linux / packages/" and download the appropriate Tools.
  
and installed:
+
Extract with:
  
  # dkms -m vmware-modules -v 9 -k `uname -r` install
+
  $ tar -xvf vmware-tools-''name''-''version''-''buildID''.x86_64.component.tar
  
If everything went well, the modules will now be recompiled automatically the next time the kernel changes.
+
And install using the VMware installer:
  
==Troubleshooting==
+
# vmware-installer --install-component=''/path/''vmware-tools-''name''-''version''-''buildID''.x86_64.component
  
===Could not open /dev/vmmon: No such file or directory.===
+
If the above does not work, try installing {{AUR|ncurses5-compat-libs}}.
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 {{Ic|vmmon}} VMware service is not running. If using the {{ic|.service}} file from step 8. all VMware services can be started with:
+
=== Incorrect login/password when trying to access VMware remotely ===
# systemctl start vmware
+
  
otherwise use:
+
VMware Workstation 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:
# /etc/init.d/vmware start
+
  
===Kernel headers for version 3.x-xxxx were not found. If you installed them[...]===
+
{{hc|/etc/pam.d/vmware-authd|
Install them with:
+
#%PAM-1.0
  # pacman -S linux-headers
+
auth    ''required      pam_unix.so''
 +
account  ''required      pam_unix.so''
 +
password ''required      pam_permit.so''
 +
session ''required      pam_unix.so''
 +
}}
  
{{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.}}
+
and restart the {{ic|vmware}} [[systemd]] service.
  
===USB devices not recognized===
+
Now you can connect to the server with the credentials provided during the installation.
====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].
+
  
You may also manually extract the VMware bundle and copy the {{ic|vmware-USBArbitrator}} script from {{ic|<destination folder>/vmware-usbarbitrator/etc/init.d/}} to {{ic|/etc/init.d/}}:
+
{{Note|{{Pkg|libxslt}} may be required for starting virtual machines.}}
$ ./VMware-<edition>-<version>.<release>.<architecture>.bundle --console --extract /tmp/vmware-bundle
+
# cp /tmp/vmware-bundle/vmware-usbarbitrator/etc/init.d/vmware-USBArbitrator /etc/init.d/
+
  
====2) The {{ic|vmware-usbarbitrator}} binary is segfaulting====
+
=== Issues with ALSA output ===
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 --info -f|
+
[http://bankimbhavsar.blogspot.co.nz/2011/09/hd-audio-in-vmware-fusion-4-and-vmware.html To fix] sound quality issues or enabling proper HD audio output, first run:
VTHREAD initialize main thread 2 "usbArb" pid 6426
+
$ aplay -L
Segmentation fault
+
 
 +
If interested in playing 5.1 ''surround sound'' from the guest, look for {{ic|1=surround51:CARD=''vendor_name'',DEV=''num''}}, if experiencing quality issues, look for {{ic|1=front:CARD=''vendor_name'',DEV=''num''}}. Finally put the name in the {{ic|.vmx}}:
 +
 
 +
{{hc|~/vmware/''Virtual_machine_name''/''Virtual_machine_name''.vmx|2=
 +
sound.fileName=''"surround51:CARD=Live,DEV=0"''
 +
sound.autodetect=''"FALSE"''
 
}}
 
}}
  
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.
+
[[Advanced Linux Sound Architecture#User-space utilities|OSS emulation]]{{Broken section link}} should also be disabled.
  
To fix it, add a version string in the form of {{ic|<year>.<month>(.<day>)}} (e.g. {{ic|[https://www.archlinux.org/news/december-time-for-a-new-install-medium/ 2012.12.01]}}).
+
=== Kernel-based Virtual Machine (KVM) is running ===
  
===process XXXX: Attempt to remove filter function[...]===
+
To disable {{ic|KVM}} on boot, you can use something like:
The full error is, for example:
+
       
process 6094: Attempt to remove filter function 0xadcc96f0 user data 0xb795aba0, but no such filter has been added
+
{{hc|/etc/modprobe.d/vmware.conf|
  D-Bus not built with -rdynamic so unable to print a backtrace
+
blacklist kvm
Aborted
+
blacklist kvm-amd  # For AMD CPUs
 +
blacklist kvm-intel # For Intel CPUs
 +
}}
  
This means that the hal daemon is not running. Install {{AUR|hal}} from the [[AUR]] and start the daemon with:
+
=== Segmentation fault at startup due to old Intel microcode ===
# hald
+
  
===The installer fails to start===
+
Old Intel microcode may result in the following kind of segmentation fault at startup:
If you just get back to the prompt when opening the {{ic|.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|uninstallation]] section of this article):
+
# rm -r /etc/vmware-installer
+
  
===Incorrect login/password when trying to access VMware remotely===
+
/usr/bin/vmware: line 31: 4941 Segmentation fault "$BINDIR"/vmware-modconfig --appname="VMware Workstation" --icon="vmware-workstation"
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:
+
  
{{hc|/etc/pam.d/vmware-authd|
+
See [[Microcode]] for how to update the microcode.
#%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 VMware services with:
+
=== Guests have incorrect system clocks or are unable to boot: "[...]timeTracker_user.c:234 bugNr=148722" ===
# systemctl restart vmware
+
  
Now you can connect to the server with the credentials provided during the installation.
+
This is due to [http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1591 incomplete] support of power management features ([[Wikipedia:Intel speedstep|Intel SpeedStep]] and [[Wikipedia:AMD powernow|AMD PowerNow!]]/[[Wikipedia:Cool'n'Quiet|Cool'n'Quiet]]) in VMware Linux that vary the CPU frequency. In March 2012, with the release of [https://projects.archlinux.org/svntogit/packages.git/commit/trunk/config.x86_64?h=packages/linux&id=9abe018d91a5d8c3af7523d30b8aa73f86b680be linux 3.3-1] the maximum frequency [[CPU frequency governors|Performance]] governor was replaced with the dynamic ''Ondemand''. When the host CPU frequency changes, the Guest system clock runs too quickly or too slowly, but may also render the whole Guest unbootable.
  
{{Note|{{Pkg|libxslt}} may be required for starting virtual machines.}}
+
To prevent this, the maximum host CPU frequency can be specified, and [[Wikipedia:Time Stamp Counter|Time Stamp Counter]] (TSC) disabled, in the global configuration:
  
===Issues with ALSA output===
+
{{hc|/etc/vmware/config|2=
The following instructions from [http://bankimbhavsar.blogspot.co.nz/2011/09/hd-audio-in-vmware-fusion-4-and-vmware.html Bankim Bhavsar's wiki] show how to manually adjust the [[ALSA]] output device in a VMware {{ic|.vmx}} file. This might help with quality issues or with enabling proper HD audio output:
+
host.cpukHz = "X"  # The maximum speed in KHz, e.g. 3GHz is "3000000".
 +
host.noTSC = "TRUE" # Keep the Guest system clock accurate even when
 +
ptsc.noTSC = "TRUE" # the time stamp counter (TSC) is slow.
 +
}}
  
# Suspend/Power off the VM.
+
{{Tip|To periodically correct the time (once per minute), in the ''Options'' tab of VMware Tools, enable: ''"Time synchronization between the virtual machine and the host operating system"''.}}
# Run {{ic|aplay -L}}
+
# If you are interested in playing 5.1 surround sound from the guest, look for {{ic|1=surround51:CARD=vendor-name,DEV=num}}. If you are experiencing quality issues, look out for a line starting with front.
+
# 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.
+
  
==="Aborted" error message when starting VMWare or VMWare Player===
+
=== Networking on Guests not available after system restart ===
  
Following an upgrade of Curl to version 7.29.0, VMWare receives a segfault upon startup and exits with a "Aborted" error message. See https://bugs.archlinux.org/task/33779 for details.
+
This is likely due to the {{ic|vmnet}} module not being loaded [http://www.linuxquestions.org/questions/slackware-14/could-not-connect-ethernet0-to-virtual-network-dev-vmnet8-796095/]. See also the [[#systemd services]] section for automatic loading.
  
==Uninstallation==
+
=== Workstation Server service does not start ===
  
To uninstall VMware you need the product name (either {{ic|vmware-workstation}} or {{ic|vmware-player}}). To list all the installed products:
+
If the {{ic|vmware-workstation-server.service}} fails with:
 +
{{hc|# systemctl status vmware-workstation-server|
 +
[...]
 +
Could not find administrative user. Error 127
 +
}}
  
  # vmware-installer -l
+
You may need a symlink for the following:
 +
  # ln -s wssc-adminTool /usr/lib/vmware/bin/vmware-wssc-adminTool
  
and uninstall with:
+
== Uninstallation ==
  
# vmware-installer -u <vmware-product>
+
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
  
Manually included symlinks have to be removed manually in {{ic|/sbin/}}:
+
and uninstall with ({{ic|--required}}&nbsp;skips the confirmation):
  # rm /sbin/insmod /sbin/lsmod /sbin/modinfo /sbin/rmmod
+
  # vmware-installer -u ''product'' --required
  
Remember to also remove the {{ic|.service}} file:
+
{{Tip|Use {{ic|--console}} for the console UI.}}
# systemctl disable vmware
+
 
 +
Remember to also [[disable]] and remove the services:
 
  # rm /etc/systemd/system/vmware.service
 
  # rm /etc/systemd/system/vmware.service
 +
# rm /etc/systemd/system/vmware-usbarbitrator.service
 +
 +
You may also want to have a look at the module directories in {{ic|/usr/lib/modules/''kernel_name''/misc/}} for any leftovers.

Latest revision as of 12:00, 5 December 2016

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

Note:
  • This article is about the latest major VMware versions, meaning VMware Workstation Pro and Player 12.5.
  • For older versions, use the vmware-patchAUR package.

Installation

Install the correct dependencies:

Download the latest VMware Workstation Pro or Player (or a beta version, if available).

Start the installation:

# sh VMware-edition-version.release.architecture.bundle
Tip: Some useful flags:
  • --eulas-agreed - Skip the EULAs
  • --console - Use the console UI.
  • --custom - Allows changing the install directory to e.g. /usr/local (make sure to update the vmware-usbarbitrator.service paths in #systemd services).
  • -I, --ignore-errors - Ignore fatal errors.
  • --set-setting=vmware-workstation serialNumber XXXXX-XXXXX-XXXXX-XXXXX-XXXXX - Set the serial number during install (good for scripted installs).
  • --required - Only ask mandatory questions (results in silent install when combined with --eulas-agreed and --console).

For the System service scripts directory, use /etc/init.d (the default).

Note: During the installation you will get an error about "No rc*.d style init script directories" being given. This can be safely ignored, since Arch uses systemd.
Tip: To (re)build the modules from terminal later on, use:
# vmware-modconfig --console --install-all

Configuration

Kernel modules

VMware Workstation 12.5 supports kernels up to 4.8 out of the box.

systemd services

(Optional) Instead of using /etc/init.d/vmware (start|stop|status|restart) and /usr/bin/vmware-usbarbitrator directly to manage the services, you may also use .service files (also available in the vmware-systemd-servicesAUR package, and also included in vmware-patchAUR):

/etc/systemd/system/vmware.service
[Unit]
Description=VMware daemon
Requires=vmware-usbarbitrator.service
Before=vmware-usbarbitrator.service
After=network.target

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

[Install]
WantedBy=multi-user.target
/etc/systemd/system/vmware-usbarbitrator.service
[Unit]
Description=VMware USB Arbitrator
Requires=vmware.service
After=vmware.service

[Service]
ExecStart=/usr/bin/vmware-usbarbitrator
ExecStop=/usr/bin/vmware-usbarbitrator --kill
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

Add this service as well, if you want to connect to your VMware Workstation installation from another Workstation Server Console:

/etc/systemd/system/vmware-workstation-server.service
[Unit]
Description=VMware Workstation Server
Requires=vmware.service
After=vmware.service

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

[Install]
WantedBy=multi-user.target

After which you can enable them on boot.

Launching the application

To open VMware Workstation Pro:

$ vmware

or Player:

$ vmplayer

Tips and tricks

Entering the Workstation Pro 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 does not 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

Extracting the installer

To view the contents of the installer .bundle:

$ sh VMware-edition-version.release.architecture.bundle --extract /tmp/vmware-bundle/

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"

Enable 3D graphics on Intel and Optimus

Some graphics drivers are blacklisted by default, due to poor and/or unstable 3D acceleration. After enabling Accelerate 3D graphics, the log may show something like:

Disabling 3D on this host due to presence of Mesa DRI driver.  Set mks.gl.allowBlacklistedDrivers = TRUE to override.

This means the following:

~/.vmware/preferences
mks.gl.allowBlacklistedDrivers = TRUE

Troubleshooting

/dev/vmmon not found

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 module is not loaded. See the #systemd services section for automatic loading.

Kernel headers for version 4.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.

If not using the systemd service to automatically handle the services, you need to manually start the vmware-usbarbitrator binary as root each time.

To start:

# vmware-usbarbitrator

To stop:

# vmware-usbarbitrator --kill

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 it should removed (you may also refer to the uninstallation section of this article):

# rm -r /etc/vmware-installer/

Unable to download VMware Tools for Guests

If after #Preventing crashes and freezes when checking for updates[broken link: invalid section] you are still unable to download the VMware Tools ISOs, you may either try running vmware or vmplayer as root, or downloading them directly from the VMware repository.

Navigate to: "application name / version / build ID / linux / packages/" and download the appropriate Tools.

Extract with:

$ tar -xvf vmware-tools-name-version-buildID.x86_64.component.tar

And install using the VMware installer:

# vmware-installer --install-component=/path/vmware-tools-name-version-buildID.x86_64.component

If the above does not work, try installing ncurses5-compat-libsAUR.

Incorrect login/password when trying to access VMware remotely

VMware Workstation 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

To fix sound quality issues or enabling proper HD audio output, first run:

$ aplay -L

If interested in playing 5.1 surround sound from the guest, look for surround51:CARD=vendor_name,DEV=num, if experiencing quality issues, look for front:CARD=vendor_name,DEV=num. Finally put the name in the .vmx:

~/vmware/Virtual_machine_name/Virtual_machine_name.vmx
sound.fileName="surround51:CARD=Live,DEV=0"
sound.autodetect="FALSE"

OSS emulation[broken link: invalid section] should also be disabled.

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

Segmentation fault at startup due to old Intel microcode

Old Intel microcode may result in the following kind of segmentation fault at startup:

/usr/bin/vmware: line 31: 4941 Segmentation fault "$BINDIR"/vmware-modconfig --appname="VMware Workstation" --icon="vmware-workstation"

See Microcode for how to update the microcode.

Guests have incorrect system clocks or are unable to boot: "[...]timeTracker_user.c:234 bugNr=148722"

This is due to incomplete support of power management features (Intel SpeedStep and AMD PowerNow!/Cool'n'Quiet) in VMware Linux that vary the CPU frequency. In March 2012, with the release of linux 3.3-1 the maximum frequency Performance governor was replaced with the dynamic Ondemand. When the host CPU frequency changes, the Guest system clock runs too quickly or too slowly, but may also render the whole Guest unbootable.

To prevent this, the maximum host CPU frequency can be specified, and Time Stamp Counter (TSC) disabled, in the global configuration:

/etc/vmware/config
host.cpukHz = "X"  # The maximum speed in KHz, e.g. 3GHz is "3000000".
host.noTSC = "TRUE" # Keep the Guest system clock accurate even when
ptsc.noTSC = "TRUE" # the time stamp counter (TSC) is slow.
Tip: To periodically correct the time (once per minute), in the Options tab of VMware Tools, enable: "Time synchronization between the virtual machine and the host operating system".

Networking on Guests not available after system restart

This is likely due to the vmnet module not being loaded [1]. See also the #systemd services section for automatic loading.

Workstation Server service does not start

If the vmware-workstation-server.service fails with:

# systemctl status vmware-workstation-server
[...]
Could not find administrative user. Error 127

You may need a symlink for the following:

# ln -s wssc-adminTool /usr/lib/vmware/bin/vmware-wssc-adminTool

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 (--required skips the confirmation):

# vmware-installer -u product --required
Tip: Use --console for the console UI.

Remember to also disable and remove the services:

# rm /etc/systemd/system/vmware.service
# rm /etc/systemd/system/vmware-usbarbitrator.service

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