== Investigation 1: Installing from a Live Disc Network Install with Kickstart ==

* '''Boot media:''' Fedora Live CD* '''Media and Installation source:''' Network server: http://belmont.senecac.on.ca/fedora/releases/16/Fedora/x86_64/os/* '''Kickstart file:''' http://zenit.senecac.on.ca/~chris.tyler/fedora16-vda-ks-200.cfg

# Run this command to start the installation of a virtual machine named fedora1: virt-install --connect qemu:///system --name fedora1 -r 768 --os-variant fedora16 --network network=default --disk /var/lib/libvirt/images/f16-ks-1,size=10 -l httphtp://belmont.senecac.on.ca/fedora/releases/16/Fedora/x86_64/os/ -x ks=httphtp://zenit.senecac.on.ca/~chris.tyler/fedora16-vda-ks-200.cfg --noautoconsole

# Record the approximate time that the installation ends. Subtract the start time to find out how long the installation took.

# To gather the information listed above, study the [http://zenit.senecac.on.ca/~chris.tyler/fedora16-vda-ks-200.cfg kickstart file]. Record your answers.

=== Investigation 2 ===

=== Investigation 3 ===

# Make a copy of the [http://zenit.senecac.on.ca/~chris.tyler/fedora16-vda-ks-200.cfg kickstart file]. Modify it so that the user account that is created has the same user ID as your matrix account. Change the IP address in the kickstart file to 192.168.122.202. Place this the modified kickstart file in a location where it can be accessed via a web browser (for example, in the public_html directory in your Matrix account).

## Use Change the name of the disk file to match the name of the IP address 192virtual machine.168.122## Use a disk size of 12G.202

== Investigation 24: Installing Managing Virtual Machines from the Network Command Line ==

{{Admon/tip|Authenticate Note: The commands used to manage virtual machines must be executed on the network|The rest of this lab uses network accesshost (your disk pack) and not inside virtual machine.''' Be sure to authenticate Use the host name information in the command prompt to confirm that you are on the network using your browser before proceeding'''correct machine when entering commands.}}

=== 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/16/Fedora/x86_64/os/* '''Memory:''' 768MB* '''Disk space:''' 15GB* '''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/16/Fedora/x86_64/os/#* In '''step 2 of 5''', set the ''OS Type'' to '''Linux''' and ''Version'' to '''Fedora 16'''. # 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, 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 16 - x86_64" and the "Fedora 16 - 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/16/Fedora/x86_64/os/* '''Kickstart location:''' http://zenit.senecac.on.ca/~chris.tyler/fedora16-vda-ks.cfg* '''Memory:''' 768MB* '''Disk space:''' 10GB* '''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://zenit.senecac.on.ca/~chris.tyler/fedora16-vda-ks.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"|-! ||f16host||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'''|| || || |||-|'''Disk layout could be selected during installation'''|| || || |||-|'''No questions asked during installation'''|| || || |||-|'''Total installation time''' (after installation questions)|| || || |||-|'''Amount of disk space used'''|| || || |||-|'''Questions asked during first boot'''|| || || |||-|'''Advantages of this type of installation'''|| || || |||-|'''Disadvantages of this type of installation'''|| || || |||-|'''This type of installation is recommended for...'''|| || || |||} == Investigation 5: Managing Virtual Machines from the Command Line == {{Admon/note|Manage virtual machines from the host|The commands used to manage virtual machines must be executed on the host (your disk pack) and not inside a virtual machine.}} # Start the ''fedora1'' virtual machine, and stop the ''fedora2'' and ''fedora3'' virtual machines.

# Stop the ''fedora3'' virtual machine: <code>virsh shutdown fedora3</code>  {{Admon/note|Virtual Machine Does not Shutdown from Command|Note: If the Virtual machine fails to shutdown from the <code>virsh shutdown</code> command, then you can go to or from the '''Virtual Machine manager''' and '''<code>halt''' </code> or <code>poweroff</code> or '''<code>shutdown''' </code> commands within the VM itself, then you can click the use dthe <code>virsh destroy ''name'PowerOff''' button in the VM window</code> command. You'll should want to avoid a forced shutdown since those are that is equivalent to yanking the cord out of the wall on a physical machine!|}}<ol> <li value="6"># Confirm that ''fedora3'' has been shut down.</li> <li># Execute this 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> <li value="11"># 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.</ol>

'''Answer the == Investigation 5 observations / questions in your lab log book.''': How do I backup a virtual machine? ==

== Investigation 6: How do I backup a virtual machine? == {{Admon/important|Backing up VMs|Taking the time to backup the image of the Operating System's file system allows the user to return to a '''"restoration point"''' in case something bad occurs to the OS during a lab. 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>{{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.}}

{{Admon/important|Backing up VMs|Note: It 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.}}

{{Admon/tip|Shutting Down the Host while Virtual Machines are Running|Note: If you shut down your host system while virtual machines are running, they will be suspended, and will resume the next time you boot your host system.}}

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

'''Answer the Investigation 7 6 observations / questions in your lab log book.'''

# Lag Lab Logbook (lab2) notes filled-in.

# The kickstart installation (fedora3) was a installations you performed were network installationinstallations. 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?)