Changes

Jump to: navigation, search

OPS235 Lab 2 - CentOS6

1,327 bytes removed, 12:29, 24 September 2018
no edit summary
[[Category:OPS235]]
 {{Admon/caution|THIS IS AN OLD VERSION OF THE LAB|'''This is an archived version. Do not use this in your OPS235 course.'''}}
= CentOS Installation Methods (on Virtual Machines: centos1, centos2, centos3) =
 
== Preparing the Virtual Machine Manager ==
 
# Open a web-browser, and open the OPS235 Lab #2 WIKI. '''<br /><br />NOTE:''' You need to enter your "MySeneca" username and password to obtain a "wired" Internet connection (otherwise, you will not be able to perform the yum install command in the next step). Remember to perform a "wired-connection" (logging in with your MySeneca username and password via a web-browser) every time you boot-up your host machine...<br /><br />
# Install the virtualization software (virtualization, libvirt, virt-manager) using <code>yum install virtualization libvirt virt-manager</code> (and reply "y" to all of the prompts)
# The command you issued will install the following software:
:* kvm/qemu - the hypervisor and other hardware emulation systems.
:* A system service named libvirtd that manages the VMs.
:* A graphical tool for managing virtual machines and the virsh command-line tool.
<ol>
<li value="4">Start the virtualization service: <code>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>service iptables restart</code></li>
</ol>
<ol>
<li value="6">Start the graphical tool by selecting the menu options '''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, not as root|Otherwise all your virtual machines will be owned by root and you won't be able to use them as a regular user.}}
== Using the Virtual Machine Manager ==
<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 '''centos1''', and when prompted for the timezone, select '''Toronto - Eastern Time Ontario''', and when </li> <li>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>
<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 ignore the kdump out-of-memory warning). Make certain that the VM has a network interface connection (i.e. look at network applet on the top panel). Create a user with the same name as your Matrix account.</li>
<li>Login using the new user account.</li>
</ol>
#* Reduce the size of the root LV to '''8000 MB'''.
#* '''Add a <u>logical volume</u> 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'''.
# 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'''.
# Start the ''centos1'' virtual machine, and stop the ''centos2'' and ''centos3'' virtual machines.
# Switch to the c6host machine, and open a shell terminal.
# Enter these commands into your f19host c6host machine and note the result:
#* <code>'''virsh list'''</code>
#* <code>'''virsh list --all'''</code>
# Three working virtual machines created.
# Disk layout and size correct on all virtual machines
# Use virsh to list the status of all vms.
# Four kickstart files.

Navigation menu