13,420
edits
Changes
no edit summary
[[Category:OPS235]][[Category:OPS235 Labs]]
= Fedora 19 17 Installation Methods (on Virtual Machines: fedora1, fedora2, fedora3) =
== Introduction ==
:* '''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).
You should already have both a '''Fedora installation DVD''' and a '''Fedora LIVE DVDCD'''.
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:
|
! Install. Source
|-
! CD or DVD
! ✓
! ✓
! ✓
! ✓
|-6
! PXE Network Boot
! ✓
== Required Materials (Bring to All Labs) ==
* Fedora 19 17 LIVE CD* Fedora 17 x86_64 Installation DVD
* SATA Hard Disk (in removable disk tray)
* USB Memory Stick
* Lab Logbook
==Prerequisites==
:* '''virsh''' (Refer to Fedora Virtualization Guide link in the "Resources on the Web" section)
:* [http://linuxmanpages.com/man1/gzip.1.php gzip / gunzip]
== Resources on the Web ==
|- valign="top"
|
[http://docs.fedoraproject.org/virtualization-guide/f13/en-US/Fedora/19/html/Virtualization_Getting_Started_Guide/index.html Fedora Virtualization Getting Started Guide]
|
* [http://docs.fedoraproject.org/en-US/Fedora/1917/html/Fedora_Live_Images/ Fedora 17 Live Image Guide]* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Quick_Start_Guide/ Fedora 19 17 Installation Quick Start Guide]
|
[http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/ Fedora 19 17 Installation Guide]* [http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/ch-Preparing-x86.html#s1-steps-network-installs-x86/ Preparing for a Network Installation]* [http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/ch-Preparing-x86.html#s1-steps-network-installs-x86 Performing a Network Installation]
|
[http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/ Fedora 19 17 Installation Guide]* [http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/sn-automating-installation.html Automating the Installation with Kickstart]* [http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/ch-kickstart2.html Kickstart Installations]* [http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/ch-redhat-config-kickstart.html Kickstart Configurator]
|}
# '''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 />
# Open a shell terminal, and login to the root account. {{Admon/tip|Remember to use '''su -''' prior to running administration commands|A common mistakes students make in OPS235 is to forget to log into the root account prior to running administration commands. Therefore, if a command doesn't work, ask yourself, "is this is an administration command?"}} <ol> <li value="3">Install the Fedora virtualization software by issuing the Linux command: <code>'''yum groupinstall "Virtualization"'''</code> ( You can alternatively use the Linux command: or <code>pkcon install @virtualization</code> )</li></ol> {{Admon/tip|More About KVM| The KVM virtualization software installed is in three parts:<ol><li>:* '''A system service named ''libvirtd''''' that manages the VMs.</li><li>:* '''Tools to manage virtualization''', including the <code>virt-manager</code> graphical tool and the <code>virsh</code> command-line tool.</li><li>:* The actual '''virtual machines''' themselves.</li></ol>}} <ol> <li value="4">Start the virtualization service using the systemctl command: <code>'''systemctl start libvirtd.service'''</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>'''systemctl restart iptables.service'''</code></li></ol> {{Admon/tip|Maybe reboot your fedora host now|Sometimes virt-manager does not work properly unless you reboot after installing the virtualization software.}}
<ol>
<li value="63">After rebooting your computer system, and logging back into your account, Start the virtualization service: <code>service libvirtd start </code></li> <li>The firewall configuration is altered by the graphical tool by clicking addition of the '''Activities''' menu, in virtualization software. Restart the search box, type firewall so that these changes become active: <code>'''virt-manager'''service iptables restart</code> and then click the virtual manager icon.</li>
</ol>
{{Admon/importantcaution|Running virt-manager from command line (shell)Reboot your fedora host now| You can also run the virtual manager program from command line by typing "'''virt-manager'''". It is highly recommended to run the virtual machine manager from a regular user account and not the root account. Running virt-manager as root may not work due to configuration issuesproperly unless you reboot after installing the virtualization software.}}
<ol>
<li value="75">You will be prompted to enter After rebooting your password: enter computer system, and logging back into your user (not root) password and click account, start the graphical tool by selecting the "menu options '''Activities'''>'''Applications'''>'''AuthenticateSystem Tools'''" button.</li> '''Virtual Machine Manager''' or by typing the command <licode>Record the setup commands in your lab logvirt-book.manager</li> <licode>Proceed to Investigation 1.</li>
</ol>
{{Admon/important|Note Comparison Chart In Investigation #4Run virt-manager as a regular user| In the next 3 investigations, you will install Fedora19 Running virt-manager as separate virtual machines using different install techniquesroot may not work due to configuration issues. '''It is highly recommended to print-out the comparison chart for each of these techniques prior to performing Investigations 1 - 3, and fill out the chart as you perform these investigations!'''}}
== Investigation 1: Installing from the Fedora19 Desktop a Live Disc (950MB) ==
{{Admon/tip|Using an Image instead of a Live Disc|It is recommended that you perform this installation from your Fedora Desktop LIVE DVD (950MB)CD. As a matter of interest (for future reference), it is possible to install directly from the ISO file you used to burn your Live DVDCD. There are many Internet tutorials that show the individual how to perform that task.}}
==== Introduction ====
In this investigation, you will install Fedora from your live disc, and observe the differences between this type of installation and the DVD installation previously performed.
==== VM Details ====
* '''Name:''' fedora1
* '''Boot media:''' Fedora 19 Desktop Live DVDCD* '''Installation source:''' Fedora 19 Desktop Live DVDCD* '''Memory:''' 1024MB768MB* '''Disk space:''' 15GB10GB
* '''CPUs:''' 1
|[[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 ]]
# In the Virtual Machine Manger, click on the 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 virtual machine (called '''fedora1''') name and select '''Local install media (ISO image or CDROM)''' (refer to ''Step 1 of 5'' thumbnail above).# Click the '''Forward''' Button.# '''Step 2 of 5:''' '''Insert the CDROM or DVD containing the Fedora Live Disc image. Wait a moment for the disc to be recognized''', You should see a black dialog box appear that recognizes the DVD. Click on the black box to confirm.# Make certain that you then select "'''Use CDROM or DVD'''".# Under "Location your as the install media section", select "'''Use CDROM or DVD'''". Set the ''OS type'' to '''Linux''' and the ''Version'' to '''Fedora 1917''' (refer to ''Step 2 of 5'' thumbnail above), then click the '''Forward''' Button.
<!-- {{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 '''1024 768 MB''' and the number of CPUs to '''1''' (refer to ''Step 3 of 5'' thumbnail above), Then click the '''Forward''' button.# '''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 '''15 10 GB''' and check-mark checkmark the box labelled labeled '''Allocate entire disk now''' (refer to ''Step 4 of 5'' thumbnail above), then click the '''Forward''' button.
# '''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).
{{Admon/note|Fedora LIVE DVD CD Install Screen Shots Thumbnails|While performing the Fedora 19 17 LIVE DVD CD install, click on the thumbnails below to provide a '''"visual reference"''' while performing this particular Fedora installation.
}}
{|cellpadding="8" width="100%"
|[[Image:fedoralive1.png|thumb|100px| The Virtual Machine will now start in '''Live''' mode. '''Install to Hard Disk''']]|[[Image:Installscreenfailedtoload.png|thumb|140px| '''Installation Summary''' Ignore and close the "Failed To Load" dialog box. Used to select '''Date and Time''' as well as '''Installation Destination'''. Search for the panel on the upper-left-hand side of the screen.]]|[[Image:Installationdestination1fedoralive2.png|thumb|140px|'''Installation Destination''' dialog box (confirm Login to the VM and select '''done''').]]|[[Imagedouble-click:Installationdestination2.png|thumb|140px|<br /> '''Installation OptionsApplications''' dialog box within <br />>'''Installation DestinationSystem Tools''' process (make suggested settings and select <br />>'''doneInstall to Hard Disk''').]]|[[Image:Installationdestination3selectstorage1.png|thumb|140px100px|Select '''Manual Partitioning''' dialog box within '''Installation Destination''' process (click link to ''Specialized Storage Devices'automatically create partitions''' and proceed to next dialog box).]]|[[Image:Installationdestination4selectstorage2.png|thumb|140px100px|Confirm partitions to be automatically created and then click Select '''doneVirtio Block Device'''.]]|[[Image:Installationdestination5finishcdinstall.png|thumb|140px100px|Confirm summary of changes, click 'You will get the ''Accept ChangesFirstboot''', then click '''Begin Installation''' at configuration questions during the ''Installation Summary'' dialog box to proceed with your installationboot process.]]
|}
<ol>
<li value="118">When you have completed your installation, click the '''QuitThe virtual machine will now start''' button. You should return to the Fedora Live desktop. </li> <li>Shutdown the Fedora Live session by clicking on Select the default menu item labelled: '''Live UserStart Fedora 17''' button (. The virtual machine is running from the live disc at this point, and no software has been installed on the top right-hand corner) and select ''hard drive'Power Off''', and confirm that you want to power-offof the virtual machine. It is a good idea to be patient! Sometimes it may take a few minutes for shut-down!</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="1310">The Installation Summary dialog box will appear (similar to what you encountered in lab1 for your full DVD install). It is assumed that you will be familiar with the general steps on During the installation process. <li>Set the Time Zone , when prompted for "a storage device, first select '''TorontoSpecialized Storage Devices'''".</li> <li>When back at the main installation summary menu, and then select '''Installation Destination'''.</li> <li>In the Installation Options dialog box Confirm approx. '''15 GB''' for the '''Virtio Block Device''' and click the '''Done''' button in the top left-hand corneroption. '''Note: It may take a few minutes to access the <u>next</u> Installation Options dialog box, so please be patient!'''</li> <li>Click "When prompted for the hostname, enter '''I want to review/modify my disk partitions before continuingfedora1'''", confirm that and when prompted for the partition scheme is set to timezone, select '''LVMToronto - Eastern Time Ontario''', and click the '''Continue''' button.</li> <li>In the Manual Partitioning dialog boxwhen asked about storage, click on the link "select '''Click here to create them automaticallyUse All Space'''"</li> <li>Review the automatically created partitions in the next dialog box. Record in your lab log-book the partition names and related sizes, and note the virtual hard disk device name (i.e. vda1). </li>Click the '''Done''' button at Use the top left-hand cornerdefault values for all other fields.</li> <li>Confirm the Summary of Changes, and then click the "'''Accept Changes'''" button located on Notice that the bottom right-hand side. Note: please installer does not ask you what software should be patient, and wait a few minutes until you can access installed; compare the Installation Summary dialog box. Click '''Begin Installation'''. Note installation time to the amount of time that it takes took to complete this do your Lab 2 installation.</li> <li>During the installation process, set a root password and create a least one regular user account.</li> </ol> {{Admon/tip|Screen Lock|If during the install process, the screen locks, drag the mouse upwards, and simply press enter to unlock Record this information in the screen (no password is required for a '''live usertable contained in Investigation 4''').|}} <ol/li> <li value="22">After When the installation process has completedis complete, click on the '''Quitreboot''' button. This should return you to the LIVE version of Linux that was running to help install to the Hard Drive. Click on the live username located at the top bottom right-hand corner and power-off of the machinescreen.</li>
</ol>
<ol>
<li value="2313">Make certain that you remove your Fedora19 Live DVD Start the VM from your DVD driveits disk image. From your ''Virtual Machine Manager'' windowThis can be done graphically by selecting the Virual machine name, start your and then clicking on the '''fedora1Open''' virtual machine (remember to press button, and then click the '''Playplay''' button to start when the next screen appears (or by selecting Virtual Machine>Run from the VMvirtual machine menu).</li><li>Log into your You will get the ''Firstboot'fedora1''' VM as a regular user (you created configuration questions during the installation boot process).</li><li>Upon first log-in, set your Gnome preferences (asking you are NOT required to create a user, set-up a cloud account for this coursethe date and time, and optionally send the hardware profile to the Fedora Project).</li><li>Open Create a terminal (shell), and log into '''root'''.</li> <li>Change your '''host user with the same name''' to '''fedora1''' (refer to as your [[OPS235 Lab 1]] notes)Matrix account.</li> <li>Compare Login using the installation time to the amount of time it took to do this type of installation. Record this information in the '''table contained in Investigation 4'''new user account.</li>
</ol>
<ol>
<li value="2815">Enable SSH access to your virtual machine with these commands (semi-colon allows commands to be run in sequence):<br /> <code>'''systemctl service sshd start sshd; systemctl enable chkconfig sshd.service'''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 <u>virtual machine</u> from your the host (f19hostyour main Fedora installation): <code>'''ssh ''fedora1_IP_address'''IPaddress''</code> (determined from step 27 above)</li>
</ol>
* '''Name:''' fedora2
* '''Boot media:''' Network installation
* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/1917/Fedora/x86_64/os/
* '''Memory:''' 1024MB
* '''Disk space:''' 20GB
# 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/1917/Fedora/x86_64/os/ . Select the system to automatically detect OS type and version. Did it work? If it didn't work, you can move backwards to a previous screen and then manually select the appropriate OS type and Linux version.#* In '''step 3 2 of 5''', select set the appropriate RAM.#* In ''OS Type'step 4 of 5''', set the hard-drive space to '''20GBLinux''' (<u>NOT</u> 15 GB!)#* In and ''Version'step 5 of 5'to '', review the settings, and click '''FinishFedora 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).
# Complete the '''Installation Summary''' sections (Date and Time, Installation Destinatation) like When you did in get to the fedora1 install, except in the '''disk partitioning''' step, select '''Use All Space''' and enable the checkbox labelled '''Review and modify partition layout'''. Allow the installation program to automatically create the partitionsIf an dialog box displays a permissions problem, but we will be making changes then click yes to the partition sizesproceed.# On the next screen, change the logical volumes as follows:#* Select Reduce the size of the logical volume (partition) '''root''' (i.e. '''/''' ), and reduce the size LV to '''10 GB''', then click '''Update Settings8000 MB'''.#* Click the '''plus sign''' (i.e. '''+''') to <u>add</u> Add a logical volume called '''with a size of 2000 MB and a mountpoint of /home''' with a size of (you can name it whatever you want, and use '''2 GBext4'''. Note that you can make changes to other items (such as the file -system type like ext4), but you are not required to do this for this lab.# Review your changesOn the software selection screen, click select '''Done''', click '''Accept Changes''' to return to the '''Installation SummaryGraphical Desktop'''.# Make certain that Software Selection is set to '''Gnome Desktop'''.# Complete On the installationsame screen, select the "Fedora 17 - x86_64" and set a the "Fedora 17 - x86_64 - Updates". Leave "Installation Repo" selected. ''root passwordDO NOT'' and at least 'enable the "Test Updates" repository'one regular user'' account.# Click '''Reboot''' to restart Complete the systeminstallation. Note: be patient for the reboot process! (Force a Virtual Machine shutdown only if absolutely necessary).# Record the time taken to install, and compare this to the time taken by the previous installations.# What was different with your fedora2 install (upon completion) that was different than your fedora1 install? What was similar?# Record this information in the '''table contained in Investigation 4'''. {{Admon/tip|Adding Repositories|Repositories are online resources that contain operating system programs, application programs, was well as updates (patches). Although you have the basic repositories for Fedora19, you can add other repositories as well for "cutting-edge" programs or special applications that may not be available via the regular repositories.|}} <ol><li value="13">Turn the screen lock feature of in your fedora2 VM by selecting '''Activities''', typing '''settings''', and clicking the system settings icon. Click the Privacy icon, and switch '''lock screen''' from '''ON''' to '''OFF'''. After changing the settings, close the system settings window.</li><li>To add the RPM FUSION repository issue the following command (you can copy and paste to a shell in your fedora2 VM):<br />su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm'</li><li>You will be required to enter your root password.</li> </ol><ol><li value="16">Proceed to Investigation 3.</li></ol>
'''Answer the Investigation 2 observations / questions in your lab log book.'''
* '''Name:''' fedora3
* '''Boot media:''' Network installation
* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/1917/Fedora/x86_64/os/* '''Kickstart location:''' http://matrixwww.senecacdrivehq.oncom/file/df.caaspx/shareID10606286/~murray.saulfileID1269952040/murrayFedora17-kickstart.cfg
* '''Memory:''' 1024MB
* '''Disk space:''' 15GB
==== Steps ====
# Create the VM as you did with the ''<u>'''fedora2'''</u>'' Virtual Machine.virtual machine, specifying a network install as before, except:# * In '''step 2 of 5''', use after entering the same URL for ''Installation Source''. Click to expand the installation source, click on the '''URL Options''' and enter control.#* Enter the '''Kickstart''' URL: http://matrixwww.senecacdrivehq.oncom/file/df.caaspx/~murray.saulshareID10606286/fileID1269952040/murrayFedora17-kickstart.cfg . Make certain to select the option for the kick-start file to determine the OS type and version and click '''Forward'''.# Specify the RAM amount (1024 MB) and Hard Disk space (15GB) and proceed to next screen.# Verify the installation settings, and then click '''Finish'''.# Observe the installation. Accept default questions, and ignore errors (such as user account error). How is it different from booting from an optical disc (CD/DVD)? What is the purpose of the '''kickstart''' file?
# 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? # '''If installation is finished, but nothing happens when you click the "reboot" button, then force a shutdown'''.# Take a look at the '''kickstart''' file by clicking on the link in a web-browser (using the URL you entered) and search for "'''password'''" (you may have to search for this pattern a couple of times). Determine <u>determine</u> the '''root password''' as well as the '''regular username 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.# You can shutdown your text-based fedora3 VM by issuing the following Linux command (as root): <code>'''shutdown'''</code> or <code>'''halt'''</code>. Try to wait a least 2 minutes to see if the VM complete shuts-down. Only force a shutdown if absolutely necessary.# Why do you think you have installed both graphical and text-based VMs for this course?# Record this information in the '''table contained in Investigation 4'''.
'''Answer the Investigation 3 observations / questions in your lab log book.'''
{|border="1" width="100%" cellpadding="5"
|-
! ||f19hostf17host||fedora1||fedora2||fedora3
|-
|'''Installation Method'''||Installation Disc||Live Disc||Network Installation||Network Installation + Kickstart
# Switch to your terminal and issue the command: <code>'''virsh start fedora1'''</code>
# Check to see if your fedora1 VM is now running.
# Switch to the terminal and issue the command: <code>'''virsh list --all'''</code> 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 request to "shutdown virtual machine gracefully", but may not always work. Why do you think it is useful to have commands to manipulate VMs?
{{Admon/note|Virtual Machine Does not Shutdown from Command|If the Virtual machine fails to shutdown from the <code>virsh shutdown</code> command, then you can go to the '''Virtual Machine manager''' and '''halt''' or '''shutdown''' within the VM itself, then you can click the '''PowerOff''' button in the VM window. You'll want to avoid a forced shutdown since those are equivalent to yanking the cord out of the wall on a physical machine!|}}
# Shut down all of the virtual machines.
# Change to the directory <code>'''/var/lib/libvirt/images/'''</code>. Note the size of the files in this directory. What do these files contain?
# 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="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>
::* 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>
When you perform a non-Kickstart installation, the installation program creates a Kickstart file in the <code>/root</code> directory for reference.
# Obtain the kickstart files for all four of your installations (your disk pack '''''f19host'''f17host'', 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 f19host f17host system (tip: use <code>'''scp'''</code>), or use the hint in the tip box above to '''send via e-mail'''.# 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).
# How could you use the kickstart file produced by the installation program to perform additional, identical installations?
