OPS235 Lab 2 - Fedora17

THIS IS AN OLD VERSION OF THE LAB
This is an archived version. Do not use this in your OPS235 course.

Fedora 17 Installation Methods (on Virtual Machines: fedora1, fedora2, fedora3)

Introduction

A virtual machine is a software simulation of a computer which can be used as though it were actual hardware. It's possible to run multiple virtual machines on one computer, reducing hardware requirements and introducing flexibility. Some common uses of virtualization include:

• 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.

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 (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:

Method Boot Media Install. Source CD or DVD ✓ ✓ Hard Disk ✓ ✓ USB Flash Drive ✓ ✓ Network (http/nfs repository) ✓ ✓ PXE Network Boot ✓ X

Objectives

• Understand Virtualization
• Use KVM virtualization on Fedora
• Use a variety of installation methods:
  • Live Image Installation
  • Network Installation
  • Kickstart Installation
• Understand the advantages and disadvantages of each type of installation, and be able to select the best installation method for a particular situation.

Required Materials (Bring to All Labs)

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

Prerequisites

• Completion and Instructor "Sign-off" of Lab 1: OPS235 Lab 1

Linux Command Online Reference

Each Link below displays online manpages for each command (via http://linuxmanpages.com):

• virsh (Refer to Fedora Virtualization Guide link in the "Resources on the Web" section)
• gzip / gunzip

Resources on the Web

Virtualization:	Live Image Installation:	Network Installation:	Kickstart Installation:
Fedora Virtualization Guide	Fedora 17 Live Image Guide Fedora 17 Installation Quick Start Guide	Fedora 17 Installation Guide Preparing for a Network Installation Performing a Network Installation	Fedora 17 Installation Guide Automating the Installation with Kickstart Kickstart Installations Kickstart Configurator

Performing Lab 2

Preparation

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 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 must be done at Seneca.

1. Open a web-browser, and open the OPS235 Lab #2 WIKI.
   
   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...
   
   
2. Install the Fedora virtualization software: yum groupinstall "Virtualization" or pkcon install @virtualization The virtualization software installed is in three parts:

• A system service named libvirtd that manages the VMs.
• Tools to manage virtualization, including the virt-manager graphical tool and the virsh command-line tool.
• The actual virtual machines themselves.

3. Start the virtualization service: service libvirtd start
4. The firewall configuration is altered by the addition of the virtualization software. Restart the firewall so that these changes become active: service iptables restart

Reboot your fedora host now
virt-manager may not work properly unless you reboot after installing the virtualization software.

5. After rebooting your computer system, and logging back into your account, start the graphical tool by selecting the menu options Activities>Applications>System Tools>Virtual Machine Manager or by typing the command virt-manager

Run virt-manager as a regular user
Running virt-manager as root may not work due to configuration issues.

Investigation 1: Installing from a Live Disc

Using an Image instead of a Live Disc
It is recommended that you perform this installation from your Fedora LIVE 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 CD. 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 Live CD
• Installation source: Fedora Live CD
• Memory: 768MB
• Disk space: 10GB
• CPUs: 1

Screen-Shot Thumbnail Reference

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.

Virtual Machine Manager: Create a New Virtual Machine

Step 1 of 5: Create a New Virtual Machine

Step 2 of 5: Create a New Virtual Machine

Step 3 of 5: Create a New Virtual Machine

Step 4 of 5: Create a New Virtual Machine

Step 5 of 5: Create a New Virtual Machine

Steps

1. In the Virtual Machine Manger, click on the icon to Create a Virtual Machine in the upper-left corner:
   (refer to Virtual Machine Manager thumbnail above).
2. A window will appear with the title New VM. There are five steps to be completed; click Forward after each step:
3. Step 1 of 5: Enter the virtual machine (called fedora1) name and select Local install media (refer to Step 1 of 5 thumbnail above).
4. 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).
5. 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).
6. 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).
7. 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).

