SUSE Conversations


The Complete Guide to Installing VMware Server in SLES 10 SP1



By: jhbown

April 18, 2008 6:49 pm

Reads:244

Comments:4

Rating:0

When I first started down this road, I was fairly new to SLES. So after crashing and burning more times than I care to remember, I decided to document the entire process. With any luck, this will save someone out there a great deal of time and effort.

Please keep a few things in mind:

This is one of many ways VMware Server can be installed. Your tastes (and mileage) may vary.

Root access is required.

As with all things Linux, commands outlined in this document are case sensitive.

Finally, note that VNC, PuTTY and/or Cygwin can be used if installing VMware Server remotely from a Windows workstation.

Part 1 of 2 – Installing VMware Server for Linux

  1. Update the host machine via YaST Online Update (YOU). If not already, install the following packages via Software Management.

    kernel-source
    gcc
    gcc-c++ (dependent on the former)
    make (part of a default SLES10 SP1 installation. Not sure about SLES 10, though)

    Click “Continue” if/when you’re presented with “In addition to your manual selections, the following packages have been changed to resolve dependencies”. In this case, glibc-devel, libmudflap and libstdc++-devel also need to be installed. Now may be a good time to reboot the machine as well. You should certainly reboot if prompted to by YaST.

  2. Download VMware Server for Linux and the corresponding Management User Interface (MUI) from the following website. The latter is not required, though it does add functionality. As of this writing, the current version of both is 1.0.4, build 56528. Note that registration is required in order to receive a serial number via e-mail.

    http://register.vmware.com/content/download.html

    The following commands will download the files into the user’s Home directory, as outlined in the following screenshots.

    wget http://download3.vmware.com/software/vmserver/VMware-server-1.0.4-56528.tar.gz

    wget http://download3.vmware.com/software/vmserver/VMware-mui-1.0.4-56528.tar.gz

    ls

  3. Unpack the newly downloaded tar files via the following commands.

    tar xzf VMware-server-1.0.4-56528.tar.gz
    tar xzf VMware-mui-1.0.4-56528.tar.gz

    After being unpacked, two new directories will appear in the user’s home directory.

    vmware-server-distrib
    vmware-mui-distrib

  4. Rename each directory via the “mv” command so they both have a suffix matching the build number. That way, in the future, when a new version is released/downloaded, the existing files won’t be overwritten.

    mv vmware-server-distrib vmware-server-distrib-1.0.4-56528
    mv vmware-mui-distrib vmware-mui-distrib-1.0.4-56528

  5. Move the two newly renamed directories to the /usr/local/src directory, again via the “mv” command. Note root access is required to do this, thus the “sudo” prefix.
  6. In order for the installation to succeed, the running kernel and the kernel source installed earlier must be the same version. This goes for gcc and gcc-c++ as well. To confirm this, issue the following command.

    rpm -qa kernel* gcc*

    If for some reason they don’t match, check to make sure the machine is properly updated. If you updated your running kernel earlier, you must reboot before going any further.

  7. Once the version numbers match up, issue the following commands.

    su -
    cd /usr/src/linux-2.6.16.54-0.2.5
    make cloneconfig; make modules_prepare

    This is what you’ll see when the command completes.

  8. Now that you’re back at a prompt, issue the following commands.

    cd /usr/local/src/vmware-server-distrib-1.0.4-56528
    List the files in said directory via ls to confirm the presence of the installer file, vmware-install.pl
    Begin the installation by typing ./vmware-install.pl

  9. When asked “In which directory do you want to install the binary files?”, press Enter to accept the default of /usr/bin.
  10. When asked “What is the directory that contains the init directories (rc0.d/ to rc6.d/)?”, press Enter to accept the default of /etc/init.d.
  11. When asked “What is the directory that contains the init scripts?”, press Enter to accept the default of /etc/init.d.
  12. When asked “In which directory do you want to install the daemon files?”, press Enter to accept the default of /usr/sbin.
  13. When asked “In which directory do you want to install the library files?”, press Enter to accept the default of /usr/lib/vmware.
  14. When asked the path “/usr/lib/vmware” does not exist currently. This program is going to create it, including needed parent directories. Is this what you want?”, press Enter to accept the default of yes.
  15. When asked “In which directory do you want to install the manual files?”, press Enter to accept the default of /usr/share/man.
  16. When asked “In which directory do you want to install the documentation files?”, press Enter to accept the default of /usr/share/doc/vmware.
  17. When asked “The path “/usr/share/doc/vmware” does not exist currently. This program is going to create it, including needed parent directories. Is this what you want?”, press Enter to accept the default of yes.
  18. When presented with “The installation of VMware Server 1.0.4 build-56528 for Linux completed successfully. You can decide to remove this software from your system at any time by invoking the following command: “/usr/bin/vmware-uninstall.pl”.

    Before running VMware Server for the first time, you need to configure it by invoking the following command: “/usr/bin/vmware-config.pl”. Do you want this program to invoke the command for you now?”, press Enter to accept the default of yes.

  19. NOTE: The “/usr/bin/vmware-config.pl” command must be re-issued if the kernel of the host machine is updated after VMware Server has been installed.
  20. When presented with “You must read and accept the End User License Agreement to continue. Press enter to display it.”, press Enter.
  21. Press “q” to exit the End User License Agreement.
  22. When asked “Do you accept?”, type “yes”.
  23. When asked “In which directory do you want to install the mime type icons?”, press Enter to accept the default of /usr/share/icons.
  24. When asked “What directory contains your desktop menu entry files? These files have a .desktop file extension.”, press Enter to accept the default of /usr/share/applications.
  25. When asked “In which directory do you want to install the application’s icon?”, press Enter to accept the default of /usr/share/pixmaps.
  26. When asked “None of the pre-built vmmon modules for VMware Server is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)?”, press Enter to accept the default of yes.
  27. When asked “What is the location of the directory of C header files that match your running kernel?”, press Enter to accept the default location. In this case, /lib/modules/2.6.16.54-0.2.5-smp/build/include.
  28. When asked “Do you want networking for your virtual machines?”, press Enter to accept the default of yes.
  29. Press “q” to exit.
  30. When asked “Do you want to be able to use NAT networking in your virtual machines?”, press Enter to accept the default of yes.
  31. When asked “Do you want this program to probe for an unused private subnet?”, press Enter to accept the default of yes.
  32. When presented with “vmnet8 is a NAT network on private subnet 192.168.196.0.”, press “q” to exit.
  33. When asked “Do you wish to configure another NAT network?’, press Enter to accept the default of No.
  34. When asked “Would you like to be able to use host-only networking in your virtual machines?’, press Enter to accept the default of Yes.
  35. When asked “Do you want this program to probe for an unused private subnet?”, press Enter to accept the default of yes.
  36. When presented with “vmnet1 is a host-only network on private subnet 172.16.201.0.”, press “q” to exit.
  37. When asked “Do you wish to configure another host-only network?’, press Enter to accept the default of No.
  38. In this step, there are a few things to consider BEFORE answering.

    You will be presented with the following.

    The default port : 902 is not free. We have selected a suitable alternative port for VMware Server to use. You may override this vale now. Remember to use this port when connecting to this server. Please specify a port for remote console connections to use [904].

    The installation is alerting you to the fact that port 902 will already be in use by SLES. Any value entered here will require the VMware Server Console, which defaults to port 902, to be either accessed with a non-default port or reconfigured.

    To access the VMware Server Console with a non-default port, the port number can simply be added at the end of the computer’s IP address with a colon. For example, 192.168.0.200:904.

    If all your VMware Servers use a non-default port, you can change this setting so that port 904 does not have to be added manually every time. This is done as follows.

    NOTE: The Windows and Linux changes mentioned below are to be made on workstations accessing the server via a local installation of the remote console, NOT on the server itself. In Windows, you may need to create the config.ini file. More can be found here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US &cmd=displayKC&externalId=1754

    Windows
    In the file C:\Documents and Settings\All Users\Application Data\VMware\VMware Server\config.ini, the entry authd.client.port must be changed as follows: authd.client.port=”xxx”. It is suggested that the port number be above 1024.

    Linux
    In the file /etc/vmware-console/config or /usr/lib/vmware-console/config, the entry authd.client.port must be changed as follows: authd.client.port=”xxx”. It is suggested that the port number be above 1024.

    Regardless, make a note of what non-standard port you’ve chosen. When finished installing VMware Server, that same port will need to be opened on the server’s firewall in YaST.

    When presented with “Please specify a port for remote console connections to use.”, press Enter to accept the default value, which in this case is 904.

  39. When asked “In which directory do you want to keep your virtual machine files?’, DO NOT press Enter. Because the default value contains a space, this should be changed. Change said value to /var/lib/vmware/vmfiles or whatever you like.
  40. When presented with “The path “/var/lib/vmware/vmfiles” does not exist currently. This program is going to create it, including needed parent directories. Is this what you want?’, press Enter to accept the default of Yes.
  41. When presented with “Please enter your 20-character serial number.”, enter the number you received from VMware when you registered.
  42. When presented with “The configuration of VMware Server 1.0.4 build-56528 for Linux for this running kernel completed successfully.”, installation is complete.

