JAI SHRIRAM ENGINEERING COLLEGE

AVINASHIPALAYAM, TIRUPUR-638 660.

DEPARTMENT OF ARTIFICIAL INTELLIGENCE AND DATASCIENCE

Regulation: 2021

LAB MANUAL

CCS372 VIRTUALIZATIONLABORATORY

III AI&DS/ VI SEM

Prepared By Approved By
Ms. B.REVATHI (AP/AD) Ms.P. Mallika (HOD / AD)
 JAI SHRIRAM ENGINEERING COLLEGE
TIRUPPUR – 638 660
Approved by AICTE, New Delhi & Affiliated to Anna University, Chennai
Recognized by UGC & Accredited by NAAC and NBA (CSE and ECE)

DEPARTMENT OF ARTIFICIAL INTELLIGENCE AND DATA SCIENCE

VISION AND MISSION

VISION
To impart quality education and create center of excellence in the field of
AI & DS to produce industry ready engineers

MISSION
M1: Developing professionals with sound understandings in AI.

M2: Enhancing employability and entrepreneurial skills in young minds and

create leaders to serve our society with ethical values
M3: Implementing cutting-edge teaching and practical learning techniques.
 JAI SHRIRAM ENGINEERING COLLEGE
TIRUPPUR – 638 660
Approved by AICTE, New Delhi & Affiliated to Anna University, Chennai
Recognized by UGC & Accredited by NAAC and NBA (CSE and ECE)

CCS372 VIRTUALIZATIONLABORATORY

SYLLABUS

PRACTICAL EXERCISES:

1. Create type 2 virtualization in VMWARE or any equivalent Open Source Tool. Allocate

memory and storage space as per requirement. Install Guest OS on that VMWARE.

2. a. Shrink and extend virtual disk

b. Create, Manage, Configure and schedule snapshots

c. Create Spanned, Mirrored and Striped volume

d. Create RAID 5 volume

3. a. Desktop Virtualization using VNC

b. Desktop Virtualization using Chrome Remote Desktop

4. Create type 2 virtualization on ESXI 6.5 server

5. Create a VLAN in CISCO packet tracer

6. Install KVM in Linux

7. Create Nested Virtual Machine (VM under another VM)

 JAI SHRIRAM ENGINEERING COLLEGE
TIRUPPUR – 638 660
Approved by AICTE, New Delhi & Affiliated to Anna University, Chennai
Recognized by UGC & Accredited by NAAC and NBA (CSE and ECE)

CCS372 VIRTUALIZATIONLABORATORY

Course Outcome

C314.1 Analyze the virtualization concepts and Hypervisor

C314.2 Apply the Virtualization for real
C314.3 Install & Configure the different VM platforms
C314.4 Experiment with the VM with various software

Course Outcome – Assessment Methodology

Course Outcomes Vs POs/PSOs Mapping (High: 3, Medium: 2, Low: 1)

CO PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 PO11 PO12 PSO1 PSO2 PSO3
C314.1 1 3 1 3 2 - - - 1 1 3 1 2 3 2

C314.2 3 2 2 1 2 - - - 1 2 2 3 3 2 1

C314.3 3 2 1 3 1 - - - 2 2 1 3 3 3 2

C314.4 1 1 2 3 3 - - - 3 3 1 1 3 2 2

C314.5 1 3 2 3 1 - - - 2 1 3 3 1 1 2

C314 1.8 2.2 1.6 2.6 1.8 - - - 1.8 1.8 2 2.2 2.4 2.2 1.8
 INDEX
CO PO
Ex.No Name of the Experiment Mapped

Create type 2 virtualization in VMWARE or 1, 2, 3, 4, 9, 10, 11,

any equivalent Open Source Tool. CO1
1 12

shrink virtual hard disks in Hyper-V and How to 1, 2, 3, 4, 9, 10, 11,

CO2 12
2 compact virtual hard disks in Hyper-V

1, 2, 3, 4, 9, 10, 11,
Create RAID 5 volume CO4
3 12

Desktop Virtualization using Chrome remote 1, 2, 3, 4, 9, 10, 11,