Removing and Recreating VMs
If for some reason the user wants to remove a Virtual Machine, they can right-click the VM, and select delete in the Virtual Machine Manager. It is recommended to "delete the image file" in the remove VM dialog box when removing and then recreating a VM. Note: If you fail to properly remove the VM image file, it may affect the hard disk size for the new VM (i.e. use the old smaller size. Make certain to remove that VM image file prior to recreating the VM.

Fedora LIVE CD Install Screen Shots Thumbnails
While performing the Fedora 17 LIVE CD install, click on the thumbnails below to provide a "visual reference" while performing this particular Fedora installation.

The Virtual Machine will now start.

Ignore and close the "Failed To Load" dialog box. Search for the panel on the upper-left-hand side of the screen.

Login to the VM and double-click: Applications >System Tools >Install to Hard Disk.

Select Specialized Storage Devices

Select Virtio Block Device.

You will get the Firstboot configuration questions during the boot process.

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.

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.

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.

10. During the installation process, when prompted for a storage device, first select Specialized Storage Devices, and then select the Virtio Block Device option.
11. 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.
12. When the installation is complete, click on the reboot button at the bottom right-hand corner of the screen.

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.
14. Login using the new user account.

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.

15. Enable SSH access to your virtual machine with these commands (semi-colon allows commands to be run in sequence):
    service sshd start; chkconfig sshd on
16. Find out the IP address of your virtual machine: ifconfig eth0
17. Enter the following command on your virtual machine to create a firewall exception to allow ssh traffic into the machine:
    iptables -I INPUT -p tcp -s0/0 -d0/0 --dport 22 -j ACCEPT
18. Confirm that you can ssh to your virtual machine from the host (your main Fedora installation): ssh IPaddress

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

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

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/17/Fedora/x86_64/os/
   • In step 2 of 5, set the OS Type to Linux and Version to Fedora 17.
2. Observe the boot process. How is it different from booting from an optical disc (CD/DVD)?
3. Start the installation process (make certain to use information in the VM Details section above).
4. 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).
5. On the software selection screen, select Graphical Desktop.
6. 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.
7. 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

1. 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
2. Observe the installation. How is it different from booting from an optical disc (CD/DVD)?
3. Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations.
4. What happens when the installation is finished?
5. Take a look at the kickstart file (using the URL you entered) to determine the root password as well as the name and password for the first user account.
6. 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

1. In each VM, run this command: yum update
2. 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):

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

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.

1. Start the fedora1 virtual machine, and stop the fedora2 and fedora3 virtual machines.
2. Switch to the f19host machine, and open a shell terminal.
3. Enter these commands into your f19host machine and note the result:
   • virsh list
   • virsh list --all
   • virsh list --inactive
4. Now, shut-down your fedora1 VM normally, and close the fedora1 VM window. Make certain NOT to close the Virtual Machine Manager main window.
5. Switch to your terminal and issue the command: virsh start fedora1
6. Check to see if your fedora1 VM is now running.
7. Switch to the terminal and issuevirsh list --all and confirm the status of the fedora1 VM.
8. 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?

Virtual Machine Does not Shutdown from Command
If the Virtual machine fails to shutdown from the virsh shutdown 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!

Answer the Investigation 5 observations / questions in your lab log book.

Investigation 6: How do I backup a virtual machine?

Backing up VMs
There are two general processes in order to back up your images:

1. Compressing your images (also recommended to backup up to external storage USB Key) using the gzip command.
2. 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).

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.
Failure to take the time to make and confirm backups can result in loss of lab work for the student!

1. Shut down all of the virtual machines.
2. Change to the directory /var/lib/libvirt/images/. Note the size of the files in this directory. What do these files contain?
3. Make a compressed backup of the fedora3.img file to your home directory with this command: gzip < fedora3.img > ~YourUserId/fedora3.img.backup.gz
   (Note: Make certain to use the redirection signs "<" and ">" properly in the command!)

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.