Part 2 of 2 – Installing the VMware Management User Interface

  1. cd /usr/local/src/vmware-mui-distrib-1.0.4-56528
  2. List the files in said directory via ls to confirm the presence of the installer file, vmware-install.pl
  3. Begin the installation by typing sudo ./vmware-install.pl
  4. When presented with “You must read and accept the End User License Agreement to continue. Press enter to display it.”, press Enter.
  5. Once read, press “q”, then “y”. NOTE: typing the whole word “yes” is not required.
  6. When asked “In which directory do you want to install the binary files?”, press Enter to accept the default of /usr/bin.
  7. When asked “What is the directory that contains the init directories (rc0.d/ to rc6.d/)?”, press Enter to accept the default of /etc/init.d.
  8. When asked “What is the directory that contains the init scripts?”, press Enter to accept the default of /etc/init.d.
  9. When asked “In which directory do you want to install the VMware Management Interface files?”, press Enter to accept the default of /usr/lib/vmware-mui.
  10. When asked “The path “/usr/lib/vmware-mui” does not exist currently. This program is going to create it, including needed parent directories. Is this what you want?”, press Enter to accept the default of yes.
  11. When asked “In which directory do you want to install the documentation files?”, press Enter to accept the default of /usr/lib/vmware-mui/doc.
  12. When asked “The path “/usr/lib/vmware-mui/doc” does not exist currently. This program is going to create it, including needed parent directories. Is this what you want?”, press Enter to accept the default of yes.
  13. When presented with “The installation of VMware Management Interface 1.0.4 build-56528 for Linux completed successfully. You can decide to remove this software from your system at any time by invoking the following command: “/usr/bin/vmware-uninstall-mui.pl”.

    Before running VMware Management Interface for the first time, you need to configure it by invoking the following command: “/usr/bin/vmware-config-mui.pl”. Do you want this program to invoke the command for you now?”, press Enter to accept the default of yes.

  14. When asked “Set the number of minutes before an http session times out. (This is the length of time before someone connecting to VMware Management Interface will be logged out) [60]”, press Enter to accept the default of 60.
  15. When presented with “The configuration of VMware Management Interface completed successfully.”, installation is complete.
  16. Start YaST, then select “Security and Users, then “Firewall”. On the left side of the screen, select “Allowed Services”, then click the “Advanced” button in the opposite corner of the screen. Under “TCP Ports”, enter “8333”. This port is specific to the MUI. We also need to open port 904 for the VMware Server console. Multiple entries need to be separated by a space, not a comma. Click “Next”, then “Accept”.