CO2
4 Desktop 12

Desktop Virtualization using Chrome remote 1, 2, 3, 4, 9, 10, 11,

Desktop CO2 12
5

CO2 1, 2, 3, 4, 9, 10, 11,

6 Create type 2 virtualization on ESXI 6.5 server 12

1, 2, 3, 4, 9, 10, 11,
Create a VLAN in CISCO packet tracer CO3
7 12

1, 2, 3, 4, 9, 10, 11,
Install KVM in Linux CO2
8 12

1, 2, 3, 4, 9, 10, 11,
Create Nested Virtual Machine(VM under another CO5 12
9
VM)
Ex.no :1
Create type 2 virtualization in VMWARE or any equivalent
Date: Open Source Tool.

Aim
To create type 2 virtualization in vmware.

Steps:

1. Click Create a New Virtual Machine

2. Select the default option, Installer disc image file (iso)
3. Click Browse to find the ISO file
4. With "guest" OS selected, click Next
5. Select Linux as the Guest operating system type
6. Under Version, scroll through the list and select the OS
7. Click Next to proceed and if necessary, input a Virtual machine name
8. Confirm the storage Location and change if needed
With the operating system selected and configured, it's time to build the virtual machine.

1. Under Specify Disk Capacity adjust Maximum disk size if required (the default should be
enough)
2. Select Split virtual disk into multiple files as this makes moving the VM to a new PC easy
3. Click Next then confirm the details on the next screen
4. If anything seems wrong click Back, otherwise click Finish
Result
Thus the operating system like Linux using VMware was installed and Virtual machine created
sussessfuly.
 Ex.no :2
shrink virtual hard disks in Hyper-V and How to compact
Date: virtual hard disks in Hyper-V

Aim:
In Hyper-V environment, you can shrink, convert, expand, merge, reconnect or compact a virtual hard
disk by editing the corresponding file using either the GUI or CLI tools.

PROCEDURE

1. In Hyper-V Manager, connect to the VM

2.After logging into the VM, launch the Disk Management utility by typing msc in the search bar

.
3. Right-click the disk volume you would like to shrink, and select the Shrink Volume option

4. The next step is to enter the amount of space you wish to shrink in MB.
As you fill out this property, the Total size after shrink in MB value will change automatically, thus showing you
what the disk storage capacity will be after the shrink operation is complete.

5. Click Shrink to start shrinking the disk volume. As a result, you will have roughly 25 GB of
unallocated disk space.

6. After that, shut down the VM.

7. In Hyper-V Manager, right-click the VM and select Settings.

8. In the Hardware section, click Hard Drive to get access to the virtual hard disk settings.

Select Edit to launch the Edit Virtual Hard Disk Wizard.

9. You can skip the Locate Disk step, as you have already selected which disk you would like to
shrink. Click Next.
10. In the Choose Action section, select Shrink and click Next.

11. The next step is to configure the new size of the virtual hard disk.

12. In the Summary section, you can look through the changes you are about to
implement. Click Finish to complete the action and close the wizard.
13. Click Inspect to verify that the disk size has actually changed and you have successfully
shrunk the virtual hard disk.

As you can see, the maximum disk size has been successfully reduced to 115 GB.
How to compact virtual hard disks in Hyper-V

Unlike shrinking, the compact operation doesn’t reduce the storage capacity of the virtual hard disk. This
action reduces the file size of a virtual hard disk by removing empty blocks from the file. Note that you
cannot compact fixed virtual hard disks.

Before compacting or shrinking a virtual hard disk, it is recommended that you empty the Recycle Bin,
defragment the disk, and then create its backup to protect critical data in case of disk failure.
Remember that the VM using the disk needs to be turned off for the compact operation to work

1. Open Hyper-V Manager.

2. Right-click the VM and select Settings.

3. Click Hard Drive to get access to the virtual hard disk attached to this VM.
4. Click Edit to launch the Edit Virtual Hard Disk Wizard.
5. Skip the Locate Disk step as you have already selected the required virtual hard disk file,
and click Next.

