1,576
edits
Changes
no edit summary
[[Category:OPS235]][[Category:OPS235 Labs]]
{{Admon/caution|THIS IS AN OLD VERSION OF THE LAB|'''This is an archived version. Do not use this in your OPS235 course.'''}}
= Fedora 19 Installation Methods (on Virtual Machines: fedora1, fedora2, fedora3) =
You should already have both a '''Fedora installation DVD''' and a '''Fedora LIVE CDDVD'''.
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
! ✓
! ✓
== Required Materials (Bring to All Labs) ==
* Fedora 19 LIVE CDDVD
* SATA Hard Disk (in removable disk tray)
* USB Memory Stick
:* '''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/virtualizationen-guideUS/f13Fedora/en-US19/html/ Virtualization_Getting_Started_Guide/index.html Fedora Virtualization Getting Started Guide]
|
* [http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Quick_Start_Guide/ Fedora 19 Installation Quick Start Guide]
|
<ol>
<li value="4">Start the virtualization serviceusing the systemctl command: <code>'''systemctl start libvirtd.service libvirtd start'''</code></li> <li>The firewall configuration is altered by the addition of the virtualization software. Restart the firewall so that these changes become active: <code>'''systemctl restart iptables.service iptables restart'''</code></li>
</ol>
{{Admon/cautiontip|Reboot Maybe reboot your fedora host now|Sometimes virt-manager may does not work properly unless you reboot after installing the virtualization software.}}
<ol>
<li value="7">You will be prompted to enter your root password: enter your user (not root ) password and click the "'''Authenticate'''" button.</li>
<li>Record the setup commands in your lab log-book.</li>
<li>Proceed to Investigation 1.</li>
</ol>
{{Admon/important|Note Comparison Chart In Investigation #4| In the next 3 investigations, you will install Fedora19 as separate virtual machines using different install techniques. '''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 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 CD DVD (950MB). As a matter of interest (for future reference), it is possible to install directly from the ISO file you used to burn your Live CDDVD. There are many Internet tutorials that show the individual how to perform that task.}}
==== Introduction ====
* '''Name:''' fedora1
* '''Boot media:''' Fedora 19 Desktop Live CD/DVD* '''Installation source:''' Fedora 19 Desktop Live CD/DVD* '''Memory:''' 768MB1024MB* '''Disk space:''' 10GB15GB
* '''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-manager2a.png|thumb|100px|'''Insert Fedora19 Live DVD''' (Click black dialog box) ]]
|[[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 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 select "'''Use CDROM or DVD'''".
# Under "Location your install media section", select "'''Use CDROM or DVD'''". Set the ''OS type'' to '''Linux''' and the ''Version'' to '''Fedora 19''' (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 '''768 1024 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 '''10 15 GB''' and checkmark check-mark the box labeled labelled '''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 CD DVD Install Screen Shots Thumbnails|While performing the Fedora 19 LIVE CD DVD 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 startin '''Live''' mode.'''Install to Hard Disk''']]|[[Image:failedtoloadInstallscreen.png|thumb|140px| '''Ignore Installation Summary''' dialog box. Used to select '''Date and close the "Failed To Load" Time''' as well as '''Installation Destination''']]|[[Image:Installationdestination1.png|thumb|140px|'''Installation Destination''' dialog box(confirm and select '''done'''. Search for the panel on the upper-left-hand side of the screen).]]|[[Image:fedoralive2Installationdestination2.png|thumb|140px|Login to the VM and double-click:<br /> '''ApplicationsInstallation Options'''<br />>dialog box within '''System ToolsInstallation Destination'''<br />>process (make suggested settings and select '''Install to Hard Diskdone''').]]|[[Image:selectstorage1Installationdestination3.png|thumb|100px140px|Select '''Specialized Storage DevicesManual Partitioning''' dialog box within '''Installation Destination''' process (click link to '''automatically create partitions''' and proceed to next dialog box).]]|[[Image:selectstorage2Installationdestination4.png|thumb|100px140px|Select Confirm partitions to be automatically created and then click '''Virtio Block Devicedone'''.]]|[[Image:finishcdinstallInstallationdestination5.png|thumb|100px140px|You will get Confirm summary of changes, click '''Accept Changes''', then click '''Begin Installation''' at the ''FirstbootInstallation Summary'' configuration questions during the boot processdialog box to proceed with your installation.]]
|}
<ol>
<li value="1011">When you have completed your installation, click the '''The virtual machine will now startQuit'''button. Select You should return to the default menu item labelled: Fedora Live desktop. </li> <li>Shutdown the Fedora Live session by clicking on the '''Live User'Install to Hard Drive'' button (at the top right-hand corner) and select '''Power Off''', and confirm that you want to power-off. It is a good idea to be patient! Sometimes it may take a few minutes for shut-down!</li>
</ol>
}}
<ol>
<li value="1113">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 the installation process.
<li>Set the Time Zone for "'''Toronto'''".</li>
<li>When back at the main installation summary menu, select '''Installation Destination'''.</li>
<li>In the Installation Options dialog box Confirm approx. '''10 15 GB''' for the '''Virtio Block Device''' and click the '''Done''' button in the top left-hand corner. '''Note: It may take a few minutes to access the <u>next</u> Installation Options dialog box, so please be patient!'''</li>
<li>Click "'''I want to review/modify my disk partitions before continuing'''", confirm that the partition scheme is set to '''LVM''', and click the '''Continue''' button.</li>
<li>In the Manual Partitioning dialog box, click on the link "'''Click here to create them automatically'''"</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 the top left-hand corner.</li>
<li>Confirm the Summary of Changes, and then click the "'''Accept Changes'''" button located on the bottom right-hand side. Note: please be patient, and wait a few minutes until you can access the Installation Summary dialog box. Click '''Begin Installation'''. Note the time that it takes to complete this 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 the screen (no password is required for a '''live user''').|
}}
<ol> <livalue="22">When prompted for After the hostnameinstallation process has completed, enter '''fedora1''', and when prompted for click on the timezone, select '''Toronto - Eastern Time Ontario''', and when asked about storage, select '''Use All SpaceQuit'''button. '''Use the default values for all other fields.''' Notice that the installer does not ask This should return you what software should be installed; compare the installation time to the amount LIVE version of time it took Linux that was running to help install to do your Lab 2 installation. Record this information in the '''table contained in Investigation 4'''Hard Drive.</li> <li>When the installation is complete, click Click on the '''reboot''' button live username located at the bottom top right-hand corner of and power-off the screenmachine.</li>
</ol>
{{Admon/tip|Virtual Machine Fails to Shutdown.| You should shut down the VM normally as you would shutdown any operating system. If your VM does NOT shutdown normally, you can select from the Virtual Machine Manager window: '''Virtual Machine''' -> '''Shutdown''' -> '''Force Off'''.|
}}
<ol>
</ol>
<ol>
<li value="1528">Enable SSH access to your virtual machine with these commands (semi-colon allows commands to be run in sequence):<br /> <code>service '''systemctl start sshd start; chkconfig systemctl enable sshd on.service'''</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 the your host (your main Fedora installationf19host): <code>'''ssh ''IPaddressfedora1_IP_address'''''</code> (determined from step 27 above)</li>
</ol>
* '''Boot media:''' Network installation
* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/19/Fedora/x86_64/os/
* '''Memory:''' 768MB1024MB* '''Disk space:''' 15GB20GB
* '''CPUs:''' 1
# Create the VM (called '''fedora2''') as you did with the ''fedora1'' virtual machine, except:
#* In '''step 1 of 5''', set the installation type to '''Network Install (HTTP, FTP, or NFS)'''.
#* In '''step 2 of 5''', provide the location of the software source by providing the URL http://belmont.senecac.on.ca/fedora/releases/19/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 2 3 of 5''', set select the appropriate RAM.#* In '''OS Typestep 4 of 5''' , set the hard-drive space to '''Linux20GB'''(<u>NOT</u> 15 GB!)#* In '' and 'step 5 of 5'Version'' to , review the settings, and click '''Fedora 19Finish'''. # 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 Complete the '''Installation Summary''' sections (Date and Time, Installation Destinatation) like you get to did in the fedora1 install, except in 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 problemAllow the installation program to automatically create the partitions, then click yes but we will be making changes to proceedthe partition sizes. # On the next screen, change the logical volumes as follows:#* Reduce Select the logical volume (partition) '''root''' (i.e. '''/''' ), and reduce the size of the root LV to '''8000 MB10 GB''', then click '''Update Settings'''.#* Click the '''plus sign''' (i.e. '''Add +''') to <u>add</u> a logical volume with a size of 2000 MB and a mountpoint of called '''/home''' (you can name it whatever you want, and use with a size of '''ext42 GB''' . Note that you can make changes to other items (such as the file-system typelike ext4), but you are not required to do this for this lab.# On Review your changes, click '''Done''', click '''Accept Changes''' to return to the software selection screen, select '''Graphical DesktopInstallation Summary'''.# Make certain that Software Selection is set to '''Gnome Desktop'''On .# Complete the same screeninstallation, select the "Fedora 19 - x86_64" and the "Fedora 19 - x86_64 - Updates". Leave "Installation Repo" selected. set a ''root password'DO NOT'and at least ' enable the "Test Updates" repository'one regular user''account.# Complete Click '''Reboot''' to restart the system. Note: be patient for the installationreboot 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.'''
* '''Boot media:''' Network installation
* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/19/Fedora/x86_64/os/
* '''Kickstart location:''' http://wwwmatrix.drivehqsenecac.com/fileon.ca/df~murray.aspx/shareID10606286/fileID1269952040saul/Fedora19murray-kickstart.cfg* '''Memory:''' 768MB1024MB* '''Disk space:''' 10GB15GB
* '''CPUs:''' 1
==== Steps ====
# Create the VM as you did with the ''<u>'''fedora2'' virtual machine, specifying a network install as before, except:'</u>'' Virtual Machine.#* In '''step 2 of 5''', after entering use the same URL for the installation source, click on ''Installation Source''. Click to expand the '''URL Options''' control.#* Enter and enter the '''Kickstart ''' URL: http://wwwmatrix.senecac.drivehqon.com/fileca/df~murray.aspx/shareID10606286/fileID1269952040saul/Fedora19murray-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 <u>determine</u> search for this pattern a couple of times). Determine the '''root password ''' as well as the name '''regular username 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.'''
# Start the ''fedora1'' virtual machine, and stop the ''fedora2'' and ''fedora3'' virtual machines.
# Switch to the f19host machine, and open a shell terminal.# Enter these commands into your host f19host machine and note the result:#* <code>'''virsh list'''</code>#* <code>'''virsh list --all'''</code>#* <code>'''virsh list --inactive'''</code># Start Now, shut-down your fedora1 VM normally, and close the fedora1 VM window. Make certain NOT to close the ''fedora3'' virtual machine from Virtual Machine Manager main window.# Switch to your terminal and issue the command line: <code>'''virsh start fedora3fedora1'''</code># Repeat the commands from step 2 and notice any changesCheck to see if your fedora1 VM is now running.# Stop Switch to the terminal and issue the ''fedora3'' virtual machinecommand: <code>'''virsh shutdown fedora3list --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!|}}
'''Answer the Investigation 5 observations / questions in your lab log book.'''
# 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="4">Compare the size of the compressed and original files.</li>
<li>Start the '''''fedora3''''' VM.</li> <li>'''Make certain that you are in your fedora VM, and <u>not</u> in your Fedora main system.!'''</li> <li>Wreck <u>only</u> your fedora 3 system! Try this command inside the fedora3 virtual machine ('''DO NOT''' do this on your main Fedora system, or you will have to repeat your '''lab1''' and portions of your '''lab2'''!): <code>'''rm -rf /*'''</code></li> <li>Shut down the VM.If you tried to start the Fedora3 VM, it would not boot since all system files have been removed!</li> <li>Restore the original image from the backup in your home directory (type by typing this command carefully): <code>'''gunzip <~'''YourUserId'''/fedora3.img.backup.gz >fedora3.img'''</code></li>
<li>Restart the VM. Is it working normally?</li>
<li>Create compressed backups of your other virtual machines.</li>
<ol>
<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''''', 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 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?
