Changes

[[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|} |}

* '''Fedora 16 LIVE CD''' - You can burn this onto a CD-R in the Open Lab* '''Fedora 16 x_64 Installation DVD''' - You can burn this onto a DVD-R in the Open 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)* '''Lab Logbook (Lab1 Reference Sheet)''' == Required Materials (Bring to make notes and observationsAll Labs).==

* Fedora 17 LIVE CD* Fedora 17 x86_64 Installation DVD* SATA Hard Disk (in removable disk tray)* USB Memory Stick* Lab Logbook  ==PrerequisitePrerequisites==

:* '''virsh''' (Refer to Fedora Virtualization Guide belowlink in the "Resources on the Web" section)

== 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)|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.}}2=== Preparation ==

# '''Open a web-browser''', and open the '''OPS235 Lab #2 WIKI'''. '''<br /><br />NOTE:''' You need to enter your "MySeneca" username and password to obtain a "wired" Internet connection (otherwise, you will not be able to perform the "groupinstall" command in the next step). Remember to perform a "wired-connection" (logging in with your MySeneca username and password via a web-browser) every time you boot-up your host machine...<br /><br /># Install the Fedora virtualization software: <code>yum groupinstall "Virtualization"</code> or <code>pkcon install @virtualization</code> The virtualization software installed is in three parts::* '''A system service named ''libvirtd''''' that manages the VMs.:* '''Tools to manage virtualization''', including the <code>virt-manager</code> graphical tool and the <code>virsh</code> command-line tool.:* The actual '''virtual machines''' themselves.<ol> <li value==Instructions=="3">Start the virtualization service: <code>service libvirtd start</code></li> <li>The firewall configuration is altered by the addition of the virtualization software. Restart the firewall so that these changes become active: <code>service iptables restart</code></li>=== Preparation ===</ol>