6. In the Summary section, you can verify the changes that are about to be made to the virtual
hard disk. Click Finish to complete the action and close the wizard.

7. Click Inspect to verify that the disk file size has been actually reduced.
Result:

Thus shrink virtual hard disks in Hyper-V and How to compact virtual hard disks in Hyper-V was executed
successfully.
 Ex.no :3
RAID 0, RAID 1, RAID 5, RAID 10 Explained with Diagrams
Date:

RAID stands for Redundant Array of Inexpensive (Independent) Disks.

On most situations you will be using one of the following four levels of RAIDs.

 RAID 0
 RAID 1
 RAID 5
 RAID 10 (also known as RAID 1+0)
This article explains the main difference between these raid levels along with an easy to understand
diagram.

In all the diagrams mentioned below:

 A, B, C, D, E and F – represents blocks
 p1, p2, and p3 – represents parity

RAID LEVEL 0
Following are the key points to remember for RAID level 0.

 Minimum 2 disks.
 Excellent performance ( as blocks are striped ).
 No redundancy ( no mirror, no parity ).
 Don’t use this for any critical system.

RAID LEVEL 1

Following are the key points to remember for RAID level 1.

 Minimum 2 disks.
 Good performance ( no striping. no parity ).
 Excellent redundancy ( as blocks are mirrored ).

RAID LEVEL 5

RAID LEVEL 5
Following are the key points to remember for RAID level 5.

Minimum 3 disks.
Good performance ( as blocks are striped ).
Good redundancy ( distributed parity ).
Best cost effective option providing both performance and redundancy. Use this for DB that is
heavily read oriented. Write operations will be slow.

RAID LEVEL 10

Following are the key points to remember for RAID level 10.
Minimum 4 disks.
This is also called as “stripe of mirrors”
Excellent redundancy ( as blocks are mirrored )
Excellent performance ( as blocks are striped )
If you can afford the dollar, this is the BEST option for any mission critical applications (especially
databases).
 Ex.No: 3 Desktop Virtualization using VNC and Chrome remote Desktop
Date:

Starting the VNC session

Step 1 – Opening a terminal

Open MobaXterm and click on the Start local terminal button, as highlighted in the
image below.

Step 2 – Connecting to Linux system with SSH

In the command line, enter the following command

ssh your_username@host_name
Replace your_username with your MCECS username and replace host_name with
the address of the MCECS Linux machine or server you want to connect with (for
example, mo.ece.pdx.edu or rita.cecs.pdx.edu).

Enter your MCECS account password when prompted, and log in to the host system.

Step 3 – Starting VNC session process

Start a VNC session by entering the command vncserver

 NOTE: If you see the following message after entering vncserver, this means
you have a VNC session already running on this system. Go to the end of this
article for more information on how to check for existing VNC sessions and
also how to terminate them.

Step 4 – Creating VNC session password

You should now see a prompt to enter a password like in the image below. This will be your VNC session
password.

Be aware of the following:

• The session password needs to be at least 6 characters long.

• This password is only used to log in to your VNC session and is not tied to your MCECS account
password.
• This password is stored with very poor encryption, so it is advised that you do not use a sensitive
password for your VNC session password.

You will also be prompted to enter a view-only password, which can be used by other people to observe
your VNC session. If you are unsure about this feature, enter n for “no” and avoid creating one.

NOTE: It is possible you may not see a password prompt. If you have previously used VNC, the new
process will sometimes use your previous session password. If you have forgotten your previous session
password, run the command vnc passwd to change it.

Step 5 – Getting Display/Port numbers

Your VNC session has been created, and you should see a message similar to the
sample output below
The number that appears after the host address is the display number (it is underlined in red
in the image above). By adding this number to 5900, this will give you the port number
used to connect your VNC viewer to the VNC session.

For example, if your display number is 4, your port number is 5904. If your display
number is 12, your port number is 5912.

NOTE: Your display number may not be the same as the sample image above. Make sure to
read the output message in your terminal and look for the number after the semicolon for your
true display number.

The VNC session is now running on the remote Linux host system and is ready to connect
with your VNC viewing software. You can exit and close this terminal if you want, as the
VNC session will continue to run in the background. Be aware that the CAT will kill any
VNC session that has been idle for more than 48 hours.

