[[Category:OPS235]]{{Draft}}{{Admon/importantcaution|The course schedule, labs, and links are subject to changeTHIS IS AN OLD VERSION OF THE LAB|'''This is an archived version.|Check with Do not use this in your professor for details and changes specific to your sectionOPS235 course.'''}} =OPS235 Lab 2: Fedora 16 17 Installation Methods (on Virtual Machines: fedora1, fedora2, fedora3)=

:* '''Software testing''' -- Using multiple operating systems simultaneously on a single computer for testing and experimentation.:* '''Network simulation''' -- Testing network services, protocols, and security scenarios with a small number of computers.:* '''Isolation''' -- Protecting multiple sets of data by storing them on multiple virtual machines. If one of the virtual machines is compromised, the data on other virtual machines is still protected.:* '''Server consolidation''' -- Reducing the number of physical servers in a network by moving physical machines to virtual machines. This saves hardware, administration, cooling, and electricity costs, and it can increase the utilization of hardware (by ensuring that the hardware is not under-loaded).:* '''Load-balancing and disaster recovery''' -- It is possible to migrate virtual machines between different physical machines, to ensure that a workload is balanced across multiple computers, to allow routine hardware maintenance and upgrading, and to compensate for hardware failure or other disasters. {|cellpadding="8" width="100%"|- valign="top"| '''In this lab, you will create three virtual machines'''. This also gives you an opportunity to experiment with different ways of installing Fedora. Later in this course you will install another operating system distribution in a virtual machine.

You should already have both a '''Fedora installation DVD ''' and a '''Fedora LIVE CD'''. In both cases, the boot media (which you used to load the installation software) and the installation source (where the software that got installed came from) were the same: your CD/DVD provides both. However, the Fedora (and most other Linux distributions) permits you to use any combination of boot media and installation media:

* '''Installation In both cases, the boot media (which you used to load the installation software) and the installation source (the software that got installed) were the same: your CD/DVD provides both. However, the Fedora (and most other Linux distributions) permits you to use any combination of boot media and installation media: |{|border="1" cellpadding="3" width="100%"|-! Method! Boot Media! Install. Source:'''** |-! CD or DVD** ! ✓! ✓|-! Hard diskDisk! ✓** ! ✓|-! USB flash driveFlash Drive** ! ✓! ✓|-! Network HTTP or NFS software (http/nfs repository)! ✓! ✓|-! PXE Network Boot! ✓! X|} |}

==Required Materials (Bring to All Labs)Prerequisites==

* '''Fedora 16 LIVE CD''' - You can burn this onto a CD-R in the Open Lab* '''Fedora 16 x_64 Installation DVD''' Completion and Instructor "Sign- You can burn this onto a DVD-R in the Open off" of Lab (or burn image onto a DVD+R if you are using the Freedom Toaster).* '''SATA Hard Disk''' (in removable disk tray)* '''USB Memory Stick''' (minimum 64M)* '''1: [[OPS235 Lab Logbook (Lab1 Reference Sheet)''' (to make notes and observations).1]]

