After you configure a virtual machine, you can boot it for the first time and install a guest operating system. Refer to "VMware Application Reference" to see a list of which operating systems can be installed as guest operating systems.
The installation of guest operating systems is intended to differ as little as possible from their installation on a physical machine. If there are any additional steps or differences, however, they are noted in this chapter.
If you should happen to power on without a bootable disk you will see the message "Operating System not found." You can just put in the disk and press Reset.
The following general steps are required to install each guest operating system. However, Step 2 will vary for each guest OS; at this step be sure that you refer to the appropriate section, in this chapter for your guest OS.
To install a guest operating system in a VM:
If you took a break after configuring the VM and exited the VMware application, then launch VMware using the configuration file that you just defined. Enter:
You should see a virtual machine with the name of the configuration file in its title bar. You have not yet pressed Power On.
Note that at this point the mouse cursor can move anywhere on the screen. However, if you should happen to click in the VM window, the cursor can move only within that window. Managing the cursor's movement is described in "Using the Mouse Cursor" . If necessary, refer to that section now to understand how to move the cursor between the virtual machine and the host operating system.
Each disk that you have created for a VM is associated with a disk mode (disk modes are described in "The Disk Modes" ). The disk drive on which you are installing the guest operating system should be a persistent mode disk (persistent is the default).
Although you can use undoable mode, you must make sure that you apply the changes, in this case the installation of the guest operating system, at the end of the VMware session. If you do not apply the changes, then you will need to re-do the installation of the guest OS.
If you want to use nonpersistent mode, you should first install the guest OS while the disk is in persistent mode. Then you can power off to end the VMware session and change the disk mode to nonpersistent.
Instructions for this step diverge depending upon the actual guest OS. Please continue by turning to the appropriate section from the following list:
You may also want to refer to the documentation for the guest operating system.
You can press Escape while a VM is booting to see a window in which you can set the BIOS boot order, and if desired, access other BIOS Setup screens. (This is the same as pressing F2 during boot.) For example, when you carry files for a VM from one machine to another, the boot order might differ on the two machines and you might want to adjust it.
Once you have moved the mouse cursor into the VM window and clicked within the window, you cannot move the mouse cursor outside the window. Refer to "Using the Mouse Cursor" for instructions on how to move the mouse cursor out of the VM window when you want to use the host operating system.
After the guest operating system is installed you may need install and configure any additional network drivers desired for the VM. (No additional setup is required if the VM uses no networking.)
For more information on network setup, refer to "About VMware Networking" .
If you are installing a Windows guest OS, refer to "Installing the VMware SVGA Driver and Toolbox" .
If you are installing a Linux guest OS, refer to "Installing the VMware SVGA X server and Toolbox (Linux)" .
When you have completed the installation of the guest operating system, you can install and run the applications of your choice on the guest OS. These tasks are beyond the scope of this manual, as the behavior of user applications running on a guest OS should be the same as when run conventionally.
Windows NT
The installation of Windows NT is essentially identical to a conventional installation.
To install Windows NT:
You can boot off the Windows NT CD-ROM or use the setup diskettes.
NT does the hard disk format and recommends that you do not partition the hard drive.
You should see "AMD PCNET Family Ethernet Adapter" in the list of adapters. If you do not, you should select it from the list. You need not change any of the default settings for the adapter.
For improved performance or if you want to set your guest OS terminal display to anything other than 16 colors at 640 by 480, then you must download the VMware SVGA driver after you have installed Windows NT as the guest OS. See "Installing the VMware SVGA Driver and Toolbox" for instructions.
The installation of Windows 98 varies slightly from a conventional installation.
To install Windows 98:
We refer to this media as a CD-ROM although you can use either the Windows 98 CD-ROM or disk. The VM should now boot from the CD-ROM.
The setup program runs FDISK and then reboots.
Select this even if you have a SCSI CD-ROM drive.
The hardware setup program autodetects the "AMD PCNET Family Ethernet Adapter" network card; the default settings will work and should not be changed.
For improved performance or if you want to set your guest OS terminal display to anything other than 16 colors at 640 by 480, then you must download the VMware SVGA driver after you have installed Windows 98 as the guest OS. See "Installing the VMware SVGA Driver and Toolbox" for instructions.
Note that the DefaultColorDepth must be the same in the host operating system as in the guest operating system in order to use the SVGA driver.
The installation of Windows 95 is varies slightly from a conventional installation.
Some Microsoft Windows 95 OEM disks included with new computers are customized for those computers and include device drivers and other utilities specific to that hardware. Though you can install this Windows 95 OS on your actual computer you may not be able to install it in a VMware virtual machine. You may need to purchase a new copy of Windows to install in a VM.
Some Windows 95 distributions include instructions that do not include the steps to FDISK and FORMAT a C: drive. You must FDISK and FORMAT the VMware virtual IDE hard disk drives before running Windows 95 setup.
The following instructions are for the simplest case of one virtual IDE hard disk drive and one virtual IDE CD-ROM drive. Note the following suggestions if you have configured your VM differently:
To install Windows 95:
Make this selection even if your computer has a SCSI CD-ROM drive.
If you create a primary partition which is smaller than the size of the hard disk, then make sure the partition is marked Active.
If the cursor is not already within the VMware window, click in the window and enter CTR-ALT-DEL. If prompted on reboot to select a CD-ROM driver, select the first IDE CD-ROM driver from the list.
If you have multiple hard drives or CD-ROMs you may need to use a different drive (E:) in this prompt.
You must manually add the driver because Windows 95 does not detect it during the "Analyzing Computer" phase, even if you selected the Network Adapter detection option). To enable networking:
VMware's virtual disks support DMA transfers for better performance. You can enable this feature after installing Windows 95. To enable DMA transfers:
For improved performance, and if you want to set your terminal display to anything other than 16 colors at 640 by 480, then you must download the VMware SVGA driver. See "Installing the VMware SVGA Driver and Toolbox" for instructions.
DOS and Windows 3.11
The installation of Windows 3.11 and DOS 6.2 is essentially identical to a conventional installation.
To install Windows 3.11 or DOS 6.22:
You can install MS-DOS 6.22 using the MS-DOS 6.22 diskettes and WIN3.11 using the standard install diskettes.
VMware supports networking from WIN3.11 (or Windows for Workgroups). The ethernet driver should be Advanced Micro Devices PCNET Family (NDIS2/NDIS3).
Red Hat Linux
The following notes apply to Red Hat 5.0, 5.1 and 5.2 except when specifically noted.
To install Red Hat Linux:
Do you have any SCSI adapters? select "No"
select "add" (to start partitioning)
A suggestion is to make the swap equal to the RAM of the VM.
<Choose a Card>select "Generic VGA Compatible"
<Monitor Setup>select "Generic Monitor"
<Screen Configuration>select "Probe"
Refer to the S.u.S.E 6.0 manual during the install. Remember that you will only be able to run the Standard VGA16 Xserver without the support of VMware's X server.
To install S.u.S.E. Linux:
By default S.u.S.E 6.0 does not install the DHCP client. If you installed an Ethernet Adapter during configuration of your VM and you want to use DHCP, you should select this package. Otherwise you will have to allocate a static IP address for the VM.
When prompted to select the network card, select the AMD LANCE and PCnet (AT1500/NE2100). Make sure you set the following parameter correctly: io=0x300.
See "Installing the VMware SVGA X server and Toolbox (Linux)" .
Caldera OpenLinux 1.3
To install Caldera OpenLinux:
In the beginning, Caldera appears to detect no devices (no CD-ROMs, hard drives, or network cards). This is expected.
The VM may complain about 'Illegal Opcodes'. This is also expected and should not prevent a successful installation. The VM automatically attempts to boot from the hard disk before the CD-ROM. Because of this, after Caldera reboots the VM after partitioning and formatting the hard drive, the VM will appear to do nothing after the bios splash screen. That is, the screen will be blank.
The install should now continue normally.
When installing LILO, be sure to install LILO onto "the first hard drive" and not onto the primary partition. Installing onto the primary partition causes LILO to fail to come up during boot time and results in a black, blank screen after the bios splash.
You can now set up networking as usual per the Caldera instructions.
The glibc runtime library (glibc-2.06-1.i386.rpm) is located in the col/contrib/RPMS directory on the installation CD-ROM for Caldera 1.3.
See "Installing the VMware SVGA X server and Toolbox (Linux)" .