Difference between revisions of "VMware"

From ArchWiki
Jump to: navigation, search
(Installation)
(Installation: clarify)
 
(256 intermediate revisions by 59 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}} - the {{ic|vmware-vmblock-fuse}} service is [https://www.mail-archive.com/open-vm-tools-devel@lists.sourceforge.net/msg00213.html favored] over the {{ic|vmblock}} module, and the vmblock module not built anymore without disabling [http://cateee.net/lkddb/web-lkddb/FUSE_FS.html fuse] in the kernel
 +
*{{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 at least the installer
  
# a sysv init directory is needed to install
+
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).
#:<code>mkdir -p /etc/init.d/{rc0.d,rc1.d,rc2.d,rc3.d,rc4.d,rc5.d,rc6.d}</code>
+
# KVM cannot be active. Edit <code>/etc/modprobe.d/vmware.conf</code>
+
#:<code>blacklist kvm</code>
+
#: and <code>blacklist kvm-intel</code> or <code>kvm-amd</code>
+
# 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]).
+
# Start the installation ({{Ic|--console}} uses terminal instead of the GUI):
+
#:<code> $ chmod +x VMware-''edition''-''version''.''release''.''architecture''.bundle</code>
+
#:<code># ./VMware-''edition''-''version''.''release''.''architecture''.bundle --console</code>
+
# Read and accept the EULA to continue.
+
# Set {{ic|System service scripts directory}} to {{ic|/etc/init.d}}.
+
# (Optional) If Eclipse is installed, enter the directory path to the Integrated Virtual Debugger.
+
  
== Configuration ==
+
Start the installation:
 +
# sh VMware-''edition''-''version''.''release''.''architecture''.bundle
  
{{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).}}
+
{{Tip|Some useful flags:
 +
*{{ic|--eulas-agreed}} - Skip the EULAs
 +
*{{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}}).
 +
}}
  
{{Note|Ensure you have installed the correct headers required for building the modules ({{Pkg|linux}} from {{ic|[core]}} uses {{Pkg|linux-headers}}).}}
+
For the {{ic|System service scripts directory}}, use {{ic|/etc/init.d}} (the default).
  
=== VMware module patches and installation ===
+
{{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]].}}
  
VMware Workstation 9 and Player 5 both support kernels up to 3.9. Any later requires patching of the VMware modules.
+
{{Tip|To (re)build the modules from terminal later on, use:
 
+
==== 3.10 kernels ====
+
 
+
The call {{ic|create_proc_entry()}} has been dropped from 3.10 in favor of {{ic|proc_create()}}. This requires patching the {{ic|vmblock}} and {{ic|vmnet}} modules that use them.
+
 
+
The patches (including the optional fuse patch) can be found [http://pkgbuild.com/git/aur-mirror.git/tree/vmware-patch/vmblock-9.0.2-5.0.2-3.10.patch here] and [http://pkgbuild.com/git/aur-mirror.git/tree/vmware-patch/vmnet-9.0.2-5.0.2-3.10.patch here]:
+
 
+
$ cd /tmp
+
$ curl -O http://pkgbuild.com/git/aur-mirror.git/plain/vmware-patch/vmblock-9.0.2-5.0.2-3.10.patch
+
$ curl -O http://pkgbuild.com/git/aur-mirror.git/plain/vmware-patch/vmnet-9.0.2-5.0.2-3.10.patch
+
$ cd /usr/lib/vmware/modules/source
+
# tar -xvf vmblock.tar
+
# tar -xvf vmnet.tar
+
# patch -p0 -i /tmp/vmblock-9.0.2-5.0.2-3.10.patch
+
# patch -p0 -i /tmp/vmnet-9.0.2-5.0.2-3.10.patch
+
# tar -cf vmblock.tar vmblock-only
+
# tar -cf vmnet.tar vmnet-only
+
# rm -r vmblock-only
+
# rm -r vmnet-only
+
 
  # vmware-modconfig --console --install-all
 
  # vmware-modconfig --console --install-all
 
==== 3.9 kernels - patch for fuseless systems (optional) ====
 
 
Systems that don't have {{pkg|fuse}} will not be able to use the {{ic|/usr/lib/vmware/bin/vmware-vmblock-fuse}} client. These systems will fall back to the original {{ic|vmblock.ko}} module, which won't load due to the symbol {{ic|putname}} being replaced by {{ic|__putname}}:
 
 
{{hc|# modprobe vmblock|
 
modprobe: ERROR: could not insert 'vmblock': Unknown symbol in module, or unknown parameter (see dmesg)
 
}}
 
{{hc|$ dmesg <nowiki>|</nowiki> tail -1|
 
[ 8896.222258] vmblock: Unknown symbol putname (err 0)
 
 
}}
 
}}
  
The patch can be found [http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-emulation/vmware-modules/files/264-putname.patch?&view=markup here]:
+
== Configuration ==
  
$ cd /tmp
+
=== Kernel modules ===
$ curl -O http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-emulation/vmware-modules/files/264-putname.patch
+
$ cd /usr/lib/vmware/modules/source
+
# tar -xvf vmblock.tar
+
# patch -p1 -i /tmp/264-putname.patch
+
# tar -cf vmblock.tar vmblock-only
+
# rm -r vmblock-only
+
# vmware-modconfig --console --install-all
+
  
{{Note|
+
VMware Workstation 12.5 supports kernels up to 4.8 out of the box.
* The following is 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}}.
+
=== systemd services ===
  
==== 3.7 kernels and up ====
+
''(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}}):
  
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:
+
{{hc|/etc/systemd/system/vmware.service|
# ln -s /usr/src/linux-'''$(uname -r)'''/include/generated/uapi/linux/version.h /usr/src/linux-'''$(uname -r)'''/include/linux/
+
2=[Unit]
You can replace "'''{{ic|$(uname -r)}}'''" with any kernel not currently running.
+
Description=VMware daemon
{{Note|You will need to redo this upon every kernel update.}}
+
Requires=vmware-usbarbitrator.service
 +
Before=vmware-usbarbitrator.service
 +
After=network.target
  
==== 3.8 / 3.9 kernels ====
+
[Service]
 +
ExecStart=/etc/init.d/vmware start
 +
ExecStop=/etc/init.d/vmware stop
 +
PIDFile=/var/lock/subsys/vmware
 +
RemainAfterExit=yes
  
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]):
+
[Install]
 +