Connecting with your VNC session with MobaXterm’s

VNC viewer

Step 1 – Opening new VNC viewer session

In MobaXterm, click on the Session button in the upper left hand corner

Step 2 – VNC viewer setup

In the window that pops up, look for the VNC icon in the top row and click on it

 In the Remote hostname or IP address box, enter localhost

 In the Port box, enter your Port Number. Recall that this is 5900 plus the
Display Number that appeared after running the vncserver command
Step 3 – SSH Gateway setup

In the lower area, click on the Network Settings tab, and then click on the SSH gateway
(jumphost) button. The button is highlighted in the blue box in the image above.

In the window that pops up, enter the following

 In the Gateway host box, enter the address of the host machine that
your VNC session is running on (e.g. ada.cs.pdx.edu, mo.ece.pdx.edu,
etc).
 In the Username box, enter your MCECS username.
 In Port, leave it set at 22
 Do not check off the box for Use SSH key.
 Afterwards, click the OK button with the green checkmark to save these settings and
close this configuration window.

When you return to the previous menu, click the OK button again and connect MobaXterm’s VNC
Viewer with the remote VNC session
Step 4 – VNC password guid

When you see the following window asking for the password for MCECS username on the host address,
enter your MCECS login password. This window may or may not appear, depending on how recently you
used MobaXterm to view a VNC session previously.

When you see the following window asking for the password for localhost, enter your VNC
session password.
 A new tab should now appear in MobaXterm with a Linux graphical interface.
Congratulations! You are now remotely connected with a Linux system via VNC.

Disconnecting vs. Terminating your VNC session

It is possible to disconnect from your VNC session and reconnect with it later on to pick up where you left
off. In MobaXterm, if you close the tab or click on the Disconnect button, your VNC session will not end
and will continue to run on the host system. To reconnect with your session, simply follow the instructions
above for Connecting with your VNC session with MobaXterm’s VNC viewer using the same session
password and port number as before.

Be aware that on CAT-supported systems, VNC sessions are terminated if they have been idle for more
than 48 hours.
If you want to kill the VNC session, you can use the Log Off or Shutdown option in the
Linux graphical interface. The location of these options will vary depending on the version
of Linux on the host system and your personal settings.

Alternatively, you can kill VNC sessions using the command vncserver -kill :X, where X is
replaced with your session’s Display Number.
Checking for existing VNC sessions
If you want to check for existing VNC sessions or find its display number,
run the command vncserver -list

If there is an existing session, you will see the following output

If there are no sessions running, you will see the following output

Changing your VNC password

If you want to change your VNC session password, run the command vncpasswd and follow the
prompts. The session password can be changed even if you have VNC currently running, allowing you
to use the new password even after starting a session.
Ex. No:5 Basic VLAN Configuration
Date
Basi
c VLAN Configuration

Topology Diagram

Addressing Table
Device
(Hostname) Interface IP Address Subnet Mask Default Gateway

S1 VLAN 99 172.17.99.11 255.255.255.0 N/A

S2 VLAN 99 172.17.99.12 255.255.255.0 N/A

S3 VLAN 99 172.17.99.13 255.255.255.0 N/A

PC1 NIC 172.17.10.21 255.255.255.0 172.17.10.1

PC2 NIC 172.17.20.22 255.255.255.0 172.17.20.1

PC3 NIC 172.17.30.23 255.255.255.0 172.17.30.1

PC4 NIC 172.17.10.24 255.255.255.0 172.17.10.1

PC5 NIC 172.17.20.25 255.255.255.0 172.17.20.1

PC6 NIC 172.17.30.26 255.255.255.0 172.17.30.1

Initial Port Assignments (Switches 2 and 3)

 Ports Assignment Network
Fa0/1 – 0/5 802.1q Trunks (Native VLAN 99) 172.17.99.0 /24
Fa0/6 – 0/10 VLAN 30 – Guest (Default) 172.17.30.0 /24
Fa0/11 – 0/17 VLAN 10 – Faculty/Staff 172.17.10.0 /24
Fa0/18 – 0/24 VLAN 20 – Students 172.17.20.0 /24

