Red Hat Enterprise Linux 4.0

Support

This guest operating system is supported on the following VMware products:

General Installation Notes

Be sure to read General Guidelines for All VMware Products as well as this guide to installing your specific guest operating system.

The easiest method of installing Red Hat Enterprise Linux 4.0 in a virtual machine is to use the standard Red Hat distribution CD. The notes below describe an installation using the standard distribution CD; however, installing Red Hat Enterprise Linux 4.0 via the boot floppy/network method is supported as well. If your VMware product supports it, you may also install from a PXE server.

Before installing the operating system, be sure that you have already created and configured a new virtual machine.

Note: When creating the virtual machine, be sure to select the LSI Logic SCSI adapter. Red Hat Enterprise Linux 4.0 does not include a driver for the BusLogic SCSI adapter.

Note: Be sure the virtual machine is configured with at least 256MB of memory. If the virtual machine has less than 256MB of memory, Red Hat Enterprise Linux presents an error message as it loads certain VMware drivers.

Installation Steps

Note: Pay particular attention to the notes in step 4 about how to avoid installing an inappropriate kernel.

  1. Insert the Red Hat Enterprise Linux 4.0 CD-ROM in the CD-ROM drive.
  2. Power on the virtual machine to start installing Red Hat Enterprise Linux 4.0.
  3. Follow the installation steps as you would for a physical machine. Be sure to make the choices outlined in the following steps.
  4. VMware GSX Server only: In the Package Group Selection screen, choose Software Development and Select individual packages. In the Individual Package Selection screen, use the arrow keys to move down to System Environment/Kernel and press Enter. Be sure that kernel-smp is deselected (no asterisk should appear between the brackets). The SMP kernel is not supported in a GSX Server virtual machine. You do not need to change any other selections.
  5. Allow automatic partitioning of the disk to occur in the Automatic Partitioning screen or partition the virtual disk manually if you do not want to use the Red Hat defaults.
  6. You may see a warning that begins "The partition table on device <devicename> was unreadable. To create new partitions it must be initialized, causing the loss of ALL DATA on the drive." This does not mean that anything is wrong with the hard drive on your physical computer. It simply means that the virtual hard drive in your virtual machine needs to be partitioned and formatted.

    Click Yes to partition the drive.

  7. VMware GSX Server: If your computer is connected to a LAN that provides DHCP support, then in the Network Configuration screen, you may select the option Use bootp/dhcp. If you prefer, you may also set the networking parameters manually.
  8. VMware ESX Server: If you are using the vlance network adapter in your virtual machine and your computer is connected to a LAN that provides DHCP support, then in the Network Configuration screen, you may select the option Use bootp/dhcp. If you prefer, you may also set the networking parameters manually. If you are using the vmxnet network adapter in your virtual machine, use the network configuration tools in Red Hat Enterprise Linux 4.0 to configure your network connection after you finish installing the guest operating system.

This completes basic installation of the Red Hat Enterprise Linux 4.0 guest operating system.

VMware Tools

Be sure to install VMware Tools in your guest operating system. For details, see the manual for your VMware product or follow the appropriate link in the knowledge base article at www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=340.

Do not start the X server in the guest operating system until you install VMware Tools.

Known Issues

PAE Message During Installation

VMware Workstation: If your host computer has a processor that includes NX (no execute) technology you may get an error message during installation. The message says the guest operating system is trying to use PAE. The NX technology is present in AMD processors including Athlon64, Opteron and Sempron. It is also present in Intel EMT64-capable processors.

To avoid the problem, be sure the virtual machine is powered off, then use a text editor to edit the configuration (.vmx) file for the affected virtual machine. Add the following line to the file:

paevm="true"

You can then power on the virtual machine and install the guest operating system.

Clock in Guest Operating System May Run Too Quickly or Too Slowly

If the clock in your guest operating system runs too quickly or too slowly, use one of the workarounds described in the knowledge base article at www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=1420.

Enabling Sound After Installing Red Hat Enterprise Linux 4.0

VMware GSX Server: The sound device is disabled by default and must be enabled with the virtual machine control panel (VM > Settings) after the operating system has been installed. To set up the virtual machine to play sound, see Configuring Sound in the GSX Server documentation.

Guest Screen Saver

VMware GSX Server: On a Linux host with an XFree86 3.x X server, it is best not to run a screen saver in the guest operating system. Guest screen savers that demand a lot of processing power can cause the X server on the host to freeze.

Migration to a Different Processor

VMware GSX Server: VMware recommends you do not migrate a Red Hat Enterprise Linux 4.0 virtual machine between hosts when one host is running on an AMD processor and the other is running on an Intel processor.

During installation, Red Hat Enterprise Linux 4.0 chooses a kernel that is optimized for the specific processor on which it is running. The kernel may contain instructions that are available only on that processor. These instructions can have adverse effects when run on a host with the wrong type of processor.

Thus, a Red Hat Enterprise Linux 4.0 virtual machine created on a host with an AMD processor may not work if migrated to a host with an Intel processor. The reverse is also true: a Red Hat Enterprise Linux 4.0 virtual machine created on a host with an Intel processor may not work if migrated to a host with an AMD processor.

This problem is not specific to virtual machines and would also occur on physical computers. For example, if you moved a hard drive with a Red Hat Enterprise Linux 4.0 installation from an AMD machine to an Intel machine, you would experience problems trying to boot from that drive.