CSL605 Cloud Computing Lab Sem VI

EXPERIMENT 7

Name: Anushka Joseph

Batch: A
Roll no: 03

Title To study and implement Hosted Virtualization using Virtual Box.

Pre requisite Virtualization, Types of Virtualizations

Mapping with CO CSL605.1

Objective To apply the concept of Virtualization along with their types, structures and
mechanisms in a local machine.

Outcome To demonstrate creating and running Virtual machines inside hosted

hypervisors like VirtualBox.

Instructions 1. Download and Install Oracle Virtual Box

2. Download Ubuntu .iso image
3. Select this image from Virtual Box
Referral Link for detailed steps:
https://itsfoss.com/install-linux-in-virtualbox/

You can download .exe for Virtual Box and .iso Ubuntu image from given
drive link:
https://drive.google.com/drive/folders/1sYF2nGj1DUpDymkS5iyAijYoPfqv9c
vx?usp=sharing
Deliverables 1. Write theory for comparing Bare Metal and Hypervisor
Virtualizations with the help of examples.

2. Submit stepwise screenshots for creating Virtual Machine.

Theory Virtualization has become pervasive across various domains, including data
centers, edge computing setups, networks, storage systems, and desktop
environments. Despite its widespread adoption, it's crucial for administrators
and decision-makers to recognize the distinctions between different
virtualization methods.
A hypervisor is computer software or hardware that enables you to host
multiple virtual machines. Each virtual machine is able to run its own
programs. A hypervisor allows you to access several virtual machines that are
all working optimally on a single piece of computer hardware. With a
hypervisor, each virtual machine or operating system you have will be able to
run its own programs, as it will appear that the system has the host hardware's
processor, memory and resources. In reality, however, it is actually the
hypervisor that is allocating those resources to the virtual machines.

By deploying a hypervisor to abstract software from the underlying physical

hardware, IT administrators can optimize the utilization of computing
resources while enhancing workload flexibility and resilience. This
experiment offers an opportunity to revisit the classic approaches of
virtualization and explore the current landscape of both technologies.

The servers need to execute the hypervisor, and the hypervisor, in turn, loads
the client operating systems of the virtual machines. The hypervisor allocates
the correct CPU resources, memory, bandwidth and disk storage space for
each virtual machine. A virtual machine can create requests to the hypervisor
through a variety of methods, including API calls.

There are two types of hypervisors:

 Embedded or hosted hypervisors, and
 Bare metal or native hypervisors.

Bare Metal or Native Hypervisors

Bare-metal virtualization entails installing a Type 1 hypervisor directly onto

hardware without the need for prior operating systems, drivers, or applications.
Hypervisors like VMware ESXi and Microsoft Hyper-V are commonly used
in this setup. Once installed, the hypervisor identifies and virtualizes the
system's CPU, memory, and other resources, creating virtual representations.
These resources are then allocated to create independent virtual machines
(VMs), each capable of running operating systems and applications. The
hypervisor manages the communication and translation between physical and
virtual resources to ensure VMs use only virtualized resources. The number of
VMs a bare-metal hypervisor can create depends on available resources, with
each VM remaining isolated and independent from others. VMs can be saved
to disk for backup, reloading, or duplication onto other servers. A few
examples include: Microsoft Hyper-V hypervisor, VMware ESX/ESXi, Oracle
VM Server for x86, KVM, or Citrix XenServer.

Example: Upon installation, a bare-metal hypervisor identifies and virtualizes

the system's CPU, memory, and other resources, creating virtual
representations of these assets. These resources are then allocated to create
independent virtual machines (VMs), each capable of running operating
systems and applications. The hypervisor facilitates communication and
conversion between physical and virtual resources, ensuring that VMs and
their software utilize only virtualized resources. For instance, if a server has 24
CPU cores, the hypervisor translates these cores into 24 vCPUs, allowing for
various VM configurations based on resource availability. Each VM remains
isolated and independent, sharing no resources or awareness with other VMs
on the system. Administrators can save, back up, reload, or duplicate fully
configured VMs as needed.

Embedded or Hosted Hypervisor Virtualization

Hosted virtualization, like bare-metal virtualization, operates similarly in

many aspects but differs in how the hypervisor is installed. In a hosted
environment, the hypervisor is installed on top of the host operating system,
such as VMware Workstation or Oracle VirtualBox. Despite this similarity,
hosted virtualization cannot virtualize resources for the host OS or installed
applications due to their prior allocation. Consequently, the number of VMs a
hosted hypervisor can create is limited by available resources minus those
reserved for the host OS. While hosted hypervisors are commonly used in
endpoint systems for running multiple desktop environments, they are less
prevalent in enterprise tasks due to the additional layer imposed by the host
OS, which can introduce a single point of failure. However, hosted
hypervisors have found new applications in container-based virtualization,
where containers leverage a container engine as a hosted hypervisor to
efficiently utilize system resources and enable rapid scalability. Examples of
hosted hypervisors include Parallels Desktop for Mac, Windows Virtual PC,
Oracle Virtual Box, and VMware Workstation.

Example: In a software development environment, a developer can use a

hosted hypervisor like VMware Workstation to run multiple virtual machines,
each hosting different operating systems for testing software compatibility.
Additionally, the developer may leverage Docker containers within these
virtual machines to isolate and manage individual components of their
application, enabling rapid deployment and testing of microservices. This
hybrid approach combines the benefits of VMs for full OS isolation with the
efficiency and scalability of containers for managing application components.
Snapshots 1. Downloading and installing VirtualBox
1. Installing Linux using VirtualBox
2. Running Linux on Virtual Box
3. Taking a Snapshot of the screen and accessing it
4. Logging out and shutting down
5. Closing the Running of the VM and Removing it
Conclusion In summary, this experiment demonstrated the process of creating and running
virtual machines using Oracle VirtualBox. Participants followed stepwise
instructions to install VirtualBox, download an Ubuntu .iso image, and set up a
virtual machine. The experiment aimed to illustrate the differences between
bare metal and hypervisor virtualizations through theoretical comparisons and
practical examples. The experiment provided hands-on experience in
virtualization technology, helping in understanding its applications in modern
computing environments.
References 1. https://itsfoss.com/install-linux-in-virtualbox/
2. https://www.virtualbox.org/?ref=itsfoss.com
3. https://www.techtarget.com/searchitoperations/tip/A-beginners-guide-
to-hosted-and-bare-metal- virtualization#:~:text=Bare%2Dmetal
%20virtualization%20installs%2 0a,ESXi%20and%20Microsoft
%20Hyper%2DV.
4. https://pluralsight.com/blog/it-ops/what-is- hypervisor#:~:text=These
%20hypervisors%20are%20run%20as,Virtua l%20Box%2C%20and
%20VMware%20Workstation.