Upon completion of this lab, you will be able to:

• Cable a network according to the topology diagram
• Erase the startup configuration and reload a switch to the default state
• Perform basic configuration tasks on a switch
• Create VLANs
• Assign switch ports to a VLAN
• Add, move, and change ports
• Verify VLAN configuration
• Enable trunking on inter-switch connections
• Verify trunk configuration
• Save the VLAN configuration

Task 1: Prepare the Network

Step 1: Cable a network that is similar to the one in the topology diagram.
You can use any current switch in your lab as long as it has the required interfaces shown in the topology.
Note: If you use 2900 or 2950 switches, the outputs may appear different. Also, certain commands may be
different or unavailable.

Step 2: Clear any existing configurations on the switches, and initialize all ports in the shutdown state.
If necessary, refer to Lab 2.5.1, Appendix 1, for the procedure to clear switch configurations.
It is a good practice to disable any unused ports on the switches by putting them in shutdown. Disable all ports
on the switches:
Switch#config term Switch(config)#interface range faO/1-24 Switch(config-if-range)#shutdown
Switch(config-if-range)#interface range giO/1-2
Switch(config-if-range)#shutdown

Task 2: Perform Basic Switch Configurations

Step 1: Configure the switches according to the following guidelines.
• Configure the switch hostname.
• Disable DNS lookup.
• Configure an EXEC mode password of class.
• Configure a password of cisco for console connections.
• Configure a password of cisco for vty connections.
Step 2: Re-enable the user ports on S2 and S3.

S2(config)#interface range faO/6, faO/11, faO/18 S2(config-if-range)#switchport mode access S2(config-if-

range)#no shutdown

S3(config)#interface range faO/6, faO/11, faO/18 S3(config-if-range)#switchport mode access S3(config-if-

range)#no shutdown
Task 3: Configure and Activate Ethernet Interfaces
Step 1: Configure the PCs.
You can complete this lab using only two PCs by simply changing the IP addressing for the two PCs specific
to a test you want to conduct. For example, if you want to test connectivity between PC1 and PC2, then
configure the IP addresses for those PCs by referring to the addressing table at the beginning of the lab.
Alternatively, you can configure all six PCs with the IP addresses and default gateways.

Task 4: Configure VLANs on the Switch

Step 1: Create VLANs on switch S1.
Use the vlan vlan-id command in global configuration mode to add a VLAN to switch S1. There are four
VLANS configured for this lab: VLAN 10 (faculty/staff); VLAN 20 (students); VLAN 30 (guest); and VLAN
99 (management). After you create the VLAN, you will be in vlan configuration mode, where you can assign a
name to the VLAN with the name vlan name command.
S1(config)#vlan 1O
S1(config-vlan)#name faculty/staff
S1(config-vlan)#vlan 2O S1(config-vlan)#name students S1(config-vlan)#vlan 3O S1(config-vlan)#name
guest S1(config-vlan)#vlan 99 S1(config-vlan)#name management S1(config-vlan)#end
S1#

Step 2: Verify that the VLANs have been created on S1.

Use the show vlan brief command to verify that the VLANs have been created.
S1#show vlan brief

VLAN Name Status Ports

1 default active FaO/1, FaO/2, FaO/4, FaO/5 FaO/6, FaO/7, FaO/8, FaO/9
FaO/1O, FaO/11, FaO/12, FaO/13 FaO/14, FaO/15, FaO/16, FaO/17
FaO/18, FaO/19, FaO/2O, FaO/21
FaO/22, FaO/23, FaO/24, GiO/1 GiO/2
1O faculty/staff active
2O students active
3O guest active
99 management active
Step 3: Configure and name VLANs on switches S2 and S3.
Create and name VLANs 10, 20, 30, and 99 on S2 and S3 using the commands from Step 1. Verify the correct
configuration with the show vlan brief command.
What ports are currently assigned to the four VLANs you have created?

Step 4: Assign switch ports to VLANs on S2 and S3.