{{Admon/tipcaution|Update Reboot your Fedora Installationfedora host now|It's a good idea to ensure that your Fedora installation is fully updated before proceedingvirt-manager may not work properly unless you reboot after installing the virtualization software. You can update your system with the graphical tool located on the menu at >System>Administration>Software Update (or type the command <code>gpk-update-view</code>), or by typing either of these commands: <code>pkcon update</code> or <code>yum update</code>}}

# Install the Fedora virtualization software: <codeol>yum groupinstall <li value="Virtualization5"</code> or <code>pkcon install @virtualization</code> The virtualization software installed is in three parts:## A After rebooting your computer system service named ''libvirtd'' that manages the VMs.## Tools to manage virtualization, including the <code>virt-manager</code> graphical tool and the <code>virsh</code> command-line tool.## The actual virtual machines themselves.# Start the virtualization service: <code>service libvirtd logging back into your account, start</code># The firewall configuration is altered by the addition of the virtualization software. Restart the firewall so that these changes become active: <code>service iptables restart</code># Start the graphical tool by selecting the menu option options '''Activities'''>'''Applications'''>'''System Tools'''>'''Virtual Machine Manager ''' or by typing the command <code>virt-manager</code></li></ol>

{{Admon/caution|Reboot your fedora host|There appears to be an issue with supplying your VM's with == Investigation 1: Installing from a dynamic IP unless the host is restarted after installing "Virtualization". '''Reboot now to avoid this problem.'''}}Live Disc ==

=== Investigation 1: Installing from a Live Disc === {{Admon/tip|Using an Image instead of a Live Disc|If It is recommended that you do not have perform this installation from your Fedora LIVE CD. As a Live Disc availablematter of interest (for future reference), you can download it is possible to install directly from the .iso image ISO file from http://belmont.senecac.on.ca/fedora/releases/13/Live/x86_64/Fedora-13-x86_64-you used to burn your LiveCD.iso and then use the iso image file in place of There are many Internet tutorials that show the physical diskindividual how to perform that task.}}

* '''Name: ''' fedora1* '''Boot media: ''' Fedora Live CD* '''Installation source: ''' Fedora Live CD* '''Memory: 512MB''' 768MB* '''Disk space: ''' 10GB* '''CPUs: ''' 1 ==== Screen-Shot Thumbnail Reference ==== {{Admon/note|Virtual Machine Screen Shots Thumbnails|While performing the Virtual Machine setup, click on the thumbnails below to provide a '''"visual reference"''' while performing this section.}} {|cellpadding="8" width="100%" |[[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 2 of 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:''' Create a New Virtual Machine ]]|}

{{Admon/note|Fedora 12 Screen Shots|The following screen shots are from Fedora 12. The Fedora 13 version of virt-manager varies slightly -- there are a few extra controls on some dialogs which may be ignored.}} # In the Virtual Machine Manger, click on the icon to ''Create a Virtual Machine'' in the upper-left corner: <br />[[Image:Virt-manager1(refer to '''Virtual Machine Manager''' thumbnail above).png]]

# '''Step 1 of 5: ''' Enter the virtual machine (called '''fedora1''') name and select '''Local install media''' (refer to ''Step 1 of 5'' thumbnail above).<br />[[Image:Virt-manager2.png]]# '''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 it '''Use CDROM or DVD''' as the install media. Set the ''OS type'' to '''Linux ''' and the ''Version'' to '''Fedora 13.<br />[[Image:Virt-manager317''' (refer to ''Step 2 of 5'' thumbnail above).png]]

# '''Step 3 of 5: ''' Set the memory to 512 '''768 MB ''' and the number of CPUs to '''1''' (refer to ''Step 3 of 5'' thumbnail above).<br />[[Image:Virt-manager4.png]]# '''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).<br />[[Image:Virt-manager5.png]]# '''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''.<br />[[Image:Virt-manager6.png]]# The virtual machine will now start. You will see a window which displays the virtual video card from the VM. It's important (refer to note that the VM can (and often will) run even when this display is not present. The virtual machine is running from the live disc at this point, and no software has been installed on the ''hard driveStep 5 of 5'' of the virtual machinethumbnail above).# Login to the VM {{Admon/important|Removing and double-click on Recreating VMs|If for some reason the ''Install user wants to Hard Drive'' icon. The installation programremove a Virtual Machine, similar to the one used when installing Fedora in Lab 2, will appear. You will get a warning at one point during the installation process that the disk "may need to be rethey can right-initialized" -- this is simply a warning that click the virtual disk is completely blankVM, and it select delete in the Virtual Machine Manager. It is safe recommended to select ''Re-initialize drive''.# During "delete the installation process, when prompted for the drive, select image file"Virtio Block Device", when prompted for in the hostname, enter "fedora1", remove VM dialog box when prompted for the timezone, select ''America/Toronto'', removing and when asked about storage, select then recreating a VM''Use All Space''. '''Use the default values for all other fields.''' Notice that the installer does not ask Note: If you what software should be installed; compare the installation time fail to properly remove the amount of time VM image file, it took to do your Lab 2 installation.# When may affect the installation is complete, select the menu option System>Shutdown to stop the Live Disc.# Start hard disk size for the new VM from its disk image 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)i. Create a user with the same name as your Matrix accounte.# Login using use the new user accountold smaller size.# Enable SSH access to your virtual machine with these commands: <code>service sshd start; chkconfig sshd on</code># Find out the IP address of your virtual machine: <code>ifconfig eth0</code># Enter the following command on your virtual machine to create a firewall exception Make certain to allow ssh traffic into the machine: <code>iptables -I INPUT -p tcp -s0/0 -d0/0 --dport 22 -j ACCEPT</code># Confirm remove that you can ssh VM image file prior to your virtual machine from recreating the host (your main Fedora installation): <code>ssh VM.|''IPaddress''</code>}}

{{Admon/tipnote|Authenticate Fedora LIVE CD Install Screen Shots Thumbnails|While performing the Fedora 17 LIVE CD install, click on the thumbnails below to the network|The rest of provide a '''"visual reference"''' while performing this lab uses network access. Be sure to authenticate to the network using your browser before proceedingparticular Fedora installation.}}

{|cellpadding="8" width="100%" |[[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 screen.]]|[[Image:fedoralive2.png|thumb|140px|Login to the VM and double-click:<br /> '''Applications'''<br />>'''System 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="8">'''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> <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 installation process that the disk "May contain data" or "may need to be re-initialized" -- this is simply a warning that the virtual disk is completely blank, and it is safe to proceed with the installation.</li></ol> {{Admon/note|Virtual 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="10">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 ====

* '''Name: ''' fedora2* '''Boot media: ''' Network installation* '''Installation source: ''' http://belmont.senecac.on.ca/fedora/releases/1317/Fedora/x86_64/os/* '''Memory: 512MB''' 1024MB* '''Disk space: 15GB''' 20GB* '''CPUs: ''' 1

# 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/1317/Fedora/x86_64/os/#* In '''step 2 of 5''', set the ''OS Type'' to "'''Linux" ''' and ''Version'' to "'''Fedora 13" 17'''.

# 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 ext3 or '''ext4 ''' as the filesystem file-system type).# On the software selection screen, select '''Graphical Desktop'''.# '''On the same screen, select the "Fedora 13 17 - x86_64" and the "Fedora 13 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 ====

* '''Name: ''' fedora3* '''Boot media: ''' Network installation* '''Installation source: ''' http://belmont.senecac.on.ca/fedora/releases/1317/Fedora/x86_64/os/* '''Kickstart location: ''' http://zenitwww.senecacdrivehq.oncom/file/df.caaspx/shareID10606286/~chris.tylerfileID1269952040/fedora13-vdaFedora17-kskickstart.cfg* '''Memory: 512MB''' 1024MB* '''Disk space: 10GB''' 15GB* '''CPUs: ''' 1

#* In step 2 of 5, after entering the URL for the installation source, click on the '''URL Options''' control.#* Enter the Kickstart URL: http://zenitwww.senecacdrivehq.oncom/file/df.caaspx/~chris.tylershareID10606286/fileID1269952040/fedora13-vdaFedora17-kskickstart.cfg

# '''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 ===

Complete the following table(and transfer into your lab2 log-book notes):

{|border="1" width="100%" cellpadding="5"

! ||f13hostf17host||fedora1||fedora2||fedora3

=== Investigation 5: Managing Virtual Machines from the Command Line ===

# Switch to the f19host machine, and open a shell terminal.# Enter these commands into your f19host machine and note the result:#* <code>'''virsh list'''</code>#* <code>'''virsh list --all'''</code>#* <code>'''virsh list --inactive'''</code># Start Now, shut-down your fedora1 VM normally, and close the fedora1 VM window. Make certain NOT to close the ''fedora3'' virtual machine from Virtual Machine Manager main window.# Switch to your terminal and issue the command line: <code>'''virsh start fedora3fedora1'''</code># Repeat the commands from step 2 and notice any changesCheck to see if your fedora1 VM is now running.# Stop Switch to the terminal and issue<code>''fedora3'' virtual machine: <code>virsh shutdown fedora3</code># Confirm that 'list --all'fedora3'' has been shut down.# Execute this command: </code>virsh dumpxml fedora3 >fedora3and confirm the status of the fedora1 VM.xml</code># Examine the file <code>fedora3There are other commands that can be used (such as suspend, or shutdown).xml</code>The "shutdown" command may not always work since it sends a request to "shutdown virtual machine gracefully", but may not always work. What does Why do you think it contain? What format is it inuseful to have commands to manipulate VMs?# Edit the file fedora3.xml, making the following changes:#* Change {{Admon/note|Virtual Machine Does not Shutdown from Command|If the name Virtual machine fails to shutdown from the <code>fedora3avirsh shutdown</code>#* Change at least one of command, then you can go to the '''Virtual Machine manager''' and '''halt''' or '''shutdown''' within the VM itself, then you can click the hexadecimal characters '''PowerOff''' button in the UUIDVM window. Do not change You'll want to avoid a forced shutdown since those are equivalent to yanking the length cord out of the UUID. Valid hexadecimal characters are 0-9 and wall on a-f.physical machine!|}} # Issue this command: <code>virsh define fedora3a.xml</code># Issue '''Answer the command <code>virsh list --all<Investigation 5 observations /code> and record any changesquestions in your lab log book.''' # Issue the command== Investigation 6: <code>virsh undefine fedora3a</code># List all of the How do I backup a virtual machines again, and note any changes.machine? ==

=== Investigation 6{{Admon/important|Backing up VMs|There are two general processes in order to back up your images: How do I <ol><li>'''Compressing your images''' (also recommended to backup a 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 '''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!|}}

# Make a compressed backup of the <code>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 redirection signs "<" and ">" properly in the command!'''){{Admon/caution|Make sure the backup is successful!|If there are any error messages, '''DO NOT''' proceed past this point. You're going to destroy your fedora3 virtual machine and restore it using the backup you have created -- if there are any problems with the backup, you will not have a working virtual machine, and will have to re-install it.}}# <ol> <li value="4">Compare the size of the compressed and original files.</li># <li>Start the '''''fedora3''''' VM.</li># <li>'''Make certain that you are in your fedora VM, and <u>not</u> in your Fedora main system.!'''</li># <li>Wreck <u>only</u> your fedora 3 system! Try this command inside the fedora3 virtual machine ('''DO NOT''' do this on your main Fedora system, or you will have to repeat your '''lab2''' and portions of your '''lab3'''!): <code>'''rm -rf /*'''</code></li># <li>Shut down the VM.If you tried to start the Fedora3 VM, it would not boot since all system files have been removed!</li># <li>Restore the original image from the backup (type in your home directory by typing this command carefully): <code>'''gunzip <~YourUserId/fedora3.img.backup.gz >fedora3.img'''</code></li># <li>Restart the VM. Is it working normally?</li># <li>Create compressed backups of your other virtual machines.</li></ol><ol><li value="12">You should make a copy of the 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 be added to your list.Please perform the following step:<ol type="a"><li>Verify that you are in the directory: <code>/var/lib/libvirt/images/</code>.</li> <li>Execute the following command: <code>virsh dumpxml fedora3 >fedora3.xml</code></li> <li>Examine the file <code>fedora3.xml</code>. What does it contain? What format is it in?</li> <li>Make a copy of <code>fedora3.xml</code> called <code>fedora3a.xml</code>.</li> <li>Edit the file <code>fedora3a.xml</code>, making the following changes:</li></ol>::* Change the name (in the file, not the file name) to <code>fedora3a</code>::* 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-f.<ol type="a" > <li value="6">Issue this command: <code>virsh define fedora3a.xml</code> <li>Issue the command <code>virsh list --all</code> and record any changes. <li>Issue the command: <code>virsh undefine fedora3a</code> <li>List all of the virtual machines again, and note any changes. </li></ol># <li>For the remainder of these labs, it is assumed that you will backup <u>'''both'''</u> the images and xml configuration files for <u>'''all'''</u> Virtual machines, when asked to backup your virtual machines. It is also highly recommended to backup these files to 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:</li></ol>#::* In order to fully back up a virtual machine, what information should be saved in addition to the virtual machine image?# Write the answer to the Investigation 6 question in your lab book.

{{Admon/important|Backing up VMs|It's a good idea is essential to back up your VMs at the end of each lab, so you can easily restore them if something goes wrong in the next lab.}}

=== '''Answer the Investigation 7: Kickstart Files ===6 observations / questions in your lab log book.'''

== Investigation 7: Kickstart Files == {{Admon/tip|SSHD and Firewall|If you have restarted your virtual machine ''fedora1'', the sshd server you started in section investigation 1-16 (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).}}

# Obtain the kickstart files for all four of your installations (your disk pack ''f13hostf17host'', plus the ''fedora1'', ''fedora2'', and ''fedora3'' virtual machines). # To prevent confusion, copy your kickstart files to kickstart filenames that describe their purpose (eg. kickstart_host, kickstart_fedora1, kickstart_fedora2, etc...)# Copy them all to your f13host f17host system (tip: use <code>scp</code>), or use the hint in the tip box above to send via e-mail.

='''Answer the Investigation 7 observations / questions in your lab log book.''' = Completing the Lab ==

{{Admon/important | Important! | '''Arrange evidence of for each of the following these items on the your screen, and then ask your professor or lab monitor instructor to check review themand sign off on the lab's completion:}}'''

== Preparing for the Quizzes ==