Windows VMware Player and Fedora 8 Linux Network

Document Sample
Windows VMware Player and Fedora 8 Linux Network Powered By Docstoc
					                            Windows VMware Player and Fedora 8 Linux
                                       Network Edition
                                   Computer Science Program
                                        Ken Gamradt
                                       January 9, 2009

This document describes the downloading and configuring of a Fedora 8 Linux virtual machine that runs
from Windows using VMware Player.
• The virtual machine runs on the Computer Science network using a Computer Science Linux
   account (this does not support student usage on campus).
• This document assumes that a basic knowledge of using Windows and Linux exists.

Requirements

•   15 GB of free disk space – do not use the C: drive if at all possible
       o D:\Virtual Machines is recommended for downloading and running the virtual machine
                  Replace D: with the desired drive letter
•   512 MB of free system memory
       o 1 GB of total system memory at a minimum
                  2 GB or more of total system memory is recommended
•   Fedora 8 Linux virtual machine (need to downloaded)
       o F8-32-Net.alz               roughly 2 GB in size
       o F8-32-Net.a00               roughly 2 GB in size
•   VMware Player (needs to downloaded)
       o VMware Player 2.5.1         or whatever the newest version is
•   ALZip archive tool – ALZ archive format used with virtual machine (may already be installed)
       o ALZip 6.7

Accessing the Files using a Web Browser




The required files, along with the installation guide, can be found through the following web site:

http://www.csc.sdstate.edu/~gamradtk/vm/index.html

Download all of the files under the “CS Faculty Network Version” section to the desired location.
• D:\Virtual Machines (replace D: with the chosen drive letter).
Extracting the Fedora 8 Linux Virtual Machine

If ALZip is not already installed then it will need to be installed now.
• Accepting all of the install defaults is recommended.
• Feel free to make adjustments as needed: installation location, program shortcut icon placement, …




Extract the virtual machine archive file by right-clicking on it and selecting the option shown above.
• Extract to D:\Virtual Machines\F8-32-Net\ (replace D: with the chosen drive letter).

File naming convention: F8-32-Net.alz (Windows does not show common file extensions by default)
• F8 – Fedora 8
• 32 – 32 bit version (x86/i386/i586/i686)
• Net – CS Faculty Network edition
       o Does require a network connection on the SDSU LAN
       o Does require a Computer Science Linux account
       o Does include a local Linux account if needed
                 Username: compsci         Password: abc123

Installing VMware Player

Double-click the downloaded VMware Player executable file (VMware-player-2.5.1-126130.exe).




•   Click Next when the Welcome to the Installation Wizard dialog appears.
•   Click Next when the Destination Folder dialog appears.
        o C:\Program Files\VMware\VMware Player\ (default location)
                 This can be changed by clicking Change… and browsing to the desired location.
•   Select the desired program shortcut icon locations when the Configure Shortcuts dialog appears and
    then click Next.
        o Checking the Start Menu Programs folder option is recommended at a minimum
•   Click Install when the Ready to Install the Program dialog appears.




•   Click Finish when the Installation Wizard Completed dialog appears.

Notes
• Once ALZip has been installed its download installation file may be deleted
• Once VMware Player has been installed its download installation file may be deleted
• Once the virtual machine archive files have been extracted they may be deleted
Starting a Virtual Machine with VMware Player

Click (or double-click) one of the VMware Player program shortcut icons to start it.




•   Select “Yes, I accept the terms in the license agreement” and then click OK when the License
    Agreement dialog appears.
       o This only appears the first time that VMware Player is used.




•   Click Open in the Commands section of the startup screen to select the virtual machine that the
    VMware Player will run.
•   The right screen shot shows that after a virtual machine has been run at least one time it is listed in
    the Recent Virtual Machines section of the startup screen.
        o Use this to start the virtual machine after the first run.
•   Browse to the folder where the virtual machine was extracted to and select the VMware
    Configuration File for the desired virtual machine.
        o D:\Vitual Machine\F8-32-Net\F8-32-Net.vmx
•   When the virtual machine is loaded for the first time it will detect that something has changed since
    the last time it was run (or from when it was built). It needs to know whether it was copied or moved
    so that it can make any necessary system setting adjustments.
        o Select “I copied it” and then click OK.
                     “I copied it” is the default and recommended option.




•   The left screen shot shows the GRUB boot manager.
       o GRUB provides a list of available operating systems.
       o The classroom and lab computers also list Windows XP Professional.
                   The classroom and lab computers dual boot operating systems.
       o VMware Player is running from a Windows host so both operating systems are available.