Refer to the port assignment table on page 1. Ports are assigned to VLANs in interface configuration mode,
using the switchport access vlan vlan-id command. You can assign each port individually or you can use the
interface range command to simplify this task, as shown here. The commands are shown for S3 only, but you
should configure both S2 and S3 similarly. Save your configuration when done.
S3(config)#interface range faO/6-1O
S3(config-if-range)#switchport access vlan 3O S3(config-if-range)#interface range faO/11-17 S3(config-if-
range)#switchport access vlan 1O S3(config-if-range)#interface range faO/18-24 S3(config-if-
range)#switchport access vlan 2O S3(config-if-range)#end
S3#copy running-config startup-config Destination filename [startup-config]? [enter]
Building configuration... [OK]
Step 5: Determine which ports have been added.
Use the show vlan id vlan-number command on S2 to see which ports are assigned to VLAN 10. Which ports
are assigned to VLAN 10?

Note: The show vlan name vlan-name displays the same output.
You can also view VLAN assignment information using the show interfaces interface switchport
command.

Step 6: Assign the management VLAN.

A management VLAN is any VLAN that you configure to access the management capabilities of a switch.
VLAN 1 serves as the management VLAN if you did not specifically define another VLAN. You assign the
management VLAN an IP address and subnet mask. A switch can be managed via HTTP, Telnet, SSH, or
SNMP. Because the out-of-the-box configuration of a Cisco switch has VLAN 1 as the default VLAN, VLAN
1 is a bad choice as the management VLAN. You do not want an arbitrary user who is connecting to a switch
to default to the management VLAN. Recall that you configured the management VLAN as VLAN 99 earlier
in this lab.
From interface configuration mode, use the ip address command to assign the management IP address to the
switches.
S1(config)#interface vlan 99
S1(config-if)#ip address 172.17.99.11 255.255.255.O
S1(config-if)#no shutdown
S2(config)#interface vlan 99
S2(config-if)#ip address 172.17.99.12 255.255.255.O
S2(config-if)#no shutdown
S3(config)#interface vlan 99
S3(config-if)#ip address 172.17.99.13 255.255.255.O
S3(config-if)#no shutdown
Assigning a management address allows IP communication between the switches, and also allows any host
connected to a port assigned to VLAN 99 to connect to the switches. Because VLAN 99 is configured as the
management VLAN, any ports assigned to this VLAN are considered management ports and should be secured
to control which devices can connect to these ports.
Step 7: Configure trunking and the native VLAN for the trunking ports on all switches.
Trunks are connections between the switches that allow the switches to exchange information for all VLANS.
By default, a trunk port belongs to all VLANs, as opposed to an access port, which can only belong to a single
VLAN. If the switch supports both ISL and 802.1Q VLAN encapsulation, the trunks must specify which
method is being used. Because the 2960 switch only supports 802.1Q trunking, it is not specified in this lab.
A native VLAN is assigned to an 802.1Q trunk port. In the topology, the native VLAN is VLAN 99. An
802.1Q trunk port supports traffic coming from many VLANs (tagged traffic) as well as traffic that does not
come from a VLAN (untagged traffic). The 802.1Q trunk port places untagged traffic on the native VLAN.
Untagged traffic is generated by a computer attached to a switch port that is configured with the native
VLAN. One of the IEEE 802.1Q specifications for Native VLANs is to maintain backward compatibility with
untagged traffic common to legacy LAN scenarios. For the purposes of this lab, a native VLAN serves as a
common identifier on opposing ends of a trunk link. It is a best practice to use a VLAN other than VLAN 1 as
the native VLAN.
Use the interface range command in global configuration mode to simplify configuring trunking.
S1(config)#interface range faO/1-5
S1(config-if-range)#switchport mode trunk
S1(config-if-range)#switchport trunk native vlan 99
S1(config-if-range)#no shutdown
S1(config-if-range)#end
S2(config)# interface range faO/1-5
S2(config-if-range)#switchport mode trunk
S2(config-if-range)#switchport trunk native vlan 99
S2(config-if-range)#no shutdown
S2(config-if-range)#end
S3(config)# interface range faO/1-5 S3(config-if-
range)#switchport mode trunk S3(config-if-
range)#switchport trunk native vlan 99
S3(config-if-range)#no shutdown
S3(config-if-range)#end
Verify that the trunks have been configured with the show interface trunk command.
S1#show interface trunk