You can now reach your new VMware Server in Firefox via the MUI by navigating to https://ip_address_of_server_running_the_mui:8333.

There will also be an option to download a copy of the VMware Server console. Once installed, you can reach the VMware Server console by entering ip_address_of_server_running_vmware:904

ENJOY!

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Tags:
Categories: SUSE Linux Enterprise Server, Technical Solutions, Virtualization

Disclaimer: As with everything else at SUSE Conversations, this content is definitely not supported by SUSE (so don't even think of calling Support if you try something and it blows up).  It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.

4 Comments

  1. By:mfaris01

    Looks very thorough. I can’t wait to try it in the lab!
    Thanks for the article!

    Mike..

  2. By:CARAGIRL

    Thanks for taking so much time…I’ll be looking for more of your work.

    What a great nugget!

    Cheers, Caragirl

  3. By:tajudy

    You really saved me a lot of time. I have had only limited exposure to Unix years ago and this was a real help. Thanks!

  4. By:saasp

    Great installation guide!

    Make sure before you start packets xorg-x11-libs-32bit, zlib-32 and pam-modules-32bit are installed as well.

    If you want to connect with VMware server console
    add vmware-authd 904/tcp (or whatever port you use) in /etc/services and
    create links in your default runlevel so xinetd starts without user interception.

Comment

RSS