•   The right screen shot shows the Fedora 8 Linux login screen.
       o This is the exact same screen that appears on the classroom and lab computers.
       o Both environments are running identical Fedora 8 Linux installations.
       o Log into Linux using a Computer Science Linux account.
                   Or log into the local Linux account if needed
The above screen shot shows the desktop layout that is available with KDE 3.5 and Fedora 8 Linux.
• This is the exact same desktop that is available on the classroom and lab computers.




The above screen shots show the tool bar at the bottom of the window that surrounds the virtual
machine. The various components are briefly described here (from left to right):

•   Hard Disk:              indicates that a hard disk drive is active and available.
•   CD/DVD:                 indicates that an optical disk drive, CD/DVD, is active and available.
•   Floppy:                 indicates that a Floppy disk drive is active and not available.
•   Network Adapter:        indicates that a network adapter is active and available.
       o Clicking on the icon allows the networking mode to be changed.
                Changing the networking mode is not recommended.
•   Sound Card:             indicates that a sound card is active and available.
       o Because the install matches the classroom and lab install it may not fully support sound.
       o Additional software and configuration adjustments may be required.
•   Bluetooth:              indicates that Bluetooth support was detected but is not available.
       o Other plug and play devices will appear depending upon the system hardware configuration.

Note:
• The green circle displayed in the lower right portion of the icon indicates that it is connected to the
   virtual machine and available for use by the virtual machine.
Using External Media with the Virtual Machine




•   The left screen shot shows that USB devices plug and play and autorun with the virtual machine.
•   The right screen shot shows that CD/DVD disks autorun with the virtual machine.

Notes:
• Make sure that the virtual machine is selected by clicking on it before plugging in the USB device or
   inserting the CD/DVD disk.
• VMware disables autorun in Windows.
       o Windows will properly plug and play the device or disk but will not autorun them.




•   The left screen shot shows that a Removable Disk is active and available for use.
        o This occurred after a USB memory device was plugged into one of the USB ports with the
            virtual machine (the guest) selected.
                    Compare this to the tool bar screen shot on the previous page.
•   The right screen shot shows that a Removable Disk is active but not available for use.
        o This occurred after a USB memory device was plugged into one of the USB ports with
            Windows (the host) selected.
                    Compare this to the tool bar screen shot on the previous page.
•   Notice that clicking on the device icon allows the device to be connected to or disconnected from the
    virtual machine.
Shutting Down the Virtual Machine




•   Shutting down the virtual machine works exactly the same way as shutting down Linux works with
    the classroom and lab computers.
•   Select Log Out… from the K menu.
        o An alternative is to right-click an unused portion of the desktop and use the pop-up menu.
•   Select “Turn Off Computer” from the “End Session” dialog.
        o This shuts down the virtual machine and leaves Windows running.
                  It does NOT turn off the computer.

Optional Features

Adjusting Screen Size




•   Select “Control Center” from the K menu
•   Expand Peripherals and then select Display
•   Use the pull down list for “Screen size” to select a different setting.
       o 800 x 600 is the default.
Adjusting the Memory Requirement for the Virtual Machine




•   Select Change Memory Allocation… from the Troubleshoot submenu of the VMware Player menu
    located at the top of the virtual machine window.
•   The yellow triangle lists the recommended minimum amount of memory for a guest operating
    system.
•   The green triangle lists the recommended amount of memory for a guest operating system.
•   The blue triangle lists the recommended maximum amount of memory for a guest operating system.
•   The current virtual machine memory requirement is 512 MB.
        o In general, changing this amount is not recommended
                    More specifically, lower this amount is not recommended
        o Feel free to experiment with memory amounts between 256 MB and 784 MB in order to find
           a suitable compromise between the virtual machine (the guest) and Windows (the host).
                    256 MB to 512 MB with less than 2 GB of total system memory.
                    512 MB to 784 MB with 2 GB or more of total system memory.

Benefits

•   Have access to both Linux and Windows at the same time
•   When the virtual machine is updated the old version is simply deleted and the new version is
    downloaded and extracted using the methods described previously
Usage Suggestions

•   Use the network version on computers that are always connected to the SDSU LAN.
       o Office desktop computers
•   Use the standalone version on computers that are not connected to the SDSU LAN.
       o Office desktop computers
                   If SDSU LAN connectivity is not important or desired
       o Laptop computers
                   If there is enough free disk space configure both versions of the virtual machine.
                        • Network version when on campus
                        • Standalone version when off campus
                                o Make the data portable so that when an old virtual machine is deleted
                                   the data that is store in the local user account directory structure isn’t
                                   lost