Port Mode Encapsulation Status Native vlan

FaO/1 on 8O2.1q trunking 99
FaO/2 on 8O2.1q trunking 99

Port Vlans allowed on trunk FaO/1 1-4O94 FaO/2

1-4O94

Port Vlans allowed and active in management domain FaO/1 1,1O,2O,3O,99

FaO/2 1,1O,2O,3O,99

Port Vlans in spanning tree forwarding state and not pruned FaO/1 1,1O,2O,3O,99
FaO/2 1,1O,2O,3O,99

Step 8: Verify that the switches can communicate.

From S1, ping the management address on both S2 and S3.
S1#ping 172.17.99.12
Type escape sequence to abort.
Sending 5, 1OO-byte ICMP Echos to 172.17.99.12, timeout is 2 seconds:
!!!!!
Success rate is 1OO percent (5/5), round-trip min/avg/max = 1/2/9 ms
S1#ping 172.17.99.13
Type escape sequence to abort.
Sending 5, 1OO-byte ICMP Echos to 172.17.99.13, timeout is 2 seconds:
.!!!!
Success rate is 8O percent (4/5), round-trip min/avg/max = 1/1/1 ms
Step 9: Ping several hosts from PC2.
Ping from host PC2 to host PC1 (172.17.10.21). Is the ping attempt successful?
Ping from host PC2 to the switch VLAN 99 IP address 172.17.99.12. Is the ping attempt successful? Ping from
host PC2 to host PC5. Is the ping attempt successful?
Step 10: Move PC1 into the same VLAN as PC2.
The port connected to PC2 (S2 Fa0/18) is assigned to VLAN 20, and the port connected to PC1 (S2 Fa0/11) is
assigned to VLAN 10. Reassign the S2 Fa0/11 port to VLAN 20. You do not need to first remove a port from a
VLAN to change its VLAN membership. After you reassign a port to a new VLAN, that port is automatically
removed from its previous VLAN.
S2#configure terminal
Enter configuration commands, one per line. End with CNTL/Z. S2(config)#interface fastethernet O/11
S2(config-if)#switchport access vlan 2O
S2(config-if)#end

Ping from host PC2 to host PC1. Is the ping attempt successful?
Even though the ports used by PC1 and PC2 are in the same VLAN, they are still in different subnetworks, so
they cannot communicate directly.

Step 11: Change the IP address and network on PC1.

Change the IP address on PC1 to 172.17.20.22. The subnet mask and default gateway can remain the same.
Once again, ping from host PC2 to host PC1, using the newly assigned IP address.
Is the ping attempt successful? Why was this attempt successful?

Task 5: Document the Switch Configurations

On each switch, capture the running configuration to a text file and save it for future reference.

Task 6: Clean Up
Erase the configurations and reload the switches. Disconnect and store the cabling. For PC hosts that are
normally connected to other networks (such as the school LAN or to the Internet), reconnect the appropriate
cabling and restore the TCP/IP settings.
Ex.No:6
Date: Installation and Configuration of virtualization using KVM

1. Aim: Installation and Configuration of virtualization using KVM

2. Objectives: From this experiment, the student will be able to,

Understand the concepts of virtualization.
Understand KVM architecture and its configuration.

3. Outcomes: The learner will be able,

To analyze user models and develop user centric interfaces

To analyze the local and global impact of computing on individuals, organizations, and
society.
To engage in life-long learning development and higher studies.
To understand, identify, analyze and design the problem, implement and validate the solution
including both hardware and software.

4. Hardware / Software Required: Ubuntu operating system, open source software KVM,
Internet.

5. Theory: Virtualization is software that separates physical infrastructures to create various

