{{Admon/caution|THIS IS AN OLD VERSION OF THE LAB|'''This lab is under constructionan archived version.|Please do Do not print or do use this lab until it is finalizedin your 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 12 Live Image Guide]** [http://docs.fedoraproject.org/installation-quick-start-guide/f12/en-US/html/ Fedora 12 Installation Quick Start Guide]* Network Installation** [http://docs.fedoraproject.org/install-guide/f12/en-US/html/ Fedora 12 Installation Guide]*** [http://docs.fedoraproject.org/install-guide/f12/en-US/html/s1-steps-network-installs-x86.html Preparing for a Network Installation]*** [http://docs.fedoraproject.org/install-guide/f12/en-US/html/s1-begininstall-perform-nfs-x86.html Performing a Network Installation]* Kickstart Installation17 LIVE CD** [http://docs.fedoraproject.org/install-guide/f12/en-US/html/ Fedora 12 17 x86_64 Installation Guide]DVD*** [http://docs.fedoraproject.org/install-guide/f12/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/f12/en-US/html/ch-kickstart2.html Kickstart Installations]USB Memory Stick*** [http://docs.fedoraproject.org/install-guide/f12/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 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| |}

{{Admon/tip|Update your Fedora Installation|It's a good idea to ensure that your Fedora installation is fully updated before proceeding. You can update your system == Investigation 2: How do you install and remove software 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>}}RPM? ==

# Install Use 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 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'libvirtd'' that manages (for files beginning with the letter l like the VMs'''lynx''' package).## Tools to manage virtualization, including the You should see a file called: <code>virtlynx-manager2.8.7-8.fc17.x86_64.rpm</code> graphical tool and # Execute the following command: <code>virshrpm -i lynx-2.8.7-8.fc17.x86_64.rpm</code> # Issue an RPM query to check that lynx is installed. Record this commandin your lab log-line toolbook.## The actual virtual machines themselves.# Start Issue the virtualization servicefollowing command: <code>service libvirtd startrpm -e lynx</code># The firewall configuration Issue an RPM query to verify that lynx is altered by no longer installed. Record this command in your lab log-book.# Move to the addition of appropriate sub-directory for packages that begin with the virtualization softwareletter '''b'''. Restart the firewall so that these changes become active: <code>service iptables restart</code># Start the graphical tool by selecting the menu option Applications>System Tools>Virtual Machine Manager or by typing Issue the following command : <code>virtrpm -i BackupPC-manager3.2.1-7.fc17.x86_64.rpm</code>and note the result

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

==== Introduction ==Investigation 3: How do you install and remove software with ''yum''? ==

{{Admon/note|Internet Connection|In this investigation, order for yum to work you will install Fedora from your live disc, and observe require a connection to the differences between Internet. Establish this type of installation and connection by using the DVD installation previously performed.browser to log into SeneNET}}

* Name<ol> <li value="2">Issue the command: fedora1 <code>yum install BackupPC</code> and answer <code>y</code> to the question about installation. <ol type="a"> <li>Where did ''yum'' get the BackupPC software?</li>* Boot media <li>Why could ''yum'' install BackupPC when rpm couldn't?</li> </ol> </li> <li>Issue an RPM query to verify that BackupPC is installed. Record this command in your lab log-book.</li> <li>Issue the command: Fedora Live CD<code>yum remove BackupPC</code></li>* Installation source <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: Fedora Live CD<code>yum info cups</code></li></ol>::* Memory: 512MBBased on the result, do you think that cups is a useful package for your system? If not, try removing it.<ol>* Disk <li value="8">Unused and unneeded software can present a security risk and ties up disk space: 10GBneedlessly. 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>* CPUs: 1</ol>

# 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:# 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 12.<br />[[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 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''.<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. The video It's important to note that the VM can =Logical Volume Management (and often willIntroduction) 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 hostname, enter "fedora1", when prompted for the timezone, select ''America/Toronto'', and when asked about storage, select ''Use Entire Disk''. '''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># Confirm that you can ssh to your virtual machine from the host (your main Fedora installation): <code>ssh ''IPaddress''</code>=

=== Investigation 2: Installing from the Network =Check Current LVM Information Prior to Performing Investigations ==

{{Admon'''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 /tip|Authenticate hard disk partitions. '''Volume Groups''' are areas used to the network|The rest define '''Physical Volumes''' (i.e. hard disks, disk partitions, or other forms of this lab uses network accessstorage devices). Be sure '''Logical Volumes''' are then used to authenticate relate directories (mount points) to the network using your browser before proceedinga specific physical volume or for a "range" or "span" of physical volumes.}}

'''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 possible important for students to gain an understanding of LVM, and how to install Fedora entirely 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: [[Logical Volume Management]] At this point, having completed [[OPS235 Lab 2|Lab 2]] you should have roughly the following disk storage setup:<br />('''Note:''' These results are output from the network'''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. In this investigationBefore proceeding, check these values with your own system to see if you will install Fedora from a webserver are generally "on Seneca's LANthe right track".<br /><br />

* Name: fedora2 VG #PV #LV #SN Attr VSize VFree* Boot media: Network installation* Installation source: http://belmont.senecac.on vg_fedora1 1 2 0 wz--n- 9.ca/fedora/releases/12/Fedora/x86_64/os/* Memory: 512MB* Disk space: 10GB* CPUs: 150g 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: /dev/belmont.senecac.on.ca/fedora/releases/12/Fedora/x86_64/os/#* # 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 4000 MB.#* Add vda3 vg_fedora1 lvm2 a logical volume with a size of 1000 MB and a mountpoint of /home (you can name it whatever you want).# On the software selection screen, uncheck the box for ''Office and Productivity'' (as well as the other software choices).# On the same screen, select the "Fedora 12 - x86_64" and the "Fedora 12 - x86_64 - Updates". ''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.50g 0

When Fedora is installed using the techniques you have used so far, the user is asked a number of questions VG #PV #LV #SN Attr VSize VFree vg_fedora2 1 3 0 wz--n- 14. 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'' file50g 3.25g

In this investigation, PV VG Fmt Attr PSize PFree /dev/vda3 vg_fedora2 lvm2 a kickstart file is provided for you-- 14. You can also create or modify a kickstart file using a regular text editor or a graphical tool50g 3.25g

* Name'''fedora3 (Note: fedora3 This VM has no GUI installed)'''* Boot media: Network installation * Installation source: http://belmont.senecac.on.ca/fedora/releases/12/Fedora/x86_64/os/ VG #PV #LV #SN Attr VSize VFree* Kickstart location: http://zenit.senecac.on.ca/~chris.tyler/fedora3 vg_fedora3 1 3 0 wz--n-ks9.cfg* Memory: 512MB* Disk space: 10GB* CPUs: 151g 0

==== Steps ==== PV VG Fmt Attr PSize PFree# 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: /dev/zenit.senecac.on.ca/~chris.tyler/fedora3vda3 vg_fedora3 lvm2 a--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 determine the root password as well as the name and password for the first user account.# Boot the virtual machine and log in. Compare the experience to booting the other virtual machines 9.51g 0

# In each VM, run Does not use LVM. Confirm this command: <code>yum update</code># Record using 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?same commands used above.

=== Investigation 54: Managing Virtual Machines from Extend the Command Line =size of lv_root using command-line tools ==

# Start the ''fedora1'' virtual machine, and stop the ''fedora2'' and ''fedora3'' virtual machines.# Enter these commands and note the result:#* <code>virsh list</code>#* <code>virsh list --all</code>#* <code>virsh list --inactive</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.# Stop the ''fedora3'' virtual machine: <code>virsh shutdown fedora3</code># Confirm that ''fedora3'' has been shut down.# Execute Perform this command: <code>virsh dumpxml fedora3 >fedora3.xml</code># Examine the file <code>fedora3.xml</code>. What does it contain? What format is it in?# Edit the file fedora3.xml, making the following changes:#* Change the name to <code>fedora3a</code>#* Change at least one of the hexadecimal characters investigation in the UUID. Do not change the length of the UUID. Valid hexadecimal characters are 0-9 and a-f.# Issue this command: <code>virsh define fedora3.xml</code># Issue the command <code>virsh list --all</code> and record any changes.# Issue the command: <code>virsh undefine fedora3a</code># List all of the virtual machines again, and note any changes.

=== Investigation 6: How do I backup Let's say that you have run out of disk space on your computer (fedora3), you need more space on the root filesystem, perhaps to host more webpages or a virtual machinelarger database or new software. What are your options? ===Getting a replacement harddrive would probably require reinstallation of the operating system and backup/restore of the data.

# Shut down all of the virtual machinesBecause we're using LVM though - we can avoid that.# 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 We can add a compressed 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 new harddrive (DO NOT do this on your main Fedora system!which will serve as a physical volume): <code>rm -rf /</code># Shut down the VM.# Restore the original image from backup: <code>gunzip <fedora3.img.backup.gz >fedora3.img</code># Restart to 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 machinevolume group, what information should be saved in addition to and extend the virtual machine image?# Write the answer root logical volume to make use of the Investigation 6 question in your lab booknew available space.

=== Investigation 7'''Perform the following operations to increase the size of lv_root in fedora3: Kickstart Files ==='''

When you perform a non-Kickstart installation, the installation program creates a Kickstart file in the <codeu>'''<font>Steps:</rootfont>'''</codeu> directory for reference.

# Obtain <ol> <li>Run the kickstart files for all four following commands and make note of your installations (your disk pack, plus the ''fedora1'', ''fedora2'', and ''output:</li> <code>ls /dev/vd* pvs vgs lvs df -h</code> <li>Open the fedora3'' virtual machines).machine console</li># Compare these files. What are <li>Go to the differences? Similarities? (Tip: you may want to use tools such as hardware details view</li> <codeli>sdiffClick "Add Hardware" and add a new storage device of 2GBs, make sure it's a VirtIO disk.</codeli> <li> Go back to help with the comparison).console view</li># How could you use <li>Run the kickstart file produced by same ls command now, what's changed?</li> <li>Now we'll make the installation program new device as a physical volume, add it to perform additionalthe volume group, identical installations?and extend lv_root:</li> <code>pvcreate /dev/vdb

# lvextend -l +100%FREE -r vg_fedora3/lv_root</code> <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></ol> '''Answer the name Investigation 4 observations / questions in your lab log book.''' == Investigation 5: How are LVMs managed using system-config-lvm? == '''Perform this investigation on the VM named ''<u>fedora2</u>''.'''[[Image:Ops235_lab4_1.png|thumb|right|Screenshot of the system-config-lvm in Fedora installation program?. Click to enlarge.]]# Let's learn to administer (manage) our LVM graphically for our '''Fedora2''' Virtual Machine.<br />Fedora provides a tool called <code>system-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>yum install system-config-lvm</code>).<ol> <li value="2">Use this tool to determine the current LVM configuration by clicking on the appropriate element and reading the properties in the right-hand panel -- write down the answers: <ol type="a"> <li>What are the advantages names and disadvantages sizes of each type of installationthe '''PV'''s?</li># Which type <li>What is the name and size of installation works best for confirming compatibility with hardware before installation? Whythe '''VG'''?</li># Which type <li>What are the names and sizes of installation works best for installing large numbers of computersthe '''LV'''s? Why</li> <li>Is there any space in the VG which is not allocated to a LV?</li># What factors affect installation time? </ol> </li># How can you reduce <li>Increase the number size of software updates required immediately after installation?the home file-system to '''2 GB''': <ol type="a"> <li>Click on the LV containing the '''home''' filesystem.</li> <li>Click on ''Edit Properties''.</li> <li>Change the size to '''2 GB''' and click ''Ok''.</li> </ol> <li>Create a '''new 2G LV''' (LV Properties: linear) containing an ext4 filesystem named lv_archive and mount it at '''/archive''' <ol type="a"> <li>Click on ''Logical View''.</li> <li>Click the ''Create New Logical Volume''.</li> <li>Set the name, size, filesystem, and mount point.</li> <li>Click ''Ok''.</li> </ol> <li>Backup <code>'''/etc'''</code> into <code>'''/archive'''</code></li># Why would you enable additional repositories during installation?</ol># Where does ::* Copy the files in /etc into the file filesystem mounted at <code>/rootarchive</code><br /anaconda>(use the graphical tools or the command line. If using cp, remember to use the -ksR option).cfg<ol> <li value="6">Shrink the size of <code>lv_archive</code> contain, and how is it createdto '''1 GB'''.</li> <li>Try shrinking the home file-system. What happens? Why?</li></ol> '''Answer the Investigation 5 observations / questions in your lab log book.'''# How do = Updated backup instructions = If you completed this lab correctly - please make sure you start and stop are still making full backups of your virtual machines. Remember adding a new harddrive to fedora3?You will need to back up that drive as well. If you don't - you will only have half of your machine backed up, which is of no use for a recovery. = Completing the lab =# How do {{Admon/important|Time for a new backup!|If you SSH into have successfully completed this lab, make a new backup of your virtual machines?.}} '''Notes:'''# rpm command options# yum command options# How to use pvs/vgs/lvs/df/pvcreate/vgextend/lvextend# Answer to this question "What is the purpose license of the nautilus package?" '''Arrange evidence for each of these items on your screen, then ask your instructor to review them and relationship between these pieces sign off on the lab's completion:'''# nled installed on the host (disk pack - main system f16host).# Unnecessary/unused packages have been deleted (list at least 4, and show that they are no longer installed).# Fresh backup of softwarethe virtual machines. = Preparing for Quizzes = # What is a VG? PV? LV?#* libvirtWhat commands are used to determine VG / PV / LV information?# What does yum do that rpm does not?#* libvirtdList the steps to install a package via rpm command.#* virshList the steps to determine detailed information regarding an install package.#* virt-managerList the steps to remove a package via rpm command.#* virt-List the steps to installa package using the yum command.#* vncviewerList the steps to remove a package using the yum command.# What is the total size of the "main" VG on your system?# How do you create a LV?# How do you delete an LV?#* kvmHow would you increase the size of the root filesystem by 50 MB?