In the last section, we configured and secured Linux. Now it's time to work on the Management User Interface. Unlike...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
the Windows version of VMware Server, the VMware Server Management User Interface (MUI) is a separate component to be installed in the Linux version. This section details how to obtain the MUI, how to install it, how to secure and configure it, and how to log in.
You should have downloaded and unpacked the VMware MUI tarball when you downloaded the VMware Server tarball in Step VI.A.
The first step to installing the VMware Server MUI is to change directories to "/usr/local/src/vmware-mui-distrib-1.0.1-29996". Once you have done that, type:
The installation is very straightforward, and it is okay to accept all of the defaults. Once the installation is completed, you will see a screen that looks like this:
You will notice that the VMware Server MUI http server failed to start. This is because it is misconfigured for Edgy Eft, and we need to make some manual changes in order to make sure that it will function properly.
Now let's look at how to configure.
The VMware Server MUI does not start properly on Edgy Eft post installation. This is easy enough to fix thanks to a user named tauceti on the VMware forums. We need to edit the init script used to start the VMware Server MUI http server. To do this, type:
sudo vi /etc/init.d/httpd.vmware
Jump to line 258. Lines 258 through 263 should resemble the following:
start) vmware_exec "Starting httpd.vmware:" vmware_start_httpd ;; stop) vmware_exec "Shutting down http.vmware: " vmware_stop_httpd ;;
This stanza is the problem. Edit this text so that it resembles:
start) # vmware_exec "Starting httpd.vmware:" vmware_start_httpd echo "Starting httpd.vmware:" vmware_start_httpd ;; stop) # vmware_exec "Shutting down http.vmware: " vmware_stop_httpd echo "Shutting down http.vmware" vmware_stop_httpd ;;
Once you have made these changes, save the file and exit. Now type the following to start the VMware Server MUI:
sudo /etc/init.d/httpd.vmware start
There is a small problem. The file we just edited will get replaced with a "clean" version the next time the server reboots. We have to edit the "clean" version so that it has the above changes as well.
The file we need to edit is /usr/lib/vmware-mui/src/lib/httpd.vmware. Apply above changes to this file as well. Now the next time the server reboots the changes will be preserved.
By default, the VMware Server MUI will listen for incoming connections on all configured network interfaces. Just like the reconfiguring the vmware-authd daemon to only listen on the management interface NIC, we must do the same for the VMware Server MUI. We must first change directories to "/usr/lib/vmware-mui/apache/conf". Now type the following command where MGMT_NIC_IP is the IP address of your designated management interface NIC:
sudo cp httpd.conf httpd.conf.bak; sudo bash -c 'cat httpd.conf.bak | sed -r "s/^([[:space:]]+)Listen ([[:digit:]]+)$/\1Listen MGMT_NIC_IP:\2/g" > httpd.conf'
The above command will back up the httpd.conf file to httpd.conf.bak and will then create a new httpd.conf file, replacing all Listen directives so that they will be replaced with Listen directives that include the IP address of the management interface NIC in addition to the port.
We also need to make this change to the source file for httpd.conf. To do this, change the directories to "/usr/lib/vmware-mui/src/apache/conf". Now execute the exact command we used to do the initial replacement. That's it. We are finished modifying httpd.conf.
Restart the VMware Server MUI with the following command:
sudo /etc/init.d/httpd.vmware restart
Now the VMware Server MUI will only be listening for incoming connections on the management interface.
You should now be able to point a Web browser at https://MGMT_NIC_IP:8333 and see the server's VMware Server MUI. However, there are few things to consider.
While non-root users can log into the MUI to manage their VMs, only the root user can use the MUI to manage VMware Server itself. Ubuntu does not enable the root user by default, so if you intend to manage VMware Server through the MUI, you will have to enable the root user. You do this by setting a password for the root user with the following command:
sudo passwd root
Once you set a password for the root user, you will be able to log into the MUI with the root account.
Only users that have privileges on VMs can log into the MUI. That means that although you may have a user on the server where VMware Server is installed, you will only be allowed to log into the MUI if your user account has execute privileges on a VM's vmx file. We will discuss file permissions and what they mean to VMs later.
VMware Server Console
The Windows version of this guide had no dedicated VMware Server Console section, because installing VMware Server on a WindowsServer would also install the console, and an administrator could immediately start playing around with VMware Server through that.
Because we have installed VMware Server on an Ubuntu installation without X windows installed, we will need to install VMware Server Console on a separate computer. For the purposes of this guide, I will be installing VMware Server Console on an Ubuntu 6.10 (Edgy Eft), normal desktop installation.
It is quite easy to obtain the bits for the VMware Server Console. Just point a Web browser at the VMware Server, https://MGMT_NIC_IP:8333/ and the Web page that comes up will present you with a drop-down menu that lists the different versions of the VMware Server console. Select the version for Linux that is labeled "VMware Server Console for Linux (tar.gz)" and click on the button labeled "Download".
Once you have downloaded the tarball, open a shell and change directories to the location of the download. Deflate the tarball and then, as I recommended earlier with the VMware Server and VMware Serve MUI source directories, rename the directory from "vmware-server-console-distrib" to "vmware-server-console-distrib-1.0.1-29996" or whatever version it is. This will help keep straight later versions of the VMware Server Console you might download.
Change directories into "vmware-server-console-distrib-1.0.1-29996". To install the program, type:
The installation is straightforward and it is fine to accept all of the defaults.
Connecting to the VMware Server
The first step to connecting to the VMware Server server is to launch the newly installed VMware Server Console. If you are using GNOME or KDE, the installer will create a shortcut for you in your system menu. You can also launch the console by typing "vmware-server-console" from a shell (it is in /usr/bin, so it should be in your path).
When the VMware Server Console is started, it will ask you for the host name you would like to connect to. Enter the IP address of the management NIC on the VMware Server server. It will also ask for a user name and password. I have not confirmed this with VMware, but it appears that any user that exists on the VMware Server server can log into the server via the VMware Server Console. I tested this by creating a user from scratch; I did not set a shell for this user, create a primary group for this user or even create a home directory for this user, but this user was able to log in via the VMware Server Console.
Once you are connected to the remote server, proceed to the next section for instructions on how to create your first VMware on Linux VM.
About the author: Andrew Kutz is deeply embedded in the dark, dangerous world of virtualization. Andrew is an avid fan of .NET, open source, Terminal Services, coding and comics. He is a Microsoft Certified Solutions Developer (MCSD) and a SANS/GIAC Certified Windows Security Administrator (GCWN). Andrew graduated from the University of Texas at Austin with a BA in Ancient History and Classical Civilization and currently lives in Austin, TX with his wife Mandy and their two puppies, Lucy and CJ.