==Linux Command Online Reference==Each Link below displays online manpages for each command (via [http://linuxmanpages.com/ http://linuxmanpages.com])::* Completion of Lab 1'''virsh''' (Refer to Fedora Virtualization Guide link in the "Resources on the Web" section): * [[OPS235 Lab http://linuxmanpages.com/man1/gzip.1].php gzip / gunzip]

== Resources on the Web =={|cellpadding="8" width="100%"|- valign="top"| '''Virtualization''':* <span style="background-color| '''Live Image Installation:yellow;font-weight'''| '''Network Installation:bold'">[http''| '''Kickstart Installation://docs.fedoraproject.org/virtualization-guide/f13/en-US/html/ Fedora Virtualization Guide]</span>'''

'''Installation Methods|- valign="top"|[http:'''//docs.fedoraproject.org/virtualization-guide/f13/en-US/html/ Fedora Virtualization Guide]* Live Image Installation|** [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Fedora_Live_Images/ Fedora 16 17 Live Image Guide]** [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Quick_Start_Guide/ Fedora 16 17 Installation Quick Start Guide]* '''Network Installation:'''|** [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/ Fedora 16 17 Installation Guide]*** [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/ch-Preparing-x86.html#s1-steps-network-installs-x86/ Preparing for a Network Installation]*** [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/ch-Preparing-x86.html#s1-steps-network-installs-x86 Performing a Network Installation]* '''Kickstart Installation:'''|** [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/ Fedora 16 17 Installation Guide]*** [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/sn-automating-installation.html Automating the Installation with Kickstart]*** [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/ch-kickstart2.html Kickstart Installations]*** [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/ch-redhat-config-kickstart.html Kickstart Configurator]

{{Admon/tip|Performing this Lab off the Seneca network(eg. at home)|'''It is recommended to perform this lab in one of Seneca College's labs'''. This lab uses servers which are on the Seneca network and which are not available from other locations (such as your home). If you attempt this lab from another location, adjust the belmont.senecac.on.ca URLs to point to another [http://mirrors.fedoraproject.org/publiclist Fedora mirror server] -- note that you may need to change the directory name as well as the server name. The installation of the '''fedora3''' virtual machine <u>must</u> be done at Seneca.}}

===Investigation 1: How do In this investigation, you will install Fedora?==={{Admon/important | Logical Volume Management | Fedora uses a type of storage management called Logical Volume Management (LVM). In LVMfrom your live disc, disk partitions are called Physical Volumes (PVs) and provide storage to a Volume Group (VG). This storage is then split into various Logical Volumes (LVs). The advantage to observe the differences between this scheme is that you can change LV size and you can add and remove PVs after type of installation. For example, you can add a new disk to your system and then increase the size of your existing filesystems using that extra disk space. ''Please be careful to enter all LVM information accurately, including the VG and LV names.'' We will investigate and manipulate LVM in future labsDVD installation previously performed.}}

# After booting from the Installation DVD, at the Welcome ==== Screen choose "Install or upgrade an existing system" to launch the Graphical installation program and select the following options (you can use the media test to verify that your DVD burned correctly -- It will take some time -- otherwise, skip it):#* Language - English#* Keyboard Configuration - U.S. English#* Type of devices: Basic Storage Devices#* There should only be one storage drive listed - select it#* If you get a warning that the drive may need to be initialized, it is because your drive is new and contains no partitition table. Select "Re-Initialize"#* Set your hostname to - f13host (one word, no space, all lowercase)#* Root Password: enter a password of your own choosing. Pick one that is really, really hard to guess to protect your system. (Recommendation: use the first letter and all the punctuation from a favorite phrase or song verse. For example, "To be or not to be, that is the question!" could become the password "Tbontb,titq!").#* Disk Partition Setup - Specify a Custom Layout, and then set up the installation with this configuration:#** Find your existing 300MB partition (/dev/sda1). Edit this entry so that the mountpoint is /boot and is formatted as an ext3 filesystem.#** Don't touch the other existing 300M partition (/dev/sda5).#** Create 4 new LVM Physical Volumes that are 25000 MB in size. Set the File System Type to Physical Volume (LVM). Should be /dev/sda6 to /dev/sda9.#** Create an LVM Volume Group. Set the Volume Group Name to '''vg_main''' and set the Physical Extent size to '''4MB'''.#** Click on the Add button (within the "Make LVM Volume Group" window) to create a logical volume within that volume group:#*** Mount point / (root), filesystem type ext4, logical volume name '''root''', size 90000MB.#* Say yes to continue without a swap partition.#* Say yes to format /dev/sda1.#* Accept Boot Loader defaults.#* Accept Graphical Desktop and repository defaults.# Proceed with the installation. '''Note how long it takes to perform the installation.'''# Reboot using the controls on the screen. When the system starts, it will ask you some final configuration questions.#* Check the License Agreement. What license is used for the Fedora distribution? What activities do have restrictions and obligations?#* Create a user account for yourself using the same name as your learn account.#* Set date and time. Normally, you would want to enable Network Time Protocol, but since we will be experimenting with the networking turned off in later labs, leave it disabled.#* Click on Do Not Send Hardware Profile.#* Finish the post-installation customization, wait for the login screen to appear, and then login to your Learn account.Shot Thumbnail Reference ====

Answer {{Admon/note|Virtual Machine Screen Shots Thumbnails|While performing the Investigation 1 question in your lab log bookVirtual Machine setup, click on the thumbnails below to provide a '''"visual reference"''' while performing this section.}}

{{Admon/tip|Forcing the Resolution on the Projector|The podium computers in the lab rooms are connected to a video splitter. This splitter then connects to both the LCD screen on the podium and the projector at the front of the room. However, the splitter prevents the computer from successfully querying the LCD or screen to find the supported resolutions, and Fedora therefore selects a very low (safe) resolution. If you are using a podium system, you can force the native 1680x1050 resolution of the LCD display using [http://matrix.senecac.on.ca/~chris.tyler/fedora-scripts/1680x1050 this script].}}cellpadding="8" width="100%"

===Investigation |[[Image:Virt-manager1.png|thumb|125px| '''Virtual Machine Manager:''' Create a New Virtual Machine]]|[[Image:Virt-manager2.png|thumb|100px|'''Step 1 of 5:''' Create a New Virtual Machine ]]|[[Image:virtual-manager3.png|thumb|100px|'''Step 2of 5:''' Create a New Virtual Machine ]]|[[Image:virtual-manager4.png|thumb|100px|'''Step 3 of 5:''' Create a New Virtual Machine ]]|[[Image:virtual-manager5.png|thumb|100px|'''Step 4 of 5:''' Create a New Virtual Machine ]]|[[Image:virtual-manager6.png|thumb|100px|'''Step 5 of 5: How many files packages and files are installed on the system?===''' Create a New Virtual Machine ]]|}

Record # In the commands used and Virtual Machine Manger, click on the output generated icon to ''Create a Virtual Machine'' in the upper-left corner: <br />(refer to '''Virtual Machine Manager''' thumbnail above).# A window will appear with the title ''New VM''. There are five steps to be completed; click Forward after each step:# '''Step 1 of 5:''' Enter the following stepsvirtual machine (called '''fedora1''') name and select '''Local install media''' (refer to ''Step 1 of 5'' thumbnail above).# '''Step 2 of 5:''' '''Insert the CDROM or DVD containing the Fedora Live Disc image. Wait a moment for the disc to be recognized''', then select '''Use CDROM or DVD''' as the install media. Set the ''OS type'' to '''Linux''' and the ''Version'' to '''Fedora 17''' (refer to ''Step 2 of 5'' thumbnail above).<!-- {{Admon/tip|Using an ISO image|Instead of using a physical CD or DVD, you can use an ISO image of a CD or DVD. The virtualization software will make this ISO image appear like an actual CD within the virtual machine. Because hard disks are faster then optical discs, this will work faster than an actual CD/DVD.}}{{Admon/note|Choosing the operating system type and version|The purpose of the ''OS type'' and ''Version'' fields is to fine-tune some of the virtual machine settings for best performance. The VM will work even if these are set incorrectly.}} --># '''Step 3 of 5:''' Set the memory to '''768 MB''' and the number of CPUs to '''1''' (refer to ''Step 3 of 5'' thumbnail above).# '''Step 4 of 5:''' This next step creates a disk file that will be used to simulate the virtual machine's disk drive. Select a size of '''10 GB''' and checkmark the box labeled '''Allocate entire disk now''' (refer to ''Step 4 of 5'' thumbnail above).# '''Step 5 of 5:''' Review the options that you have selected. '''Make a note of the storage location.''' If anything needs to be changed, use the ''Back'' button to go back and edit it; otherwise, click '''Finish''' (refer to ''Step 5 of 5'' thumbnail above).

# To find all {{Admon/important|Removing and Recreating VMs|If for some reason the mount pointsuser wants to remove a Virtual Machine, enter they can right-click the command: <code>mount</code>#* Study the output VM, and record all the mount points select delete in your log book.# The name of the installation log file is <code>/root/installVirtual Machine Manager.log</code> -- It is an ASCII file (how can you be sure?) and can be viewed with recommended to '''"delete the <code>less</code> command. # You can make use of this image file to determine how many packages have been installed: complete the following command to count the number of packages listed " in the installation log file:#* <code>grep ________________ /root/installremove VM dialog box when removing and then recreating a VM'''.log | wc -l</code># Using the <code>rpm</code> commandNote: If you can also use the following commands fail to list all properly remove the installed packagesVM image file, and it may affect the total number of packages installed:#* <code>rpm -q -a</code>#* <code>rpm -q -a | wc -l</code>#* <code>rpm -qa | wc -l</code># The <code>-q</code> option means query, and hard disk size for the <code>-a</code> option means all new VM (in other words, query all installed software packages)i. Did you get the same number of packages from the above two methods?# Some of the files on your system were installed with the software packages, and some were created by system activity (for example, by creating your Learn account and by logging in)e. If you know use the package name (from the <code>install.log</code>), you can list all the files that were installed from the package by using the following command:#* <code>rpm -q -l package_name</code># This combines the <code>-q</code> (query) option with the <code>-l</code> (list filenames) optionold smaller size.# You can pipe the outupt through <code>wc -l</code> Make certain to count the number of lines:#* <code>rpm -ql package_name| wc -l</code># Using what you learned in steps 3, 4, and 8, get a count of the total number of files installed by all of the software packages on your system.# To find out the name remove that you have assigned VM image file prior to your Linux system, enter the command: <code>hostname</code># To find out the kernel version of your GNU/Linux workstation and the date it was created, enter the command: <code>uname -r</code># To find out all the system processes running on your GNU/Linux workstation, enter the command: <code>ps -ef</code># To capture the list of all the system processes to a file called <code>ps.lst</code>, enter recreating the command: <code>ps -ef > psVM.lst|''</code># Copy the installation log file <code>/root/install.log</code> and the file ps.lst to a USB memory key, or scp to your matrix account as a backup.'}}

=== Investigation 3: What is {{Admon/note|Fedora LIVE CD Install Screen Shots Thumbnails|While performing the Fedora 17 LIVE CD install, click on the thumbnails below to provide a runlevel? ==='''"visual reference"''' while performing this particular Fedora installation.}}

Most current Linux systems use some variation |[[Image:fedoralive1.png|thumb|100px| The Virtual Machine will now start.]]|[[Image:failedtoload.png|thumb|140px| '''Ignore and close the "Failed To Load" dialog box'''. Search for the panel on the upper-left-hand side of the init system originally developed for Unix screen.]]|[[Image:fedoralive2.png|thumb|140px|Login to the VM and double-click:<br /> '''Applications'''<br />>'''System V (called Tools'''<br />>'''Install to Hard Disk'''.]]|[[Image:selectstorage1.png|thumb|100px|Select '''Specialized Storage Devices''']]|[[Image:selectstorage2.png|thumb|100px|Select '''Virtio Block Device'''.]]|[[Image:finishcdinstall.png|thumb|100px|You will get the ''Firstboot'' configuration questions during the boot process.]]|}<ol> <li value="sysvinit") or a newer version called "upstart8">'''The virtual machine will now start'''. Select the default menu item labelled: '''Start Fedora 17'''. The virtual machine is running from the live disc at this point, and no software has been installed on the ''hard drive'' of the virtual machine.</li></ol>

These systems employ <ol> <li value="9">Login to the VM and click: '''Applications'''>'''System Tools'''>'''Install to Hard Drive'''. The installation program, similar to the one used when installing Fedora in Lab 1, will appear. You will get a warning at one point during the concept of installation process that the disk "runlevelsMay contain data" or "may need to be re-initialized" -- groups of software this is simply a warning that can be selectedthe virtual disk is completely blank, so that and it is safe to proceed with the system can be run in various modesinstallation. In Fedora systems, these runlevels are used:</li></ol>

{{Admon/note|classVirtual Machine Screen Size|The virtual machine screen size will change resolution as it switches from text to graphics mode. Use the VM menu option View>Resize to VM to resize the window to show the entire VM display. If this is larger than your screen size, use View>Scale Display>Always to scale the image so it fits on your screen.}}<ol> <li value="mediawiki10" >During the installation process, when prompted for a storage device, first select '''Specialized Storage Devices''', and then select the '''Virtio Block Device''' option.</li> <li>When prompted for the hostname, enter '''fedora1''', and when prompted for the timezone, select '''Toronto - Eastern Time Ontario''', and when asked about storage, select '''Use All Space'''. '''Use the default values for all other fields.''' Notice that the installer does not ask you what software should be installed; compare the installation time to the amount of time it took to do your Lab 2 installation. Record this information in the '''table contained in Investigation 4'''.</li> <li>When the installation is complete, click on the '''reboot''' button at the bottom right-hand corner of the screen.</li></ol> <ol> <li value="13">Start the VM from its disk image. This can be done graphically by selecting the Virual machine name, and then clicking on the '''Open''' button, and then click the '''play''' button when the next screen appears (or by selecting Virtual Machine>Run from the virtual machine menu). You will get the ''Firstboot'' configuration questions during the boot process (asking you to create a user, set the date and time, and optionally send the hardware profile to the Fedora Project). Create a user with the same name as your Matrix account.</li> <li>Login using the new user account.</li></ol> {{Admon/note|Network / Service Considerations|Please perform the tasks below in order allow these Fedora systems to be able to communicate with each other. '''Failure to properly perform these operations can cause problems in future labs'''.|}} <ol> <li value="15">Enable SSH access to your virtual machine with these commands (semi-colon allows commands to be run in sequence):<br /> <code>service sshd start; chkconfig sshd on</code></li> <li>Find out the IP address of your virtual machine: <code>ifconfig eth0</code> </li> <li>Enter the following command on your virtual machine to create a firewall exception to allow ssh traffic into the machine:<br /> <code>iptables -I INPUT -p tcp -s0/0 -d0/0 --dport 22 -j ACCEPT</code></li> <li>Confirm that you can ssh to your virtual machine from the host (your main Fedora installation): <code>ssh ''IPaddress''</code></li></ol> {{Admon/tip|Switch to Virtual Machine Manager Window|If you are currently in a Virtual machine, but want to switch to the Virtual Machine Manager Window, simply click '''Activities'''> '''Select the Virtual Machine manager window'''.}} '''Answer the Investigation 1 observations / questions in your lab log book.''' == Investigation 2: Installing from the Network == {{Admon/tip|Authenticate to the network|The rest of this lab uses network access.''' Be sure to authenticate to the network using your browser before proceeding'''.}} === Introduction === It is possible to install Fedora entirely from the network. In this investigation, you will install Fedora from a webserver on Seneca's LAN. ==== VM details ==== * '''Name:''' fedora2* '''Boot media:''' Network installation* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/17/Fedora/x86_64/os/* '''Memory:''' 1024MB* '''Disk space:''' 20GB* '''CPUs:''' 1 ==== Steps ====# Create the VM (called '''fedora2''') as you did with the ''fedora1'' virtual machine, except:#* In '''step 1 of 5''', set the installation type to '''Network Install (HTTP, FTP, or NFS)'''.#* In '''step 2 of 5''', provide the location of the software source by providing the URL http://belmont.senecac.on.ca/fedora/releases/17/Fedora/x86_64/os/#* In '''step 2 of 5''', set the ''OS Type'' to '''Linux''' and ''Version'' to '''Fedora 17'''. # Observe the boot process. How is it different from booting from an optical disc (CD/DVD)?# Start the installation process (make certain to use information in the ''VM Details'' section above).# When you get to the disk partitioning step, select '''Use All Space''' and enable the checkbox labelled '''Review and modify partition layout'''.If an dialog box displays a permissions problem, then click yes to proceed. On the next screen, change the logical volumes as follows:#* Reduce the size of the root LV to '''8000 MB'''.#* '''Add a logical volume with a size of 2000 MB and a mountpoint of /home''' (you can name it whatever you want, and use '''ext4''' as the file-system type).# On the software selection screen, select '''Graphical Desktop'''.# '''On the same screen, select the "Fedora 17 - x86_64" and the "Fedora 17 - x86_64 - Updates". Leave "Installation Repo" selected. ''DO NOT'' enable the "Test Updates" repository'''.# Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations.Record this information in the '''table contained in Investigation 4'''. '''Answer the Investigation 2 observations / questions in your lab log book.''' == Investigation 3: Installing from the Network using Kickstart == === Introduction === When Fedora is installed using the techniques you have used so far, the user is asked a number of questions. In some situations, it is better to provide the answers to these questions in a file rather than answer them individually. This type of file is called a ''kickstart'' file. In this investigation, a kickstart file is provided for you. You can also create or modify a kickstart file using a regular text editor or a graphical tool. ==== VM details ==== * '''Name:''' fedora3* '''Boot media:''' Network installation* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/17/Fedora/x86_64/os/* '''Kickstart location:''' http://www.drivehq.com/file/df.aspx/shareID10606286/fileID1269952040/Fedora17-kickstart.cfg* '''Memory:''' 1024MB* '''Disk space:''' 15GB* '''CPUs:''' 1 ==== Steps ====# Create the VM as you did with the ''fedora2'' virtual machine, specifying a network install as before, except:#* In step 2 of 5, after entering the URL for the installation source, click on the '''URL Options''' control.#* Enter the Kickstart URL: http://www.drivehq.com/file/df.aspx/shareID10606286/fileID1269952040/Fedora17-kickstart.cfg # Observe the installation. How is it different from booting from an optical disc (CD/DVD)?# Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations. # What happens when the installation is finished?# '''Take a look at the kickstart file (using the URL you entered) to <u>determine</u> the root password as well as the name and password for the first user account'''.# Boot the virtual machine and log in (use the user ID and password information from the previous step). Compare the experience to the first time you booted the other virtual machines.Record this information in the '''table contained in Investigation 4'''. '''Answer the Investigation 3 observations / questions in your lab log book.''' == Investigation 4: Updating and Comparing the VMs == # In each VM, run this command: <code>yum update</code># Record the answers to these questions in your log book:#* How long did it take to run on each VM? How many packages were updated?#* Why does it take longer in some VMs than others? Complete the following table (and transfer into your lab2 log-book notes): {|border="1"width="100%" cellpadding="5"|-!Runlevel||f17host||fedora1||fedora2||fedora3|-|'''Installation Method'''||Installation Disc||Live Disc||Network Installation||Network Installation + Kickstart|-|'''Packages Installed'''|| || || |||-|'''Updates Installed immediately after installation'''|| || || |||-|'''Software could be selected during installation'''|| || || |||-!Description|'''Disk layout could be selected during installation'''|| || || ||

|0'''No questions asked during installation'''|| || || ||Halt (powers off the system)

|1'''Total installation time''' (after installation questions)|| || || ||Single-user maintenance mode, network not running, character-mode display

|2|''Not normally 'Amount of disk space used - originally meant: Multi-user mode, network not running, character-mode display'''|| || || ||

|3'''Questions asked during first boot'''|| || || ||Multi-user mode, network running, character-mode display

|4|''Not normally used'Advantages of this type of installation'''|| || || ||

|5'''Disadvantages of this type of installation'''|| || || ||Multi-user mode, network running, graphical user interface

|6'''This type of installation is recommended for...'''|| || || ||Reboot

{{Admon/note|Different runlevel systems|Various Linux distributions may use == Investigation 5: Managing Virtual Machines from the runlevel numbers differently. For example, on some Debian/Ubuntu systems, the default (standard) runlevel is 2.}}Command Line ==

In order {{Admon/note|Manage virtual machines from the host|The commands used to implement runlevels, init uses a configuration file manage virtual machines must be executed on the host (your disk pack) and not inside a number of script files:virtual machine.}}

# Start the ''fedora1'' virtual machine, and stop the ''fedora2'' and ''fedora3'' virtual machines.# Switch to the f19host machine, and open a shell terminal.# Enter these commands into your f19host machine and note the result:#* <code>'''virsh list'''</etccode>#* <code>'''virsh list --all'''</inittabcode>#* <code>'''virsh list --inactive'''</code> is # Now, shut-down your fedora1 VM normally, and close the configuration file, which sets fedora1 VM window. Make certain NOT to close the default runlevelVirtual Machine Manager main window.* # Switch to your terminal and issue the command: <code>'''virsh start fedora1'''</etc/rccode># Check to see if your fedora1 VM is now running.d/init.d# Switch to the terminal and issue<code>'''virsh list --all'''</code> is and confirm the status of the fedora1 VM.# There are other commands that can be used (such as suspend, or shutdown). The "shutdown" command may not always work since it sends a directory of scriptsrequest to "shutdown virtual machine gracefully", but may not always work.Why do you think it is useful to have commands to manipulate VMs?

In order {{Admon/note|Virtual Machine Does not Shutdown from Command|If the Virtual machine fails to determine which of shutdown from the startup scripts should be executed in each runlevel, the one directory per runlevel is created (<code>virsh shutdown</etc/rc.d/rccode> command, then you can go to the '''Virtual Machine manager''' and '''halt''' or '''Xshutdown'''.d</code>within the VM itself, where then you can click the '''XPowerOff''' is button in the runlevel)VM window. This directory is filled with symbolic links You'll want to avoid a forced shutdown since those are equivalent to yanking the cord out of the startup scripts in <code>/etc/rc.d/init.d</code>wall on a physical machine!|}}

Answer the == Investigation 3 question.6: How do I backup a virtual machine? ==

=== Investigation 4{{Admon/important|Backing up VMs|There are two general processes in order to back up your images: What <ol><li>'''Compressing your images''' (also recommended to backup up to external storage USB Key) using the '''gzip''' command.</li><li>'''Backup the VM xlm configuration file''' (preferably to USB key) using '''virsh''' shell command to add VM to virtual machine manager list (in the event that the HOST machine is "wiped" and re-installed, but VM images and xml configuration files have been backed up external storage).</li></ol><br />Taking the time to backup the image of the Operating System's file system allows the user to return to a '''"restoration point"''' using the network configuration? ==='''gunzip''' command in case something bad occurs to the OS during a lab.<br />Failure to take the time to make and confirm backups can result in loss of lab work for the student!|}}

# To check Shut down all of the network configuration settings obtained from virtual machines.# Change to the DHCP server, run directory <code>/var/lib/libvirt/images/</code>. Note the following commands, describing size of the output files in your log book:this directory. What do these files contain?#* ifconfig#* route#* netstat -rn#* nslookup (at Make a compressed backup of the <code> prompt, enter fedora3.img</code> file to your home directory with this command: <code>'''gzip < fedora3.img > ~YourUserId/fedora3.img.backup.gz'''</code><br />('''Note: Make certain to use the word redirection signs "<"serverand " (do not type >" properly in the quotescommand!''') and record {{Admon/caution| Make sure the outputbackup is successful!|If there are any error messages, '''DO NOT''' proceed past this point. Type exit You're going to leave nslookup).# Find destroy your fedora3 virtual machine and restore it using the following information in backup you have created -- if there are any problems with the output of the above commands:backup, you will not have a working virtual machine, and will have to re-install it.}}#* MAC address (physical or hardware address) of the ethernet network interface<ol>#* The IP address (logical address) assigned by <li value="4">Compare the DHCP server#* The default route (gateway)#* The DNS nameserver Answer size of the Investigation 4 questioncompressed and original files.</li> === Investigation 5: How do You Secure <li>Start the Grub Boot Loader? ==='''''fedora3''''' VM.</li> <li>'''Make certain that you are in your fedora VM and <u>not</u> in your Fedora main system!'''</li>{{Admon/caution|Duplicate UUIDs|Before proceeding, use the <li>Wreck <codeu>mountonly</codeu> your fedora 3 system! Try this command to check to see which filesystem is mounted on inside the mount point fedora3 virtual machine: <code>'''rm -rf /boot*'''</code></li> <li>Shut down the VM. If you tried to start the Fedora3 VM, it is would not boot since all system files have been removed!</li> <li>Restore the original image from the backup in your home directory by typing this command: <code>'''gunzip < ~YourUserId/devfedora3.img.backup.gz > fedora3.img'''</sda5code></codeli> <li>, Restart the VM. Is it is the wrong filesystemworking normally?</li> <li>Create compressed backups of your other virtual machines. This may be caused by </li></ol><ol><li value="12">You should make a duplication copy of serial numbers which is the result of Lab 1; xml configuration file in case you "wipe" and re-install the host machine, and want to add a restored VM backups to the virtual machine manager list. We will demonstrate using the fedora 3 xml configuration file, and prove that a "clone" can fix this problem with this series of commandsbe added to your list.Please perform the following step:<ol type="a"> mkdir <li>Verify that you are in the directory: <code>/var/medialib/sda5 libvirt/tmpimages/sda5-files</code>.</li> umount <li>Execute the following command: <code>virsh dumpxml fedora3 >fedora3.xml</devcode></sda5li> mount <li>Examine the file <code>fedora3.xml</devcode>. What does it contain? What format is it in?</sda5 li> <li>Make a copy of <code>fedora3.xml</mediacode> called <code>fedora3a.xml</code>.</sda5li> cp -v -R <li>Edit the file <code>fedora3a.xml</mediacode>, making the following changes:</sda5li></ol>::* Change the name (in the file, not the file name) to <code>fedora3a</tmp/sda5code>::* Change at least one of the hexadecimal characters in the UUID. Do not change the length of the UUID. Valid hexadecimal characters are 0-9 and a-filesf.<ol type="a" > umount <li value="6">Issue this command: <code>virsh define fedora3a.xml</dev/sda5code> mkfs <li>Issue the command <code>virsh list -t ext3 -all</devcode> and record any changes. <li>Issue the command: <code>virsh undefine fedora3a</sda5code> mount <li>List all of the virtual machines again, and note any changes. </devli></sda5 /media/sda5ol> cp -v -R <li>For the remainder of these labs, it is assumed that you will backup <u>'''both'''</tmpu> the images and xml configuration files for <u>'''all'''</sda5-u> Virtual machines, when asked to backup your virtual machines. It is also highly recommended to backup these filesto an external storage device (eg. USB key) in case the host machine gets "wiped" and you need to rebuild your HOST machine and then restore your Virtual Machines...</* li><li>Answer this question in your log book:</media/sda5li> rm -rf </tmp/sda5-filesol> mount -::* In order to fully back up a}}virtual machine, what information should be saved in addition to the virtual machine image?

By default, the Grub boot loader allows anyone with access {{Admon/important|Backing up VMs|It is essential to the computer back up your VMs at boot time to set the runlevel, or change the boot parametersend of each lab, which so you can allow easily restore them to influence the init process and which kernel image is loaded. Anyone with access to the boot prompt can therefore bypass security controls and control which software is loaded. For example, rebooting to runlevel 1, known as single user mode, gives the user root priveleges without the need for a password! Obviously, giving a non-administrator this much control can be dangerous, and it is wise to protect if something goes wrong in the boot loader with a secure passwordnext lab. }}

We {{Admon/tip|Shutting Down the Host while Virtual Machines are Running|If you shut down your host system while virtual machines are running, they will need to choose a password, encrypt with the grub programs hash utility (called md5crypt)be suspended, and add will resume the encrypted hash of next time you boot your password to the grub configuration file, /etc/grubhost system.conf}}

{{Admon'''Answer the Investigation 6 observations /important|Do not lose the GRUB password|If you lose the GRUB password you will not be able to change boot parameters when you boot the system. If you need to write it down, put it questions in a safe place, where no one will be able to tell what it is foryour lab log book.}}'''

# Choose a suitable password. # Open the grub program by typing the command: <code>grub</code># At the grub prompt, type in the command: <code>md5crypt</code># When prompted for a password, carefully type in your password. The program will display the encrypted hash of your password. Carefully write down that encrypted hash generated by the program.# Type the command: <code>quit</code> to exit the grub program.# Open the grub configuration file, <code>/etc/grub.conf</code> for editing. (This file is actually linked to /boot/grub/grub.conf).# Carefully add the line: <code>password --md5 ''password-hash''</code> (note== Investigation 7: ''password-hash'' is the hash you generated with md5crypt) Place this line between the splashimage line and the title line. If there are other lines there, there is no need to remove them. Just insert your password line as a new line.# Make sure you have not made a mistake. What you type in must match exactly the output from the md5crypt command.# While you are editing the file you should also increase the timeout for grub to automatically boot the default OS. Edit the line <code>timeoutKickstart Files =0</code> to <code>timeout=5</code> to give us more time to interrupt the process.# You should also ensure that the grub boot menu is not hidden. Add a hash sign (<code>#</code>) to the start of the line which reads: <code>hiddenmenu</code># Save the file and exit. Your Grub boot loader is now password protected.# Find the section of [http://fedorasolved.org/post-install-solutions/runlevel this article] that explains how to change the runlevel at boot time, and read it. Reboot your system, trying to change to runlevel 1 from the boot prompt, and see if the password protection worked.# From now on, when you want to change boot parameters when you boot, you must type lowercase <code>p</code> at the boot prompt and enter the required password.

== Completing {{Admon/tip|SSHD and Firewall|If you have restarted your virtual machine ''fedora1'', the Lab ==sshd server you started in investigation 1 (step 15) will no longer be running. In addition, the firewall will have reverted to its original state. In order to use '''scp''', below, you will need to restart ssh and adjust the firewall again.<br /><br />If students cannot backup their kickstart files using the '''scp''' command, they can use a web-browser to access their Seneca e-mail with attachment (copy kickstart file to their home directory first!). For the text-based Linux system "fedora3", students can use the '''mail''' command (refer to the man command to learn how to send e-mail attachments). }}

Check off When you perform a non-Kickstart installation, the following items before asking your instructor to check your lab:installation program creates a Kickstart file in the <code>/root</code> directory for reference.

* Task 1 - Install GNU/Linux Workstation using Fedora # Obtain the kickstart files for all four of your installations (your disk pack ''f17host'', plus the ''fedora1'', ''fedora2'', and ''fedora3'' virtual machines).* Task 2 - Collect system information after installation# To prevent confusion, copy your kickstart files to kickstart filenames that describe their purpose (eg. kickstart_host, kickstart_fedora1, kickstart_fedora2, etc...)* Task 3 # Copy them all to your f17host system (tip: use <code>scp</code>), or use the hint in the tip box above to send via e- Customize and configure boot time environmentmail.* Task 4 - Collect network information# Compare these files. What are the differences? Similarities? (Tip: you may want to use tools such as <code>sdiff</code> to help with the comparison).* Task 5 - Password protect Grub Bootloader# How could you use the kickstart file produced by the installation program to perform additional, identical installations?

Arrange evidence for each of these items on your screen, then ask '''Answer the Investigation 7 observations / questions in your instructor to review them and sign off on the lablog book.'''s completion:

* Grub is password protected.* Can login with your "learn" account name* Has all = Completing the mount points* Has the package count* Has edited the default runlevel* Has the correct IP address and MAC address* Find out the default route (gateway)* IP of the DNS name server* '''Name and contact information on your disk pack'''Lab =

{{Admon/tip|Runlevel|Feel free to change '''Arrange evidence for each of these items on your screen, then ask your default runlevel to 3 or 5 according instructor to your own personal preference. Note that later labs may assume a particular runlevel.}}review them and sign off on the lab's completion:'''

# How many packages were installed?# How many files (correct to the nearest hundred) were installed?# How many mount points were used?# How many users were created automatically on your system (do not count your learn account)?# What is your learn account's UID and GID?# What is your learn account's home directory?# What is the home directory = Preparing for the user "root"?# How do you determine the host name of your GNU/Linux workstation?# What command can display the NIC's MAC address?# Which file contains the default "runlevel" value for your GNU/Linux workstation?Quizzes =

{{Admon/important|Unbind # What is the name of the Fedora installation program?# Which factors recorded in your MAC address|Before moving your disk pack table (above) were due to the type of installation performed, and which factors were due to another systemthe amount of software installed?# Which type of installation works best for confirming compatibility with hardware before installation? Why?# Which type of installation works best for installing large numbers of computers? Why?# What factors affect installation time?# How can you reduce the number of software updates required immediately after installation?# Why would you enable additional repositories during installation?# What does the file <code>/root/anaconda-ks.cfg</code> contain, [[Unbinding MAC Addresses on Fedora|unbind and how is it created?# How do you start and stop virtual machines?# How do you SSH into your MAC address]]virtual machines?# What is the purpose of and relationship between these pieces of software?#* libvirt#* libvirtd#* virsh#* virt-manager#* virt-install#* kvm# The kickstart installation (fedora3) was a network installation. Can a kickstart file be used with a DVD installation?# The kickstart installation (fedora3) was fairly fast.}}Why? Under what circumstances would it take a long time, even on a fast network?# What other types of installation sources are possible (besides Live Disc, Installation Disc, and Network?)