dedicated resources. It is the fundamental technology that powers cloud computing.
The technology behind virtualization is known as a virtual machine monitor (VMM) or virtual
manager, which separates compute environments from the actual physical infrastructure.
Virtualization makes servers, workstations, storage and other systems independent of the physical
hardware layer. This is done by installing a Hypervisor on top of the hardware layer, where the
systems are then installed.
There are three areas of IT where virtualization is making headroads, network virtualization, storage
virtualization and server virtualization:
Network virtualization is a method of combining the available resources in a network by splitting up
the available bandwidth into channels, each of which is independent from the others, and each of
which can be assigned (or reassigned) to a particular server or device in real time. The idea is that
virtualization disguises the true complexity of the network by separating it into manageable parts,
much like your partitioned hard drive makes it easier to manage your files.
Storage virtualization is the pooling of physical storage from multiple network storage devices into
what appears to be a single storage device that is
managed from a central console. Storage virtualization is commonly used in
storage area networks (SANs).
Server virtualization is the masking of server resources (including the number and
identity of individual physical servers, processors, and operating systems) from server
users. The intention is to spare the user from having to understand and manage
complicated details of server resources while increasing resource sharing and utilization
and maintaining the capacity to expand later. Virtualization can be viewed as part of an
overall trend in enterprise IT that includes autonomic computing, a scenario in which the
IT environment will be able to manage itself based on perceived activity, and utility
computing, in which computer processing power is seen as a utility that clients can pay
for only as needed. The usual goal of virtualization is to centralize administrative tasks
while improving scalability and work loads.

Procedure:

Installation Steps :
#sudo grep -c "svm\|vmx" /proc/cpuinfo
#sudo apt-get install qemu-kvm libvirt-bin bridge-utils virt-manager
#sudoadduserrait
#sudoadduserraitlibvirtd
After running this command, log out and log back in as rait

Run following command after logging back in as rait and you should see an empty list
of virtual machines. This indicates that everything is working correctly.
#virsh -c qemu:///system list
Open Virtual Machine Manager application and Create Virtual Machine #virt-
manager
Result:

SNAPSHOTS
Step 1 : #sudo grep -c "svm\|vmx" /proc/cpuinfo

Step 2 : #sudo apt-get install qemu-kvm libvirt-bin bridge-utils virt-manager

Step 3 : #sudoadduserrait
After running this command, log out and log back in as rait

Step 4 : #sudoadduserraitlibvirtd
After running this command, log out and log back in as rait

Step 5 : Open Virtual Machine Manager application and Create Virtual

Machine #virt-manager as shown below

Step 6 : Create a new virtual machine as shown below

Step 7 : Install windows operating system on virtual machine
Step 8: Installation of windows on virtual machine

Step 9: Installation of windows 7 on virtual machine

 Step 10: Initialization of windows on virtual machine

6. Conclusion:
Installation and configuration of KVM have been done successfully onto Ubantu and
users added. Like this we can create as many virtual machines as possible on OS and can
install any windows onto it
Ex.No:
Date: Create Nested Virtual Machine(VM under another VM)

Aim:
Enable Nested Virtualization

How to Set Up Hyper-V Nested Virtualization [Step-by-Step]

 Creating A NAT-Enabled Virtual Switch.

 Creating the First-Level Guest Virtual Machine. ...
 Enabling Nested Virtualization.
 Installing The Guest Operating System.
 Connecting To The Network.
 Installing Hyper-V On The First-Level Virtual Machine.
 Conclusion.

Enable Nested Virtualization in Windows 10 Hyper-V

Hyper-V is the built-in hypervisor that comes free in Windows and Windows Server. It is used to run on
Windows. Virtualization is also used for other features, like Virtualization-Based Security (VBS), Windows
Sandbox, and Windows Defender Application Guard (WDAG). Developers sometimes use virtualization with
Visual Studio to run device emulators.

Microsoft introduced support for nested virtualization in Windows Server 2016. Nested virtualization lets you
turn on . So, you can think of it like a VM running inside a VM.

There are a few prerequisites that you need to meet before you can use nested virtualization. The VM
configuration must be version 8.0 or higher. And nested virtualization is only supported on Intel CPUs with
virtualization (VT-x) and Extended Page Tables (EPT).