Page Actions
Wiki Actions
User Actions
Table of Contents
VMWare Server 2.0 beta on Ubuntu 8.04 Hardy Heron
Installing VMWare Server 2.0 Beta on Ubuntu is really a no-brainer, except for two things:
- Ubuntu is by default installed with IPv6, and VMWare is incompatible with this and fails to function.
- Ubuntu has no root account enabled, so the default administrative user needs to be altered.
Following is an account of the installation on my Ubuntu Hardy Heron.
Prerequisites
VMware Server is currently not compatible with Debian-style IPv6 (or IPv6 at all), so we must disable that first. To do this, edit /etc/modules.d/aliases, and change
alias net-pf-10 ipv6
to
alias net-pf-10 ipv6 off alias net-pf-10 off alias ipv6 off
Add the following line to /etc/modprobe.d/blacklist :
blacklist ipv6
The IP-related modules are tightly tied, so the best option to get these changes picked up, is by rebooting the system.
Install an internet superserver that VMWare understands (xinetd)
sudo apt-get install xinetd
VMWare server is going to compile kernel modules etc, so we need the followin aswell:
sudo apt-get install build-essential
Download and install
Now, go fetch the tar.gz package of VMWare Server 2.0 Beta from http://vmware.com/beta/server/ and unpack the tar to a suitable location and start the installer:
# assuming the tarball is located in your home directory, and is named "appropriately" cd /tmp tar zxvf ~/VMware-server-e.x.p-*.tar.gz cd vmware-server-distrib sudo ./vmware-install.pl
Answer the questions presented during the installation. The defaults should be safe in most cases. Personally, I choose to change the HTTP and HTTPS ports, using 8222 and 8333
Configure default user
VMWare Server insists on using root as the only user available by default, and as that user is disabled in Ubuntu, we need to change the default username. This is done in the file /etc/vmware/hostd/authorization.xml, bu changing the option ACEDataUser form root to your username
sudo vim /etc/vmware/hostd/authorization.xml
Basically, restarting VMWare at this point should give you a working setup. To be safe, I opted on rebooting.