WantedBy=multi-user.target
 +
}}
  
$ cd /tmp
+
{{hc|/etc/systemd/system/vmware-usbarbitrator.service|
$ curl -O https://raw.github.com/willysr/SlackHacks/master/vmware/vmware-3.8/vmware9.0.1_kernel3.8.zip
+
2=[Unit]
$ bsdtar -xvf vmware9.0.1_kernel3.8.zip
+
Description=VMware USB Arbitrator
# ./patch-modules_3.8.0.sh
+
Requires=vmware.service
 +
After=vmware.service
  
=== Systemd service ===
+
[Service]
 +
ExecStart=/usr/bin/vmware-usbarbitrator
 +
ExecStop=/usr/bin/vmware-usbarbitrator --kill
 +
RemainAfterExit=yes
  
'''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]):
+
[Install]
 +
WantedBy=multi-user.target
 +
}}
  
{{hc|/etc/systemd/system/vmware.service|
+
Add this service as well, if you want to connect to your VMware Workstation installation from another Workstation Server Console:
 +
 
 +
{{hc|/etc/systemd/system/vmware-workstation-server.service|
 
2=[Unit]
 
2=[Unit]
Description=VMware daemon
+
Description=VMware Workstation Server
 +
Requires=vmware.service
 +
After=vmware.service
  
 
[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
  
Line 129: Line 108:
 
}}
 
}}
  
To start the [[daemon]] on boot, enable the [[systemd]] service {{ic|vmware}}.
+
After which you can [[enable]] them on boot.
  
 
== 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!
+
To open VMware Workstation Pro:
 +
$ vmware
  
{{Tip|To (re)build the modules, use:
+
or Player:
  # vmware-modconfig --console --install-all
+
  $ vmplayer
}}
+
  
 
== Tips and tricks ==
 
== Tips and tricks ==
  
=== Entering the Workstation License Key from terminal ===
+
=== Entering the Workstation Pro 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 does not work, you can try:
 +
 +
# /usr/lib/vmware/bin/vmware-enter-serial
  
 
=== Extracting the VMware BIOS ===
 
=== Extracting the VMware BIOS ===
Line 152: Line 141:
 
  $ 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''}}:
+
To view the contents of the installer {{ic|.bundle}}:
$ mv bios440.rom ~/vmware/''Virtual machine name''/
+
  
then adding the name to the {{ic|''Virtual machine name''.vmx}} file:
+
$ sh VMware-''edition''-''version''.''release''.''architecture''.bundle --extract ''/tmp/vmware-bundle/''
{{hc|~/vmware/''Virtual machine name''/''Virtual machine name''.vmx|2=bios440.filename = "bios440.rom"}}
+
  
=== Copy-On-Write (CoW) ===
+
==== Using the modified BIOS ====
  
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):
+
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''/
  
$ chattr +C ~/vmware/''Virtual machine name''/''Virtual machine name''.vmx
+
then adding the name to the {{ic|''Virtual_machine_name''.vmx}} file:
 +
{{hc|~/vmware/''Virtual_machine_name''/''Virtual_machine_name''.vmx|2=bios440.filename = "bios440.rom"}}
  
{{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."''}}
+
=== Enable 3D graphics on Intel and Optimus ===
  
=== Using DKMS to manage the modules ===
+
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:
  
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.
+
Disabling 3D on this host due to presence of Mesa DRI driver. Set mks.gl.allowBlacklistedDrivers = TRUE to override.
  
==== Preparation ====
+
This means the following:
  
First install {{Pkg|dkms}} from the [[official repositories]].
+
{{hc|~/.vmware/preferences|2=
 +
mks.gl.allowBlacklistedDrivers = TRUE
 +
}}
  
Then create a source directory for the {{ic|Makefile}} and the {{ic|dkms.conf}}:
+
== Troubleshooting ==
# mkdir /usr/src/vmware-modules-9/
+
  
==== Build configuration ====
+
=== /dev/vmmon not found ===
  
Fetch the files from Git or use the ones below.
+
The full error is:
  
===== 1) Using Git =====
+
Could not open /dev/vmmon: No such file or directory.
 +
Please make sure that the kernel module `vmmon' is loaded.
  
$ cd /tmp
+
This means that at least the {{Ic|vmmon}} module is not loaded. See the [[#systemd services]] section for automatic loading.
$ 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 =====
+
=== Kernel headers for version 4.x-xxxx were not found. If you installed them[...] ===
  
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:
+
Install the headers ({{Pkg|linux-headers}}).
  
{{hc|/usr/src/vmware-modules-9/dkms.conf|
+
{{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.}}
2=PACKAGE_NAME="vmware-modules"
+
PACKAGE_VERSION="9"
+
  
MAKE[0]="make all"
+
=== USB devices not recognized ===
CLEAN="make clean"
+
  
BUILT_MODULE_NAME[0]="vmmon"
+
{{Tip|Also handled by {{AUR|vmware-patch}}.}}
BUILT_MODULE_LOCATION[0]="modules"
+
  
BUILT_MODULE_NAME[1]="vmnet"
+
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.
BUILT_MODULE_LOCATION[1]="modules"
+
  
BUILT_MODULE_NAME[2]="vmblock"
+
To start:
BUILT_MODULE_LOCATION[2]="modules"
+
  
BUILT_MODULE_NAME[3]="vmci"
+
# vmware-usbarbitrator
BUILT_MODULE_LOCATION[3]="modules"
+
  
BUILT_MODULE_NAME[4]="vsock"
+
To stop:
BUILT_MODULE_LOCATION[4]="modules"
+
  
DEST_MODULE_LOCATION[0]="/extra/vmware"
+
# vmware-usbarbitrator --kill
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"
+
=== The installer fails to start ===
}}
+
  
and now the {{ic|Makefile}}:
+
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):
 +
# rm -r /etc/vmware-installer/
  
{{hc|/usr/src/vmware-modules-9/Makefile|
+
=== Unable to download VMware Tools for Guests ===
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 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].
  
LOCAL_MODULES := $(addsuffix .ko, $(TARGETS))
+
Navigate to: "''application name'' / ''version'' / ''build ID'' / linux / packages/" and download the appropriate Tools.
  
all: $(LOCAL_MODULES)
+
Extract with:
        mkdir -p modules/
+
        mv *.ko modules/
+
        rm -rf $(DEST)
+
        depmod
+
  
/usr/src/linux-$(KERNEL)/include/linux/version.h:
+
$ tar -xvf vmware-tools-''name''-''version''-''buildID''.x86_64.component.tar
        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
+
And install using the VMware installer:
        vmware-modconfig --console --build-mod -k $(KERNEL) $* $(GCC) $(HEADERS) vmware/
+
        cp -f $(DEST)/$*.ko .
+
  
clean:
+
# vmware-installer --install-component=''/path/''vmware-tools-''name''-''version''-''buildID''.x86_64.component
        rm -rf modules/
+
}}
+
  
==== Installation ====
+
If the above does not work, try installing {{AUR|ncurses5-compat-libs}}.
  
The modules can then be registered:
+
=== Incorrect login/password when trying to access VMware remotely ===
  
# dkms -m vmware-modules -v 9 -k $(uname -r) add
+
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:
  
built:
+
{{hc|/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''
 +
}}
  
# dkms -m vmware-modules -v 9 -k $(uname -r) build
+
and restart the {{ic|vmware}} [[systemd]] service.
  
and installed:
+
Now you can connect to the server with the credentials provided during the installation.
  
# dkms -m vmware-modules -v 9 -k $(uname -r) install
+
{{Note|{{Pkg|libxslt}} may be required for starting virtual machines.}}
  
If everything went well, the modules will now be recompiled automatically the next time the kernel changes.
+
=== Issues with ALSA output ===
  
== Troubleshooting ==
+
[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:
 +
$ aplay -L
  
=== Could not open /dev/vmmon: No such file or directory. ===
+
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}}:
  
The full error is:
+
{{hc|~/vmware/''Virtual_machine_name''/''Virtual_machine_name''.vmx|2=
Could not open /dev/vmmon: No such file or directory.
+
sound.fileName=''"surround51:CARD=Live,DEV=0"''
Please make sure that the kernel module `vmmon' is loaded.
+
sound.autodetect=''"FALSE"''
 +
}}
  
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.
+
[[Advanced Linux Sound Architecture#User-space utilities|OSS emulation]]{{Broken section link}} should also be disabled.
  
=== Kernel headers for version 3.x-xxxx were not found. If you installed them[...] ===
+
=== Kernel-based Virtual Machine (KVM) is running ===
  
Install the headers ({{Pkg|linux-headers}}).
+
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
 +
}}
  
{{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.}}
+
=== Segmentation fault at startup due to old Intel microcode ===
  
=== USB devices not recognized ===
+
Old Intel microcode may result in the following kind of segmentation fault at startup:
  
{{Tip|Also handled by {{AUR|vmware-patch}}.}}
+
/usr/bin/vmware: line 31: 4941 Segmentation fault "$BINDIR"/vmware-modconfig --appname="VMware Workstation" --icon="vmware-workstation"
  
==== 1) The {{ic|vmware-USBArbitrator}} script is missing ====
+
See [[Microcode]] for how to update the microcode.
  
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].
+
=== Guests have incorrect system clocks or are unable to boot: "[...]timeTracker_user.c:234 bugNr=148722" ===
  
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/}}:
+
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.
$ ./VMware-''edition''-''version''.''release''.''architecture''.bundle --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 ====
+
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:
  
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|/etc/vmware/config|2=
{{hc|# vmware-usbarbitrator|
+
host.cpukHz = "X"  # The maximum speed in KHz, e.g. 3GHz is "3000000".
Pipe unexpectedly closed.
+
host.noTSC = "TRUE" # Keep the Guest system clock accurate even when
}}
+
ptsc.noTSC = "TRUE" # the time stamp counter (TSC) is slow.
{{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.
+
{{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"''.}}
  
To fix it, add a version string in the form of {{ic|''year''.''month''(.''day'')}} (e.g. {{ic|[https://www.archlinux.org/download/ 2013.06.01]}}).
+
=== Networking on Guests not available after system restart ===
  
=== The installer fails to start ===
+
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.
  
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):
+
=== Workstation Server service does not start ===
# rm -r /etc/vmware-installer
+
  
=== Incorrect login/password when trying to access VMware remotely ===
+
If the {{ic|vmware-workstation-server.service}} fails with:
 
+
{{hc|# systemctl status vmware-workstation-server|
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:
+
[...]
 
+
Could not find administrative user. Error 127
{{hc|/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 {{ic|vmware}} [[systemd]] service.
+
You may need a symlink for the following:
 
+
# ln -s wssc-adminTool /usr/lib/vmware/bin/vmware-wssc-adminTool
Now you can connect to the server with the credentials provided during the installation.
+
 
+
{{Note|{{Pkg|libxslt}} may be required for starting virtual machines.}}
+
 
+
=== Issues with ALSA output ===
+
 
+
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:
+
 
+
# Suspend/Power off the VM.
+
# 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.
+
  
 
== Uninstallation ==
 
== Uninstallation ==
Line 350: Line 303:
 
  $ vmware-installer -l
 
  $ vmware-installer -l
  
and uninstall with:
+
and uninstall with ({{ic|--required}}&nbsp;skips the confirmation):
  # vmware-installer -u ''vmware-product''
+
  # vmware-installer -u ''product'' --required
  
Remember to also disable and remove the {{ic|vmware}} service:
+
{{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 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/}}.
+

Latest revision as of 10:36, 28 November 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:

  • fuse - the vmware-vmblock-fuse service is favored over the vmblock module, and the vmblock module not built anymore without disabling fuse in the kernel
  • gksu - for root operations (memory allocations, registering license, etc.)
  • gtkmm - for the GUI
  • linux-headers - for module compilation
  • ncurses5-compat-libsAUR - needed by at least the installer

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.