Changes

OPS245 Lab 2

1 byte removed, 19:01, 17 January 2021

m

→‎Part 1: Backing Up Virtual Machines: - clarifying instructions.

[http://wiki.centos.org/HowTos/KVM Installing & Using KVM on CentOS ]

[http://www.dedoimedo.com/computers/kvm-intro.html Using KVM (tutorial)]

[https://~~www.centos~~libvirt.org/~~docs~~sources/5virshcmdref/html-single/~~5.2/Virtualization/sect-Virtualization-Commands_for_Red_Hat_Virtualization-virsh_the_command_line_interface_tool_for_virtualization.html~~ virsh command reference ]

|valign="top" style="padding-left:20px;"|

Miscellaneous

# Launch the ''KVM virtual machine manager'' by clicking '''Applications''' -> '''System Tools''' -> '''Virtual Machine Manager'''.

# When prompted, enter your ~~'''root'''~~ password.

# Click the '''create a new VM icon''' located near the top left-corner of the application window.

# Select the '''Network Install''' option and click '''Forward'''.

#Repeat the steps as you did in the previous investigation ([https://wiki.cdot.senecacollege.ca/wiki/OPS235_Lab_2#Part_1:_Install_KVM_Virtualization_Application Investigation1 Part 1]) to '''stop and disable firewalld, install iptables-services, start and enable iptables''' for this newly-created VM.

# Repeat the steps as you did with c7host post-install to '''turn off SELinux''' (using the command 'vi' instead of 'vim') and perform a '''yum update'''.

# Issue the following command to obtain and record your ~~centos2~~ centos3 IPADDR in your lab2 logbook: <code>ip address show</code>

# Record the time taken to install, and compare this to the time taken by the previous installations in your lab2 logbook.

:::*Home: http://mirror.netflash.net/centos/7/os/x86_64/

:: '''Kickstart File URL (Kernel options): '''

:::* ~~Seneca Lab~~Home:''' ks=https://ict.senecacollege.ca/~~~ops235/labs/centos7-kickstart.cfg:::* Home:''' ks=https://ict.senecacollege~~peter.cacallaghan/~~~ops235~~ops245/labs/centos7-kickstart~~-ext~~.cfg

:: '''VM Image Pathname:''' /var/lib/libvirt/images/centos3.qcow2

:: '''Memory:''' 2048MB ('''IMPORTANT''' Do not use less than 2048MB during installation.)

# Create the VM (called '''centos3''')

# During the install, copy the network URL, then click the '''URL options''' to expand the '''kernel options''' input textbox. Type the following in the kernel options textbox: <ul><li>~~Seneca Lab:'''~~ ks=https://ict.senecacollege.ca/~~~ops235/labs/centos7-kickstart.cfg</li><li>'''Home:''' ks=https://ict~~peter.~~senecacollege.ca~~callaghan/~~~ops235~~ops245/labs/centos7-kickstart~~-ext~~.cfg</li></ul>

# Then click the '''forward''' button to proceed. Make certain to select the correct Memory Size and Disk Space size shown in the VM Details above

# Make certain to enter the name: '''centos3''', AND then select the option: '''Customize configuration before install''', and select '''Copy Host CPU Configuration''', click '''Apply''', and then click '''Begin Installation'''.

# Compare the experience to the first time you booted the other virtual machines.

# Repeat the steps as you did in the previous investigation ([https://wiki.cdot.senecacollege.ca/wiki/OPS235_Lab_2#Part_1:_Install_KVM_Virtualization_Application Investigation1 Part 1]) to '''stop and disable firewalld, install iptables-services, start and enable iptables''' for this newly-created VM.

# Repeat the steps as you did with c7host post-install to '''turn off SELinux''' and perform a '''yum update'''. :::You'll notice something when you go to set '''SElinux''' to '''permissive'''. The kickstart file already did that for you. It could even have performed the switch from firewalld to iptables for you (but it didn't).

# Issue the following command to obtain and record your centos2 IPADDR in your lab2 logbook: <code>ip address</code>

# Remember that centos3 is text-based interface only (no graphics). To recover from a blank screen, press a key (like the SPACE key) to return to the screen display.

# Shut down your '''centos1''', '''centos2''', and '''centos3''' VMs. For ''centos2'' and ''centos3'', which are CLI-only, you can issue the following command to shutdown: <code>sudo shutdown -h</code>. Please be patient, the VMs will shut down!

# In your '''c7host''' VM, open a new Terminal window.

# Use elevated privileges ~~ist~~ to list the size and names of files in<code>/var/lib/libvirt/images/</code><ul><li>What do these files contain?</li></ul>

# Use the command <code>sudo -i</code> and enter your password if prompted. You are now root until you use the command <code>exit</code> to return to your normal user account.

# Change to the images directory by issuing the following command: <code> cd /var/lib/libvirt/images/</code>. Note that you did not need to use sudo, as you are already using elevated permissions.

<li> '''Make certain that you are in your VM and not in your main system!''' </li>

<li> Wreck only your centos3 system! Try this command inside the centos3 virtual machine:<code>sudo rm -rf /*</code> (ignore error messages).</li>

<li> Shut down and restart the centos3 VM(you may need to use the '''Force Reset''' option to do so). It </lI><li> When the machine restarts it will not boot since all system files have been removed!</li><li> Use the '''Force Off''' option to turn centos3 back off.</li>

<li> Restore the original image from the backup from your home directory to your '''images''' directory by typing this command: <code>sudo gunzip < ~YourUserId/backups/centos3.qcow2.gz > /var/lib/libvirt/images/centos3.qcow2'''</code></li>

<li> Restart the VM. Is it working normally?</li>

Peter.callaghan

932

edits

CDOT Wiki β

Changes

OPS245 Lab 2

CDOT Wiki ^β