Difference between revisions of "OPS235 Lab 2 Braille"

From CDOT Wiki
Jump to: navigation, search
(Created page with 'Category:OPS235Category:OPS235 Labs = OPS235 Lab 2 - Braille : Fedora 16 Installation on Virtual Machines = == Introduction == A '''virtual machine''' is a software sim…')
 
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
[[Category:OPS235]][[Category:OPS235 Labs]]
 
[[Category:OPS235]][[Category:OPS235 Labs]]
 +
{{Admon/caution|Braille Only|If you are not using a braille reader, please use [[OPS235 Lab 2]] instead of this lab.}}{{Admon/note|htp|Wherever this document says "htp", it should be changed to "http". This was done in order to avoid reported problems with some braille readers.}}
 
= OPS235 Lab 2 - Braille : Fedora 16 Installation on Virtual Machines =
 
= OPS235 Lab 2 - Braille : Fedora 16 Installation on Virtual Machines =
  
Line 21: Line 22:
  
 
* Completion and Instructor "Sign-off" of Lab 1: [[OPS235 Lab 1]]
 
* Completion and Instructor "Sign-off" of Lab 1: [[OPS235 Lab 1]]
−
 
  
 
==Linux Command Online Reference==
 
==Linux Command Online Reference==
Line 42: Line 42:
  
 
# Install the Fedora virtualization software: <code>yum groupinstall "Virtualization"</code> or <code>pkcon install @virtualization</code>  The virtualization software installed is in three parts:
 
# 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.
+
#* '''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.
+
#* '''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.
+
#* The actual '''virtual machines''' themselves.
−
<ol>
+
# Reboot your system.
−
<li value="2">Start the virtualization service: <code>service libvirtd start</code></li>
+
# Start the virtualization service: <code>systemctl start libvirtd</code>
−
<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>
 
−
</ol>
 
−
 
 
−
 
 
−
{{Admon/caution|Reboot your fedora host|There appears to be an issue with supplying your VM's with a dynamic IP unless the host is restarted after installing "Virtualization". '''Reboot now to avoid this problem.'''}}
 
  
−
<ol>
+
== Investigation 1: Network Install with Kickstart ==
−
<li value="4">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 <code>virt-manager</code></li>
 
−
</ol>
 
  
−
{{Admon/important|Run virt-manager as a regular user|Running virt-manager as root may not work due to configuration issues.}}
+
=== VM Details ===
−
 
 
−
 
 
−
== Investigation 1: Installing from a Live Disc ==
 
−
 
 
−
{{Admon/tip|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 download the .iso image file from http://belmont.senecac.on.ca/fedora/releases/16/Live/x86_64/Fedora-16-x86_64-Live.iso and install directly from that file. 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
 
* '''Name:''' fedora1
−
* '''Boot media:''' Fedora Live CD
+
* '''Boot Media and Installation source:''' Network server: belmont.senecac.on.ca/fedora/releases/16/Fedora/x86_64/os/
−
* '''Installation source:''' Fedora Live CD
+
* '''Kickstart file:''' zenit.senecac.on.ca/~chris.tyler/fedora16-vda-ks-200.cfg
−
* '''Memory:''' 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 ]]
 
−
|}
 
−
 
 
−
==== Steps ====
 
−
 
 
−
# 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'''  (refer to ''Step 1 of 5'' thumbnail above).
 
−
# '''Step 2 of 5:''' '''Insert the CDROM or DVD containing the Fedora Live Disc image. Wait a moment for the disc to be recognized''', then select '''Use CDROM or DVD''' as the install media. Set the ''OS type'' to '''Linux''' and the ''Version'' to '''Fedora 16''' (refer to ''Step 2 of 5'' thumbnail above).
 
−
<!-- {{Admon/tip|Using an ISO image|Instead of using a physical CD or DVD, you can use an ISO image of a CD or DVD. The virtualization software will make this ISO image appear like an actual CD within the virtual machine. Because hard disks are faster then optical discs, this will work faster than an actual CD/DVD.}}{{Admon/note|Choosing the operating system type and version|The purpose of the ''OS type'' and ''Version'' fields is to fine-tune some of the virtual machine settings for best performance. The VM will work even if these are set incorrectly.}} -->
 
−
# '''Step 3 of 5:''' Set the memory to '''768 MB''' and the number of CPUs to '''1''' (refer to ''Step 3 of 5'' thumbnail above).
 
−
# '''Step 4 of 5:''' This next step creates a disk file that will be used to simulate the virtual machine's disk drive. Select a size of '''10 GB''' and checkmark the box labeled '''Allocate entire disk now''' (refer to ''Step 4 of 5'' thumbnail above).
 
−
# '''Step 5 of 5:''' Review the options that you have selected. '''Make a note of the storage location.''' If anything needs to be changed, use the ''Back'' button to go back and edit it; otherwise, click '''Finish''' (refer to ''Step 5 of 5'' thumbnail above).
 
−
 
 
−
{{Admon/caution|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.|'''}}
 
−
 
 
−
 
 
−
{{Admon/note|Fedora LIVE CD Install Screen Shots Thumbnails|While performing the Fedora 16 LIVE 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.]]
 
−
|[[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 16'''. 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>
 
−
 
 
−
{{Admon/note|Gnome3: failed to Load Message|A dialog box will indicate that '''Gnome3 Failed to Load'''. This indicates that a "fall-back" or "generic" graphics driver will be used for the session. Just ignore this warning, close the dialog box and proceed with the session.
 
−
}}
 
−
 
 
−
<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>
 
−
 
 
−
{{Admon/note|Error Message|If you experience an error message, exit the VM window, close the Virtual Machine Manager program, reboot your host (main) computer, login and restart the Virtual Machine Manager program. Failure to follow this instructions can lead students to think that the virtual machine was not installed (when it was indeed installed).
 
−
}}
 
−
 
 
−
<ol>
 
−
<li value="13">Start the VM from its disk image. This can be done graphically by selecting the Virual machine name, and then clicking on the '''Open''' button, and then click the '''play''' button when the next screen appears (or by selecting Virtual Machine>Run from the virtual machine menu). You will get the ''Firstboot'' configuration questions during the boot process (asking you to create a user, set the date and time, and optionally send the hardware profile to the Fedora Project). Create a user with the same name as your Matrix account.</li>
 
−
<li>Login using the new user account.</li>
 
−
</ol>
 
−
 
 
−
{{Admon/note|Network / Service Considerations|Please perform the tasks below in order allow these Fedora systems to be able to communicate with each other. '''Failure to properly perform these operations can cause problems in future labs'''.|
 
−
}}
 
−
 
 
−
<ol>
 
−
<li value="15">Enable SSH access to your virtual machine with these commands (semi-colon allows commands to be run in sequence):<br /> <code>service sshd start; chkconfig sshd on</code></li>
 
−
<li>Find out the IP address of your virtual machine: <code>ifconfig eth0</code> </li>
 
−
<li>Enter the following command on your virtual machine to create a firewall exception to allow ssh traffic into the machine:<br />  <code>iptables -I INPUT -p tcp -s0/0 -d0/0 --dport 22 -j ACCEPT</code></li>
 
−
<li>Confirm that you can ssh to your virtual machine from the host (your main Fedora installation): <code>ssh ''IPaddress''</code></li>
 
−
</ol>
 
−
 
 
−
{{Admon/tip|Switch to Virtual Machine Manager Window|If you are currently in a Virtual machine, but want to switch to the Virtual Machine Manager Window, simply click '''Activities'''> '''Select the Virtual Machine manager window'''.}}
 
−
 
 
−
'''Answer the Investigation 1 observations / questions in your lab log book.'''
 
−
 
 
−
== Investigation 2: Installing from the Network ==
 
−
 
 
−
{{Admon/tip|Authenticate to the network|The rest of this lab uses network access.''' Be sure to authenticate to the network using your browser before proceeding'''.}}
 
−
 
 
−
=== Introduction ===
 
−
 
 
−
It is possible to install Fedora entirely from the network. In this investigation, you will install Fedora from a webserver on Seneca's LAN.
 
−
 
 
−
==== VM details ====
 
−
 
 
−
* '''Name:''' fedora2
 
−
* '''Boot media:''' Network installation
 
−
* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/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
 
* '''Memory:''' 768MB
 
* '''Disk space:''' 10GB
 
* '''Disk space:''' 10GB
 
* '''CPUs:''' 1
 
* '''CPUs:''' 1
  
−
==== Steps ====
+
=== Steps to Perform ===
−
# 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.'''
+
# Record the current time.
 +
# 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 htp://belmont.senecac.on.ca/fedora/releases/16/Fedora/x86_64/os/ -x ks=htp://zenit.senecac.on.ca/~chris.tyler/fedora16-vda-ks-200.cfg --noautoconsole
 +
# The virtual machine will stop when the installation is complete. You can see if the virtual machine is running with the command: virsh list
 +
# Record the approximate time that the installation ends. Subtract the start time to find out how long the installation took.
 +
# Once the virtual machine has been installed, start it with this command: virsh start fedora1
 +
# In order to connect to the virtual machine, you need to know:
 +
#* The IP address.
 +
#* The account name and password of a regular user.
 +
#* The password for the root (administrator) user.
 +
# 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.
 +
# Using the information you gathered from the kickstart file, connect to the virtual machine: ssh '''accountname''@'''IPaddress'' (substitute the correct account name and IP address)
 +
# Enter the password when requested.
 +
# On the virtual machine, determine:
 +
#* The number of packages installed
 +
#* The amount of free disk space
 +
# Stop the virtual machine by typing, as the root user inside that virtual machine, the command: poweroff
 +
# Confirm that the virtual machine is off by executing this command on your f16host: virsh list
  
−
== Investigation 4: Updating and Comparing the VMs ==
+
== Investigation 2 ==
  
−
# In each VM, run this command: <code>yum update</code>
+
# Install another virtual machine by modifying the command used in Investigation 1. Incorporate these changes:
−
# Record the answers to these questions in your log book:
+
## Use the name "fedora2" for this virtual machine.
−
#* How long did it take to run on each VM? How many packages were updated?
+
## Change the name of the disk file to match the name of the virtual machine.
−
#* Why does it take longer in some VMs than others?
+
## Use a disk size of 15G
 +
# Start fedora2 and confirm that you can connect to it.
 +
# The IP address on fedora1 and fedora2 are the same, which would cause a conflict if they were booted at the same time. Change the IP address of fedora2 to 192.168.122.201 by editing the file /etc/sysconfig/network-scripts/ifcfg-eth0
 +
# Restart fedora2 and confirm that the IP address has changed to the correct value.
 +
# Shut down fedora2.
  
−
Complete the following table (and transfer into your lab2 log-book notes):
+
== Investigation 3 ==
  
−
{|border="1" width="100%" cellpadding="5"
+
# 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 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).
−
|-
+
# Modify the command used in Investigation 1 to incorporate these changes:
−
! ||f16host||fedora1||fedora2||fedora3
+
## Use the name "fedora3" for this virtual machine.
−
|-
+
## Change the name of the disk file to match the name of the virtual machine.
−
|'''Installation Method'''||Installation Disc||Live Disc||Network Installation||Network Installation + Kickstart
+
## Use a disk size of 12G.
−
|-
+
## Use your kickstart file instead of the original one.
−
|'''Packages Installed'''|| || || ||
+
# Start fedora3 and confirm that you can connect to it, using your Matrix ID and password.
−
|-
+
# Shut down fedora3.
−
|'''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 ==
+
== Investigation 4: 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.}}
+
Note: The commands used to manage virtual machines must be executed on the host (your disk pack) and not inside virtual machine. Use the host name information in the command prompt to confirm that you are on the correct machine when entering commands.
  
−
# Start the ''fedora1'' virtual machine, and stop the ''fedora2'' and ''fedora3'' virtual machines.
+
# Start the ''fedora1'' virtual machine.
 
# Enter these commands and note the result:
 
# Enter these commands and note the result:
 
#* <code>virsh list</code>
 
#* <code>virsh list</code>
Line 270: Line 112:
 
# Start the ''fedora3'' virtual machine from the command line: <code>virsh start fedora3</code>
 
# Start the ''fedora3'' virtual machine from the command line: <code>virsh start fedora3</code>
 
# Repeat the commands from step 2 and notice any changes.
 
# Repeat the commands from step 2 and notice any changes.
−
# Stop the ''fedora3'' virtual machine: <code>virsh shutdown fedora3</code>
+
# Stop the ''fedora3'' virtual machine: <code>virsh shutdown fedora3</code> Note: If the Virtual machine fails to shutdown from the <code>virsh shutdown</code> command or from the <code>halt</code> or <code>poweroff</code> or <code>shutdown</code> commands within the VM, you can use dthe <code>virsh destroy ''name''</code> command. You should want to avoid a forced shutdown since that is equivalent to yanking the cord out of the wall on a physical machine!
−
 
+
# Confirm that ''fedora3'' has been shut down.
−
 
+
# Execute this command: <code>virsh dumpxml fedora3 >fedora3.xml</code>
−
{{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!|}}
+
# Examine the file <code>fedora3.xml</code>. What does it contain? What format is it in?
−
<ol>
+
# Make a copy of <code>fedora3.xml</code> called <code>fedora3a.xml</code>.
−
<li value="6">Confirm that ''fedora3'' has been shut down.</li>
+
# Edit the file <code>fedora3a.xml</code>, making the following changes:
−
<li>Execute this command: <code>virsh dumpxml fedora3 >fedora3.xml</code></li>
+
#* Change the name (in the file, not the file name) to <code>fedora3a</code>
−
<li>Examine the file <code>fedora3.xml</code>. What does it contain? What format is it in?</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.
−
<li>Make a copy of <code>fedora3.xml</code> called <code>fedora3a.xml</code>.</li>
+
# Issue this command: <code>virsh define fedora3a.xml</code>
−
<li>Edit the file <code>fedora3a.xml</code>, making the following changes:</li>
+
# Issue the command <code>virsh list --all</code> and record any changes.
−
</ol>
+
# Issue the command: <code>virsh undefine fedora3a</code>
−
::* Change the name (in the file, not the file name) to <code>fedora3a</code>
+
# List all of the virtual machines again, and note any changes.
−
::* 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.'''
+
== Investigation 5: How do I backup a virtual machine? ==
  
−
== Investigation 6: How do I backup a virtual machine? ==
+
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!
−
 
 
−
{{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!|}}
 
  
 
# Shut down all of the virtual machines.
 
# 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?
 
# 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>
+
# 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> 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/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>
 
<ol>
 
  <li value="4">Compare the size of the compressed and original files.</li>
 
  <li value="4">Compare the size of the compressed and original files.</li>
Line 313: Line 145:
 
::* In order to fully back up a virtual machine, what information should be saved in addition to the virtual machine image?
 
::* In order to fully back up a virtual machine, what information should be saved in addition to the virtual machine image?
  
−
{{Admon/important|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.}}
+
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|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.}}
+
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 observations / questions in your lab log book.'''
+
'''Answer the Investigation 5 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 1-16 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.}}
+
== Investigation 6: Kickstart Files ==
  
 
When you perform a non-Kickstart installation, the installation program creates a Kickstart file in the <code>/root</code> directory for reference.
 
When you perform a non-Kickstart installation, the installation program creates a Kickstart file in the <code>/root</code> directory for reference.
Line 329: Line 159:
 
# How could you use the kickstart file produced by the installation program to perform additional, identical installations?
 
# 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.'''
+
'''Answer the Investigation 6 observations / questions in your lab log book.'''
  
 
= Completing the Lab =
 
= Completing the Lab =
Line 337: Line 167:
 
# Three working virtual machines created.
 
# Three working virtual machines created.
 
# Four kickstart files.
 
# Four kickstart files.
−
# All virtual machines fully updated.
 
 
# All virtual machines backed up.
 
# All virtual machines backed up.
 
# Installation comparison table filled in.
 
# Installation comparison table filled in.
−
# Lag Logbook (lab2) notes filled-in.
+
# Lab Logbook (lab2) notes filled-in.
  
 
= Preparing for the Quizzes =
 
= Preparing for the Quizzes =
  
 
# What is the name of the Fedora installation program?
 
# What is the name of the Fedora installation program?
−
# 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?
 
−
# Which type of installation works best for confirming compatibility with hardware before installation? Why?
 
−
# Which type of installation works best for installing large numbers of computers? Why?
 
 
# What factors affect installation time?
 
# What factors affect installation time?
−
# How can you reduce the number of software updates required immediately after installation?
 
−
# Why would you enable additional repositories during installation?
 
 
# What does the file <code>/root/anaconda-ks.cfg</code> contain, and how is it created?
 
# What does the file <code>/root/anaconda-ks.cfg</code> contain, and how is it created?
 
# How do you start and stop virtual machines?
 
# How do you start and stop virtual machines?
Line 361: Line 185:
 
#* virt-install
 
#* virt-install
 
#* kvm
 
#* kvm
−
# The kickstart installation (fedora3) was a network installation. Can a kickstart file be used with a DVD installation?
+
# The installations you performed were network installations. 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?)
 

Latest revision as of 13:19, 14 February 2012

Stop (medium size).png
Braille Only
If you are not using a braille reader, please use OPS235 Lab 2 instead of this lab.
Note.png
htp
Wherever this document says "htp", it should be changed to "http". This was done in order to avoid reported problems with some braille readers.

OPS235 Lab 2 - Braille : Fedora 16 Installation on Virtual Machines

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.

Objectives

  • Understand Virtualization
  • Use KVM virtualization on Fedora
  • Use Kickstart and Network Installation Methods

Prerequisites

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

Linux Command Online Reference

See the manpages for:

  • virsh
  • gzip / gunzip

Resources on the Web

Performing Lab 2

Preparation

  1. 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.
  2. Reboot your system.
  3. Start the virtualization service: systemctl start libvirtd

Investigation 1: Network Install with Kickstart

VM Details

  • Name: fedora1
  • Boot Media and Installation source: Network server: belmont.senecac.on.ca/fedora/releases/16/Fedora/x86_64/os/
  • Kickstart file: zenit.senecac.on.ca/~chris.tyler/fedora16-vda-ks-200.cfg
  • Memory: 768MB
  • Disk space: 10GB
  • CPUs: 1

Steps to Perform

  1. Record the current time.
  2. 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 htp://belmont.senecac.on.ca/fedora/releases/16/Fedora/x86_64/os/ -x ks=htp://zenit.senecac.on.ca/~chris.tyler/fedora16-vda-ks-200.cfg --noautoconsole
  3. The virtual machine will stop when the installation is complete. You can see if the virtual machine is running with the command: virsh list
  4. Record the approximate time that the installation ends. Subtract the start time to find out how long the installation took.
  5. Once the virtual machine has been installed, start it with this command: virsh start fedora1
  6. In order to connect to the virtual machine, you need to know:
    • The IP address.
    • The account name and password of a regular user.
    • The password for the root (administrator) user.
  7. To gather the information listed above, study the kickstart file. Record your answers.
  8. Using the information you gathered from the kickstart file, connect to the virtual machine: ssh accountname@IPaddress (substitute the correct account name and IP address)
  9. Enter the password when requested.
  10. On the virtual machine, determine:
    • The number of packages installed
    • The amount of free disk space
  11. Stop the virtual machine by typing, as the root user inside that virtual machine, the command: poweroff
  12. Confirm that the virtual machine is off by executing this command on your f16host: virsh list

Investigation 2

  1. Install another virtual machine by modifying the command used in Investigation 1. Incorporate these changes:
    1. Use the name "fedora2" for this virtual machine.
    2. Change the name of the disk file to match the name of the virtual machine.
    3. Use a disk size of 15G
  2. Start fedora2 and confirm that you can connect to it.
  3. The IP address on fedora1 and fedora2 are the same, which would cause a conflict if they were booted at the same time. Change the IP address of fedora2 to 192.168.122.201 by editing the file /etc/sysconfig/network-scripts/ifcfg-eth0
  4. Restart fedora2 and confirm that the IP address has changed to the correct value.
  5. Shut down fedora2.

Investigation 3

  1. Make a copy of the 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 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).
  2. Modify the command used in Investigation 1 to incorporate these changes:
    1. Use the name "fedora3" for this virtual machine.
    2. Change the name of the disk file to match the name of the virtual machine.
    3. Use a disk size of 12G.
    4. Use your kickstart file instead of the original one.
  3. Start fedora3 and confirm that you can connect to it, using your Matrix ID and password.
  4. Shut down fedora3.

Investigation 4: Managing Virtual Machines from the Command Line

Note: The commands used to manage virtual machines must be executed on the host (your disk pack) and not inside virtual machine. Use the host name information in the command prompt to confirm that you are on the correct machine when entering commands.

  1. Start the fedora1 virtual machine.
  2. Enter these commands and note the result:
    • virsh list
    • virsh list --all
    • virsh list --inactive
  3. Start the fedora3 virtual machine from the command line: virsh start fedora3
  4. Repeat the commands from step 2 and notice any changes.
  5. Stop the fedora3 virtual machine: virsh shutdown fedora3 Note: If the Virtual machine fails to shutdown from the virsh shutdown command or from the halt or poweroff or shutdown commands within the VM, you can use dthe virsh destroy name command. You should want to avoid a forced shutdown since that is equivalent to yanking the cord out of the wall on a physical machine!
  6. Confirm that fedora3 has been shut down.
  7. Execute this command: virsh dumpxml fedora3 >fedora3.xml
  8. Examine the file fedora3.xml. What does it contain? What format is it in?
  9. Make a copy of fedora3.xml called fedora3a.xml.
  10. 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.
  11. Issue this command: virsh define fedora3a.xml
  12. Issue the command virsh list --all and record any changes.
  13. Issue the command: virsh undefine fedora3a
  14. List all of the virtual machines again, and note any changes.

Investigation 5: How do I backup a virtual machine?

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!

  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 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.}}
  1. Compare the size of the compressed and original files.
  2. Start the fedora3 VM.
  3. Make certain that you are in your fedora VM, and not in your Fedora main system.
  4. Wreck only 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!): rm -rf /*
  5. Shut down the VM.
  6. Restore the original image from the backup in your home directory (type this command carefully): gunzip <~YourUserId/fedora3.img.backup.gz >fedora3.img
  7. Restart the VM. Is it working normally?
  8. Create compressed backups of your other virtual machines.
  9. 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?

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.

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 5 observations / questions in your lab log book.

Investigation 6: Kickstart Files

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 f16host, plus the fedora1, fedora2, and fedora3 virtual machines). Copy them all to your f16host system (tip: use scp).
  2. Compare these files. What are the differences? Similarities? (Tip: you may want to use tools such as sdiff to help with the comparison).
  3. How could you use the kickstart file produced by the installation program to perform additional, identical installations?

Answer the Investigation 6 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 backed up.
  4. Installation comparison table filled in.
  5. Lab Logbook (lab2) notes filled-in.

Preparing for the Quizzes

  1. What is the name of the Fedora installation program?
  2. What factors affect installation time?
  3. What does the file /root/anaconda-ks.cfg contain, and how is it created?
  4. How do you start and stop virtual machines?
  5. How do you SSH into your virtual machines?
  6. What is the purpose of and relationship between these pieces of software?
    • libvirt
    • libvirtd
    • virsh
    • virt-manager
    • virt-install
    • kvm
  7. The installations you performed were network installations. Can a kickstart file be used with a DVD installation?
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=OPS235_Lab_2_Braille&oldid=81386"