[[Category:OPS235]][[Category:OPS235 Labs]]{{Admon/importantcaution|Unbind your MAC addressTHIS IS AN OLD VERSION OF THE LAB|Before proceeding with '''This is an archived version. Do not use this lab, [[Unbinding MAC Addresses on Fedora|unbind in your MAC address]]OPS235 course.'''}}=Logical Volume Management and Software Package Management=

== Objectives Introduction==

Installation Methods* Live Image Installation** [http://docs.fedoraproject.org/readme-live-image/en-US.html Fedora 13 Live Image Guide]** [http://docs.fedoraproject.org/installation-quick-start-guide/f13/en-US/html/ Fedora 13 Installation Quick Start Guide]* Network Installation** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/ Fedora 13 Installation Guide]*** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/s1-steps-network-installs-x86.html Preparing for a Network Installation]*** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/s1-begininstall-perform-nfs-x86.html Performing a Network Installation]* Kickstart Installation17 LIVE CD** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/ Fedora 13 17 x86_64 Installation Guide]DVD*** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/sn-automating-installation.html Automating the Installation with Kickstart]SATA Hard Disk (in removable disk tray)*** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/ch-kickstart2.html Kickstart Installations]USB Memory Stick*** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/ch-redhat-config-kickstart.html Kickstart Configurator]Lab Logbook

== Required Materials Prerequisites==

* Removable disk pack with Fedora installed (see Completion and Instructor "Sign-off" of Lab 2: [[OPS235 Lab 2|Lab 2]]).* Fedora 13 x86_64 Live CD.

{{Admon/note|Performing this Lab off the Seneca network|This lab uses servers which are on the Seneca network and which are not available from other locations ==Linux Command Online Reference==Each Link below displays online manpages for each command (such as your home). If you attempt this lab from another location, adjust the belmont.senecac.on.ca URLs to point to another via [http://mirrorslinuxmanpages.fedoraprojectcom/ http://linuxmanpages.org/publiclist Fedora mirror servercom] -- note that you may need to change the directory name as well as the server name.}}):

{|width="100%" cellpadding= Introduction ="5"|'''LVM Information Utilities:'''|'''LVM Management Utilities:'''|'''Additional Utilities:'''|- valign="top"|*[http://linuxmanpages.com/man8/vgs.8.php vgs]*[http://linuxmanpages.com/man8/lvs.8.php lvs]*[http://linuxmanpages.com/man8/pvs.8.php pvs]*[http://linuxmanpages.com/man8/vgdisplay.8.php vgdisplay]*[http://linuxmanpages.com/man8/lvdisplay.8.php lvdisplay]*[http://linuxmanpages.com/man8/pvdisplay.8.php pvdisplay]|*[http://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-system-config-lvm.html system-config-lvm] (Tutorial)*[http://linuxmanpages.com/man8/lvextend.8.php lvextend]*[http://linuxmanpages.com/man8/resize2fs.8.php resize2fs]*[http://linuxmanpages.com/man8/lvcreate.8.php lvcreate]*[http://linuxmanpages.com/man8/lvreduce.8.php lvreduce]*[http://linuxmanpages.com/man8/pvcreate.8.php pvcreate]*[http://linuxmanpages.com/man8/vgextend.8.php vgextend]|*[http://linuxmanpages.com/man8/mount.8.php mount]*[http://linuxmanpages.com/man8/umount.8.php umount]*[http://linuxmanpages.com/man8/yum.8.php yum]*[http://linuxmanpages.com/man8/rpm.8.php rpm]|}

A ==Resources on the web==Additional links to tutorials and HOWTOs:'''Please read this page to get an overview of LVM:''virtual machine'<br /><br />:* [[Logical Volume Management]] (' ''Note:''' It is recommended to return to this guide as a software simulation of a computer which can be used as though it were actual hardwarereference when performing the next several investigations):* [http://fedoranews.org/alex/tutorial/rpm/ Using the RPM Utility]:* [http://www. It's possible to run multiple virtual machines on one computer, reducing hardware requirements and introducing flexibilitycentos. Some common uses of virtualization include:org/docs/5/html/yum/ Using the YUM Utility]

* = 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.Package Management =

In this lab, == Investigation 1: How do 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 machines.query the RPM database? ==

You have already used RPM maintains a Fedora live disc and an installation discdatabase of installed software. This information is very useful to system administrators. In both casesLab 3, you queried that database using RPM with the -q argument. When you query the boot media (which RPM database, you can separately specify::* Which packages you used want to load the installation software) and the installation source do an <u>operational task</u> (where the software that got installed came fromlike installing or removing a package) were the same, using a '''select-option''': they CD* What <u>information</DVD provided both. Howeveru> you want about those packages, the Fedora (and most other Linux distributions) permits you to use any combination of boot media and installation media:using a '''query-option'''

{|width="100%" border= Instructions "1" cellpadding="5"|-!Option!Meaning!Select or query option?!Example command|-| -a|Select all packages|select-option| |-| -l| | | |-| -i|Show the package information.| | |-| -f filename| | | |-|packagename|Select just this package|select-option| |} '''Answer the Investigation 1 observations / table contents in your lab log book.''' == Investigation 2: How do you install and remove software with RPM? == # Use the graphical file manager (Nautilus) to change to the directory on your Installation DVD. Go to the sub-directory called '''Packages''' and then go to the sub-directory '''l''' (for files beginning with the letter l like the '''lynx''' package). You should see a file called: <code>lynx-2.8.7-8.fc17.x86_64.rpm</code># Execute the following command: <code>rpm -i lynx-2.8.7-8.fc17.x86_64.rpm</code># Issue an RPM query to check that lynx is installed. Record this command in your lab log-book.# Issue the following command: <code>rpm -e lynx</code># Issue an RPM query to verify that lynx is no longer installed. Record this command in your lab log-book.# Move to the appropriate sub-directory for packages that begin with the letter '''b'''.# Issue the following command: <code>rpm -i BackupPC-3.2.1-7.fc17.x86_64.rpm</code> and note the result

{{Admon/tip|Update your Fedora Installation|It== Investigation 3: How do you install and remove software with ''s a good idea to ensure that your Fedora installation is fully updated before proceeding. You can update your system with the graphical tool located on the menu at >System>Administration>Software Update (or type the command <code>gpk-update-view</code>), or by typing either of these commands: <code>pkcon update</code> or <code>yum update</code>}}''? ==

# Install the Fedora virtualization software: <code>{{Admon/note|Internet Connection|In order for 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.## 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.# Start the virtualization service: <code>service libvirtd start</code># The firewall configuration is altered by work you require a connection to the addition of the virtualization softwareInternet. Restart the firewall so that these changes become active: <code>service iptables restart</code># Start the graphical tool Establish this connection by selecting using the menu option Applications>System Tools>Virtual Machine Manager or by typing the command <code>virt-manager</code>browser to log into SeneNET}}

{{Admon/important|Run virt-manager as a regular user|Running virt-manager as root may not work due # Change to configuration issuesyour home directory.}}

{{Admon<ol> <li value="2">Issue the command: <code>yum install BackupPC</caution|Reboot your fedora host|There appears code> and answer <code>y</code> to be an issue with supplying your VM's with a dynamic IP unless the host is restarted after installing question about installation. <ol type="Virtualizationa". > <li>Where did ''yum'' get the BackupPC software?</li> <li>Why could ''yum''install BackupPC when rpm couldn'Reboot now t?</li> </ol> </li> <li>Issue an RPM query to avoid verify that BackupPC is installed. Record this problemcommand in your lab log-book.</li> <li>Issue the command: <code>yum remove BackupPC</code></li> <li>Issue an RPM query to verify that BackupPC is no longer installed. Record this command in your lab log-book.</li> <li>Install <code>nled</code> using '''yum''}}'. Record this command in your lab log-book.</li> <li>Issue this command: <code>yum info cups</code></li></ol>::* Based on the result, do you think that cups is a useful package for your system? If not, try removing it.<ol> <li value="8">Unused and unneeded software can present a security risk and ties up disk space needlessly. Find at least 4 other packages that you're not using on your system, and remove them. Be careful to ensure that removing those packages does not also remove other software that you do need.</li></ol>

=== '''Answer the Investigation 1: Installing from a Live Disc ===3 observations / questions in your lab log book.'''

==== Introduction ==Check Current LVM Information Prior to Performing Investigations ==

In this investigation'''LVM''' ('''Logical Volume Management''') is used to manage hard disk drives / partitions for Unix/Linux systems. LVM provides more flexibility than just working with hard disks / hard disk partitions. '''Volume Groups''' are areas used to define '''Physical Volumes''' (i.e. hard disks, you will install Fedora from your live discdisk partitions, and observe the differences between this type or other forms of installation and the DVD installation previously performedstorage devices). '''Logical Volumes''' are then used to relate directories (mount points) to a specific physical volume or for a "range" or "span" of physical volumes.

* Name'''Although the concept of LVM is simple, it takes practice and preparation (or "thinking ahead") in order to correctly use this valuable tool'''. It is important for students to gain an understanding of LVM, and how to manage their file-systems using LVM. It is recommended for students to read the following resource prior to this lab and/or return to the following resource while performing this lab: fedora1[[Logical Volume Management]]* Boot media: Fedora Live CD* Installation source: Fedora Live CD* Memory: 512MB * Disk spaceAt this point, having completed [[OPS235 Lab 2|Lab 2]] you should have roughly the following disk storage setup: 10GB<br />* CPUs('''Note: 1''' These results are output from the '''vgs''', '''lvs''', and '''pvs''' commands that provide volume group, physical volume and logical volume information for each of the virtual machines that you created in lab2. Before proceeding, check these values with your own system to see if you are generally "on the right track".<br /><br />

{{Admon/note|Fedora 12 Screen Shots|The following screen shots are from Fedora 12. The Fedora 13 version of virt VG #PV #LV #SN Attr VSize VFree vg_fedora1 1 2 0 wz-manager varies slightly -n- there are a few extra controls on some dialogs which may be ignored9.}}50g 0

# In the Virtual Machine Manger, click on the icon to ''Create a Virtual Machine'' in the upper-left corner: <br />[[Image:Virt-manager1.png]]# A window will appear with the title ''New VM''. There are five steps to be completed; click Forward after each step: PV VG Fmt Attr PSize PFree# Step 1 of 5: Enter the virtual machine name and select ''Local install media''.<br />[[Image:Virt-manager2.png]]# 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 it as the install media. Set the ''OS type'' to Linux and the ''Version'' to Fedora 13.<br dev/>[[Image:Virt-manager3.png]]<!-- {{Admon/tip|Using an ISO image|Instead of using a physical CD or DVD, you can use an ISO image of vda3 vg_fedora1 lvm2 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 512 MB and the number of CPUs to 1.<br />[[Image:Virt-manager4.png]]# 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'' 9.<br />[[Image:Virt-manager5.png]]# 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''.<br />[[Image:Virt-manager6.png]]# The virtual machine will now start. You will see a window which displays the virtual video card from the VM. It's important to note that the VM can (and often will) run even when this display is not present. 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.# Login to the VM and double-click on the ''Install to Hard Drive'' icon. The installation program, similar to the one used when installing Fedora in Lab 2, will appear. You will get a warning at one point during the installation process that the disk "may need to be re-initialized" -- this is simply a warning that the virtual disk is completely blank, and it is safe to select ''Re-initialize drive''.# During the installation process, when prompted for the drive, select "Virtio Block Device", when prompted for the hostname, enter "fedora1", when prompted for the timezone, select ''America/Toronto'', 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.# When the installation is complete, select the menu option System>Shutdown to stop the Live Disc.# Start the VM from its disk image 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.# Login using the new user account.# Enable SSH access to your virtual machine with these commands: <code>service sshd start; chkconfig sshd on</code># Find out the IP address of your virtual machine: <code>ifconfig eth0</code># Enter the following command on your virtual machine to create a firewall exception to allow ssh traffic into the machine: <code>iptables -I INPUT -p tcp -s0/50g 0 -d0/0 --dport 22 -j ACCEPT</code># Confirm that you can ssh to your virtual machine from the host (your main Fedora installation): <code>ssh ''IPaddress''</code>

It is possible to install Fedora entirely from the network PV VG Fmt Attr PSize PFree /dev/vda3 vg_fedora2 lvm2 a-- 14. In this investigation, you will install Fedora from a webserver on Seneca's LAN50g 3.25g

* Name'''fedora3 (Note: fedora2 This VM has no GUI installed)'''* Boot media: Network installation* Installation source: http://belmont.senecac.on.ca/fedora/releases/13/Fedora/x86_64/os/* Memory: 512MB * Disk space: 15GB VG #PV #LV #SN Attr VSize VFree* CPUs: vg_fedora3 1 3 0 wz--n- 9.51g 0

==== Steps ==== PV VG Fmt Attr PSize PFree# Create the VM 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 URL http://belmont.senecac.on.ca/fedora/releases/13 /Fedoradev/x86_64/os/#* In step 2 of 5, set the ''OS Type'' to "Linux" and ''Version'' to "Fedora 13" # Observe the boot process. How is it different from booting from an optical disc (CD/DVD)?# Start the installation process. When you get to the disk partitioning step, enable the checkbox labelled ''Review and modify partition layout''. On the next screen, change the logical volumes as follows:#* Reduce the size of the root LV to 8000 MB.#* Add vda3 vg_fedora3 lvm2 a logical volume with a size of 2000 MB and a mountpoint of /home (you can name it whatever you want, and use ext3 or ext4 as the filesystem type).# On the software selection screen, select ''Graphical Desktop''.# On the same screen, select the "Fedora 13 - x86_64" and the "Fedora 13 - 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 9.51g 0

When Fedora is installed using the techniques {{Admon/note|VM Backups and Recovery|Most of these investigations will take place in your virtual machines. If you have used so farmake a significant mistake, the user is asked a number your virtual machine may not boot. Remember that you created backups of questions. In some situationsyour virtual machines in Lab 2, it is better to provide the answers to these questions in a file rather than answer and you can restore them individuallyif something goes wrong. This type <br /><br />'''Remember: if you did not create backups for all of file is called a your VMs, then you don't have any restoration points to fall-back to!'kickstart'' file.|}}

In this investigation, a kickstart file is provided for you. You can also create or modify a kickstart file == Investigation 4: Extend the size of lv_root using a regular text editor or a graphical tool.command-line tools ==

* Name: Let's say that you have run out of disk space on your computer (fedora3* Boot media: Network installation* Installation source: http://belmont.senecac.), you need more space onthe root filesystem, perhaps to host more webpages or a larger database or new software.ca/fedora/releases/13What are your options? Getting a replacement harddrive would probably require reinstallation of the operating system and backup/Fedora/x86_64/os/* Kickstart location: http://zenit.senecacrestore of the data.on.ca/~chris.tyler/fedora13-vda-ks.cfg* Memory: 512MB* Disk space: 10GB* CPUs: 1

==== Steps ====# Create the VM as you did with the Because we''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/fedora13-vdare using LVM though -kswe can avoid that.cfg # Observe the installation. How is it different from booting from an optical disc We can add a new harddrive (CD/DVDwhich will serve as a physical volume)?# Complete the installation. Record to the time taken to installvolume group, and compare this to extend 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) root logical volume to determine the root password as well as the name and password for the first user account.# Boot the virtual machine and log in (make use of the user ID and password information from the previous step). Compare the experience to the first time you booted the other virtual machinesnew available space.

=== Investigation 4'''Perform the following operations to increase the size of lv_root in fedora3: Updating and Comparing the VMs ==='''

# In each VM, run this command<u>'''<font>Steps: <code/font>yum update'''</codeu># 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 <ol> <li>Run the following tablecommands and make note of the output:</li> <code>ls /dev/vd* pvs vgs lvs df -h</code> <li>Open the fedora3 virtual machine console</li> <li>Go to the hardware details view</li> <li>Click "Add Hardware" and add a new storage device of 2GBs, make sure it's a VirtIO disk.</li> <li>Go back to the console view</li> <li>Run the same ls command now, what's changed?</li> <li>Now we'll make the new device as a physical volume, add it to the volume group, and extend lv_root:</li> <code>pvcreate /dev/vdb

{|border="1" width="100%"|- vgextend vg_fedora3 /dev/vdb! ||f13host||fedora1||fedora2||fedora3| lvextend -|'''Installation Method'''||Installation Disc||Live Disc||Network Installation||Network Installation l + Kickstart|100%FREE -r vg_fedora3/lv_root</code>|'''Packages Installed'''|| || || || || <li>Now rerun the ls/pvs/vgs/lvs/df commands. What has changed and what caused those changes?</li>| <li>Among the changes, note that your root filesystem is now 2GB bigger -and you have not even rebooted your machine!</li>|'''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...'''|| || || || |||}</ol>

=== '''Answer the Investigation 5: Managing Virtual Machines from the Command Line ===4 observations / questions in your lab log book.'''

# Start the ''fedora1'' virtual machine, and stop Perform this investigation on the VM named ''<u>fedora2</u>'' and '.'fedora3'' virtual machines.# Enter these commands and note the result[[Image:Ops235_lab4_1.png|thumb|right|Screenshot of system-config-lvm in Fedora. Click to enlarge.]]#* Let's learn to administer (manage) our LVM graphically for our '''Fedora2''' Virtual Machine.<br />Fedora provides a tool called <code>virsh listsystem-config-lvm</code>#* to graphically administer LVM. It will appear on the menu as '''Application'''>'''Other'''>'''Logical Volume Management'''. The package may not be installed by default, so you will need to install it by issuing: (<code>virsh list yum install system-config-alllvm</code>).#* <codeol> <li value="2">virsh list Use this tool to determine the current LVM configuration by clicking on the appropriate element and reading the properties in the right-hand panel --inactivewrite down the answers: <ol type="a"> <li>What are the names and sizes of the '''PV'''s?</codeli> <li>What is the name and size of the '''VG'''?</li># Start <li>What are the names and sizes of the ''fedora3'LV''' virtual machine from s?</li> <li>Is there any space in the command line: VG which is not allocated to a LV?</li> <code/ol>virsh start fedora3 </codeli># Repeat <li>Increase the size of the commands from step home file-system to '''2 and notice any changes.GB''': <ol type="a"># Stop <li>Click on the LV containing the ''fedora3'home''' virtual machine: filesystem.</li> <codeli>virsh shutdown fedora3Click on ''Edit Properties''.</codeli># Confirm that <li>Change the size to '''2 GB''' and click ''fedora3Ok'' has been shut down.</li># Execute this command </ol> <li>Create a '''new 2G LV''' (LV Properties: linear) containing an ext4 filesystem named lv_archive and mount it at '''/archive''' <codeol type="a">virsh dumpxml fedora3 <li>fedora3Click on ''Logical View''.xml</codeli># Examine <li>Click the file ''Create New Logical Volume''.</li> <codeli>fedora3Set the name, size, filesystem, and mount point.xml</codeli> <li>Click ''Ok''. What does it contain? What format is it in?</li># Edit the file fedora3.xml, making the following changes: </ol>#* Change the name to <li>Backup <code>'''/etc'''</code>fedora3ainto <code>'''/archive'''</code></li></ol>#::* Change at least one of Copy the hexadecimal characters files in /etc into the UUID. Do not change filesystem mounted at <code>/archive</code><br />(use the length of graphical tools or the UUIDcommand line. Valid hexadecimal characters are 0-9 and aIf using cp, remember to use the -fR option).# Issue this command: <codeol>virsh define fedora3.xml </codeli value="6"># Issue Shrink the command size of <code>virsh list --alllv_archive</code> and record any changesto '''1 GB'''.</li># Issue <li>Try shrinking the command: home file-system. What happens? Why?<code/li>virsh undefine fedora3a</codeol># List all of the virtual machines again, and note any changes.

=== '''Answer the Investigation 6: How do I backup a virtual machine? ===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 = Updated backup of the <code>fedora3.img</code> file with this command: <code>gzip <fedora3.img >fedora3.img.backup.gz</code># Compare the size of the compressed and original files.# Start the ''fedora3'' VM.# Wreck it! Try this command inside the fedora3 virtual machine (DO NOT do this on your main Fedora system!): <code>rm -rf /*</code># Shut down the VM.# Restore the original image from backup: <code>gunzip <fedora3.img.backup.gz >fedora3.img</code># Restart the VM. Is it working normally?# Create compressed backups of your other virtual machines.# 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?# Write the answer to the Investigation 6 question in your lab book.instructions =

When Remember adding a new harddrive to fedora3? You will need to back up that drive as well. If you perform a nondon't -Kickstart installationyou will only have half of your machine backed up, the installation program creates which is of no use for a Kickstart file in the <code>/root</code> directory for referencerecovery.

# Obtain = Completing the kickstart files for all four of your installations (your disk pack, plus the ''fedora1'', ''fedora2'', and ''fedora3'' virtual machines).# 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?lab =

{{Admon'''Notes:'''# rpm command options# yum command options# How to use pvs/vgs/important | Important! | Arrange evidence of each lvs/df/pvcreate/vgextend/lvextend# Answer to this question "What is the license of the following items on the screen, and then ask your professor or lab monitor to check them:}}nautilus package?"

# Three working virtual machines created.'''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:'''# Four kickstart filesnled installed on the host (disk pack - main system f16host).# All virtual machines fully updatedUnnecessary/unused packages have been deleted (list at least 4, and show that they are no longer installed).# All Fresh backup of the virtual machines backed up.# Installation comparison table filled in.

== Preparing for the Quizzes ==

# What is the name of the Fedora installation programa VG? PV? LV?# Which factors recorded in your table (above) were due What commands are used to the type of installation performed, and which factors were due to the amount of software installeddetermine VG / PV / LV information?# Which type of installation works best for confirming compatibility with hardware before installation? WhyWhat does yum do that rpm does not?# Which type of installation works best for installing large numbers of computers? Why?List the steps to install a package via rpm command.# What factors affect installation time?List the steps to determine detailed information regarding an install package.# How can you reduce List the number of software updates required immediately after installation?steps to remove a package via rpm command.# Why would you enable additional repositories during installation?List the steps to install a package using the yum command.# What does List the steps to remove a package using the file <code>/root/anaconda-ksyum command.cfg</code> contain, and how # What is it createdthe total size of the "main" VG on your system?# How do you start and stop virtual machinescreate a LV?# How do you SSH into your virtual machinesdelete an LV?# What is How would you increase the purpose size of and relationship between these pieces of softwarethe root filesystem by 50 MB?#* libvirt#* libvirtd#* virsh#* virt-manager#* virt-install#* vncviewer#* kvm