From ArchWiki
Revision as of 21:49, 22 August 2010 by Sputnick (talk | contribs)
Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

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

VMware Server Installation

Install vmware-server from the AUR.

VMware Server Console

Install vmware-server-console from the AUR.

Alternatively, on Arch64, the bin32 version can also be installed.

VMware Workstation or VMware Player


Note: This will not install with pacman, so the files installed will not be traceable/removable with pacman.

To install Workstation or Player on a Linux host using a bundle:

1. Download Template:Filename or Template:Filename from the VMware site. (Template:Codeline you can also try the testing (Beta/RC) versions found in here: http://communities.vmware.com/community/beta/ws but please note that they indeed are beta and so there's no guarantee you will not run into issues).

2. In a terminal cd to the directory where you downloaded the file.

3. Become root and create a fake System V init style directory for VMware and start the installation (the --console flag uses terminal instead of the GUI and the --custom asks all the unnecessary questions that nobody cares about):

# mkdir -p /etc/rc.d/vmware.d/{rc{0..6},init}.d
# chmod +x VMware-<edition>-<version>.<release>.<architecture>.bundle
# ./VMware-<edition>-<version>.<release>.<architecture>.bundle --console --custom

4. (Read &) accept the EULA to continue.

5. Accept the default settings until it prompts for Template:Codeline runlevels then set to:


6. For Template:Codeline set to:


It might happen that you need to set the directory for Template:Codeline as Template:Codeline (the default) or else the installation would fail. If you do, you can create a symlink from Template:Codeline to Template:Codeline afterwards or the other way around (note that you can't remove the Template:Codeline after you've placed it somewhere because that's where VMware will be looking for it).

7. (Optional) Enter the directory path to the Integrated Virtual Debugger for Eclipse if Eclipse is installed.

8. Mash enter to install. Note that if nothing happens at this point and you are returned to the prompt, try re-running the installation without the --console option.

9. At this point you would want to install the modules. First you need to either change the Template:Codeline in Template:Codeline at the lines 88 and 108 from:




or create a symlink from Template:Codeline to Template:Codeline with:

# ln -s /bin/lsmod /sbin/lsmod

For 2.6.35 kernel and VMware7.1.1, there's a script to patch the VMware sources :

$ cd /tmp
$ wget http://www.sputnick-area.net/scripts/vmware7.1.1-patch-kernel-2.6.35.bash
# chmod +x vmware7.1.1-patch-kernel-2.6.35.bash
# ./vmware7.1.1-patch-kernel-2.6.35.bash

Now you can install the modules. You can do this with either by launching VMware and letting it install the modules from there with the GUI or alternatively you can execute the command:

# vmware-modconfig --console --install-all

10. (Optional) Add vmware to the DAEMONS array in /etc/rc.conf so that the service is started automatically on boot.

11. Now, open your VMware Workstation (Template:Codeline in the console) to configure & use!


Check the product name

# vmware-installer -l

uninstall product

# vmware-installer -u <vmware-product>

Manually included parts in /etc/rc.d have to be deleted manually. Don't forget to remove vmware from the /etc/rc.conf DAEMONS array.


If when you ran


you get back to the prompt and VMware don't ask you to makes choices, then you probably have an old install, so you should rename /etc/vmware-installer/ :

# mv /etc/vmware-installer /etc/vmware-installer.old

If you get an error like this when launching up a Virtual Machine:

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

It means that at least the one VMware service isn't started up. You can start them all up by running (as root):

# /etc/rc.d/vmware start

If, on the other hand VMware complains about kernel headers like this:

Kernel headers for version 2.6.xx-xxxx were not found. If you installed them.......

Install them with the following:

# pacman -S kernel26-headers

Kernel upgrades and VMware modules

Please note that when upgrading the kernel you will have to rebuild the vmware modules with:

# vmware-modconfig --console --install-all

Otherwise your whole system might crash when trying to power up VMs so keep that in mind.

Compile Modules Problem

VMware and kernel 2.6.32

Note: not needed with vmware 7.x.x

To patch VMware modules we have to add #include "compat_sched.h" to some modules's source:

cd /tmp
tar xf /usr/lib/vmware/modules/source/vmnet.tar
nano vmnet-only/vnetUserListener.c (near line 37 add #include "compat_sched.h")
tar cf /usr/lib/vmware/modules/source/vmnet.tar vmnet-only
tar xf /usr/lib/vmware/modules/source/vmci.tar
nano vmci-only/linux/vmciKernelIf.c vmci-only/include/pgtbl.h (add #include "compat_sched.h" around 30 line)
tar cf /usr/lib/vmware/modules/source/vmci.tar vmci-only
vmware-modconfig --console --install-all

You can also use ready script http://communities.vmware.com/thread/239221