Installing VMware Server on Gentoo Linux (Version 3)
The new VMware Server is going to replace VMware's GSX Server product. And it's more than just a new name: VMware will supposedly release it free of charge. Being still in beta testing, there are currently no stable ebuilds available for it on Gentoo Linux. Fortunately, Mike Auty and others are working on one and they are doing a fine job. They also seem to be streamlining and consolidating other related VMware ebuilds. You can keep track of their progress on these Bugzilla bugs:
- Problems regarding the vmware-module ebuild: 137422.
- Problems regarding the vmware-player ebuild: 137423.
- Problems regarding the vmware-server ebuild: 137424.
- Problems regarding the vmware-server-console ebuild: 137425.
- Problems regarding the vmware-workstation ebuild: 137426.
- Problems regarding the vmware-workstation-tools ebuild: 137428.
- Problems regarding the vmware overlay in general: 122500.
The VMware Server ebuilds are not part of the official stable Gentoo portage tree so if you want to install them on your system you will have to jump through a few extra hoops. Fortunately this process has become very convenient and straight-forward thanks to Gunnar Wrobel's layman. This article sums up the procedure.
Layman is a Python script that makes additional portage overlays available on your box. The
vmware overlay is one of them but before we can use it we obviously need to install layman:
# emerge layman # echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf
You may want to browse layman's list of available overlays. It should include the vmware overlay:
# layman -L ... * vmware [Subversion] (source: http://overlays.gentoo.org...) ...
Remove older VMware Server ebuilds
If you are frequent reader of Diary Products you may have followed this recipe's predecessors. In that case you'll need to unmerge the VMware Server ebuilds:
# emerge -Cavt vmware-server-console # emerge -Cavt vmware-server-modules # emerge -Cavt vmware-server
You may also have to remove the ebuilds from your Portage overlay. Assuming it's located at
/usr/local/portage this will do:
# rm -r /usr/local/portage/app-emulation/vmware-server # rm -r /usr/local/portage/app-emulation/vmware-server-console # rm -r /usr/local/portage/app-emulation/vmware-server-modules
Install VMware Server
Add the vmware overlay to your system:
# layman -a vmware ... Checked out revision 76. * Successfully added overlay "vmware".
Add the following thre lines to you
# vi /etc/portage/package.keywords app-emulation/vmware-server ~amd64 app-emulation/vmware-modules ~amd64 app-emulation/vmware-server-console ~amd64
People using Intel architecture should use
~x86 instead of
~amd64. Also note that if you used earlier VMware Server ebuilds, your
package.keywords will already contain those three lines with one tiny but important difference: vmware-server-modules is now called vmware-modules - I guess because it's shared by other VMware ebuilds like Workstation and Player. Please adjust your
Install VMware Server and its dependencies:
# emerge -avt vmware-server
Configure VMware Server
Follow the instructions displayed at the end of the installation. In particular, add yourself to the the
vmware group and run the vmware-config.pl script.
# usermod -aG vmware root # /opt/vmware/server/bin/vmware-config.pl
This is where many people run into trouble because it seems to be the most complex part of the installation. When posting questions to the above Bugzilla bugs keep in mind that the configuration script is maintained by VMware and not by the folks who provide the VMware ebuilds. They can only get so far patching the config script. In the long run they plan to get rid of the configuration script completely.