4. Compare the size of the compressed and original files.
5. Start the fedora3 VM.
6. Make certain that you are in your fedora VM and not in your Fedora main system!
7. Wreck only your fedora 3 system! Try this command inside the fedora3 virtual machine: rm -rf /*
8. Shut down the VM. If you tried to start the Fedora3 VM, it would not boot since all system files have been removed!
9. Restore the original image from the backup in your home directory by typing this command: gunzip < ~YourUserId/fedora3.img.backup.gz > fedora3.img
10. Restart the VM. Is it working normally?
11. Create compressed backups of your other virtual machines.

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:
    1. Verify that you are in the directory: /var/lib/libvirt/images/.
    2. Execute the following command: virsh dumpxml fedora3 >fedora3.xml
    3. Examine the file fedora3.xml. What does it contain? What format is it in?
    4. Make a copy of fedora3.xml called fedora3a.xml.
    5. Edit the file fedora3a.xml, making the following changes:

    • Change the name (in the file, not the file name) to fedora3a
    • 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.

    6. Issue this command: virsh define fedora3a.xml
    7. Issue the command virsh list --all and record any changes.
    8. Issue the command: virsh undefine fedora3a
    9. List all of the virtual machines again, and note any changes.
13. For the remainder of these labs, it is assumed that you will backup both the images and xml configuration files for all 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...
14. Answer this question in your log book:

• In order to fully back up a virtual machine, what information should be saved in addition to the virtual machine image?

Backing up VMs
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.

Shutting Down the Host while Virtual Machines are Running
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 observations / questions in your lab log book.

Investigation 7: Kickstart Files

SSHD and Firewall
If you have restarted your virtual machine fedora1, the 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.

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).

When you perform a non-Kickstart installation, the installation program creates a Kickstart file in the /root directory for reference.

1. Obtain the kickstart files for all four of your installations (your disk pack f17host, plus the fedora1, fedora2, and fedora3 virtual machines).
2. To prevent confusion, copy your kickstart files to kickstart filenames that describe their purpose (eg. kickstart_host, kickstart_fedora1, kickstart_fedora2, etc...)
3. Copy them all to your f17host system (tip: use scp), or use the hint in the tip box above to send via e-mail.
4. Compare these files. What are the differences? Similarities? (Tip: you may want to use tools such as sdiff to help with the comparison).
5. How could you use the kickstart file produced by the installation program to perform additional, identical installations?

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

Completing the Lab

Arrange evidence for each of these items on your screen, then ask your instructor to review them and sign off on the lab's completion:

1. Three working virtual machines created.
2. Four kickstart files.
3. All virtual machines fully updated.
4. All virtual machines backed up.
5. Installation comparison table filled in.
6. Lab Logbook (lab2) notes filled-in.

Preparing for Quizzes

1. What is the name of the Fedora installation program?
2. Which factors recorded in your table (above) were due to the type of installation performed, and which factors were due to the amount of software installed?
3. Which type of installation works best for confirming compatibility with hardware before installation? Why?
4. Which type of installation works best for installing large numbers of computers? Why?
5. What factors affect installation time?
6. How can you reduce the number of software updates required immediately after installation?
7. Why would you enable additional repositories during installation?
8. What does the file /root/anaconda-ks.cfg contain, and how is it created?
9. How do you start and stop virtual machines?
10. How do you SSH into your virtual machines?
11. What is the purpose of and relationship between these pieces of software?
    • libvirt
    • libvirtd
    • virsh
    • virt-manager
    • virt-install
    • kvm
12. The kickstart installation (fedora3) was a network installation. Can a kickstart file be used with a DVD installation?
13. The kickstart installation (fedora3) was fairly fast. Why? Under what circumstances would it take a long time, even on a fast network?
14. What other types of installation sources are possible (besides Live Disc, Installation Disc, and Network?)