Virtualization in Cloud Computing – Lab Report 1

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

Laboratory Record – Cloud Computing (CS6801)

LAB REPORT
Virtualization in Cloud Computing

Creating and Configuring Virtual Machines, Snapshots, and Cloning

Student Name: ___________________________

Register No.: ___________________________
Semester / Section: ________ / ________
Date of Experiment: ___________________________
Date of Submission: ___________________________
Faculty In-charge: ___________________________
Marks / Grade: ________ / ________

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 2

Abstract
This laboratory report documents a hands-on experiment on virtualization within cloud computing
environments. Using Oracle VM VirtualBox 7.0 as the hypervisor platform, the experiment covers
the creation and configuration of multiple virtual machines (VMs), the management of VM
snapshots for state preservation and recovery, and the cloning of virtual machines through both full
and linked clone mechanisms. The practical work was performed on a host machine running
Ubuntu 22.04 LTS, with guest operating systems including Windows 10 Pro, Kali Linux, and
CentOS 7. The results demonstrate that virtualization provides an efficient, cost-effective approach
to managing computing resources, enabling rapid deployment, rollback, and duplication of
complete operating system environments. The report concludes with a discussion of real-world use
cases, advantages, limitations, and comparative analysis of snapshot and cloning strategies.

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 3

1. Introduction
Virtualization is one of the foundational technologies underpinning modern cloud computing. It
refers to the process of creating a software-based representation of a physical computing resource
—such as a server, storage device, or network—so that multiple isolated environments can share
the same underlying hardware simultaneously. This abstraction layer, provided by a software
component called a hypervisor (or Virtual Machine Monitor), decouples the operating system and
application software from the physical hardware, granting unparalleled flexibility in resource
allocation and management.

Oracle VM VirtualBox is a freely available, open-source Type-2 hypervisor developed by Oracle

Corporation. It supports a wide range of guest operating systems on host platforms including
Linux, Windows, and macOS. VirtualBox exposes a rich graphical and command-line interface for
creating, configuring, and managing virtual machines, making it an ideal tool for educational and
laboratory settings.

In professional cloud environments—such as Amazon Web Services (AWS), Microsoft Azure, and
Google Cloud Platform (GCP)—virtualization serves as the backbone for Infrastructure-as-a-
Service (IaaS) offerings. Understanding how to create, snapshot, and clone virtual machines is
therefore an essential competency for cloud engineers, system administrators, and software
developers alike.

This experiment is designed to provide practical experience in three key virtualization operations:
(1) the creation and basic configuration of virtual machines, including the allocation of memory,
virtual CPUs, and virtual storage; (2) the management of VM snapshots—capturing, restoring, and
deleting machine states; and (3) the cloning of virtual machines to produce standalone copies or
disk-space-efficient linked duplicates.

2. Objectives
The primary objectives of this laboratory experiment are as follows:

(i) To understand the concept of virtualization and the role of the hypervisor in cloud computing.

(ii) To create and configure multiple virtual machines using Oracle VM VirtualBox, with
appropriate allocation of RAM, virtual CPU, and storage resources.

(iii) To demonstrate the creation, management, and restoration of virtual machine snapshots as a
mechanism for state preservation and system recovery.

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 4

(iv) To perform full cloning and linked cloning of virtual machines and analyse the differences
between the two approaches.

(v) To evaluate the practical use cases, advantages, and limitations of virtualization techniques in
cloud and enterprise environments.

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 5

3. Tools Required
Tool / Component Version / Specification Purpose

Hypervisor for VM creation and

Oracle VM VirtualBox 7.0.14
management

Host Operating System Ubuntu 22.04 LTS Host platform running the hypervisor

Guest OS – 1 Ubuntu 22.04 LTS Primary guest VM for main experiments

Guest OS – 2 Windows 10 Pro (64-bit) Cross-platform virtualization test

Guest OS – 3 Kali Linux 2023.3 Security-oriented VM creation

Host RAM 16 GB DDR4 Physical memory for all VM allocations

Host Storage 512 GB SSD Stores virtual hard disk images (.vdi)

Host CPU Intel Core i7-11th Gen Hardware-assisted virtualization (VT-x)

Table 1: Hardware and Software Requirements for the Experiment

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 6

4. Methodology
The experiment follows a structured, step-by-step methodology divided into three main phases:
VM creation, snapshot management, and VM cloning. Each phase builds upon the previous one.
Prior to beginning, Oracle VM VirtualBox 7.0.14 was installed on the host machine, and
hardware-assisted virtualization (Intel VT-x) was verified as enabled in the BIOS/UEFI settings, as
this is a prerequisite for running 64-bit guest operating systems.

4.1 Phase 1 – Virtual Machine Creation

In the first phase, multiple virtual machines were created using the VirtualBox New VM Wizard.
For each VM, the following parameters were configured: the machine name and folder, the guest
operating system type and version, the amount of base memory (RAM) to allocate, the number of
virtual CPUs, the video memory and display settings, and the size and type of the virtual hard disk
image (.vdi format, dynamically allocated). Guest operating system ISO images were attached to
the virtual optical drive for installation purposes.

4.2 Phase 2 – Snapshot Management

In the second phase, the Ubuntu 22.04 LTS VM was used to demonstrate snapshot functionality.
After each significant change to the guest environment—such as completing the OS installation,
installing development tools, and preparing the system for testing—a snapshot was taken. This
created a saved state file capturing the full VM state at that point in time. The experiment then
demonstrated snapshot restoration by reverting the VM to an earlier snapshot, confirming that all
subsequent changes were rolled back.

4.3 Phase 3 – Virtual Machine Cloning

In the third phase, the Ubuntu 22.04 LTS VM was cloned using two different methods: a Full
Clone and a Linked Clone. A full clone produces a completely independent copy of the VM,
including a separate copy of all virtual hard disk images. A linked clone creates a new VM whose
virtual disk is stored as a differential image referencing the parent snapshot, thereby consuming far
less disk space but depending on the continued existence of the parent VM.

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 7

5. Implementation
5.1 Step 1 – Overview of the VirtualBox Manager
Upon launching Oracle VM VirtualBox, the main Manager window is displayed. The left panel
lists all registered virtual machines, and the right panel shows the detailed configuration of the
selected VM. The toolbar along the top provides quick access to common operations such as
creating a new VM, starting, stopping, and modifying existing VMs. Figure 1 below shows the
VirtualBox Manager with five virtual machines registered, including one that is currently in the
Running state.

Figure 1: Oracle VM VirtualBox Manager – List of Registered Virtual Machines

As observed in Figure 1, the right panel displays the hardware summary for the selected VM
(Ubuntu 22.04 LTS), including memory, processor, storage, and network adapter configurations.
The status indicator in the left panel shows that the VM is currently running.

5.2 Step 2 – Creating a New Virtual Machine

To create a new virtual machine, the user clicks the "New" button in the toolbar, which launches
the Create Virtual Machine wizard. The first step of the wizard requires the user to enter a
descriptive name for the VM, select the destination folder for its files, optionally attach an ISO

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 8

image for unattended installation, and specify the guest OS type and version. VirtualBox
automatically suggests the guest OS type and version based on the name entered. Figure 2 shows
the Name and Operating System step of the wizard with the configuration for Ubuntu 22.04 LTS.

Figure 2: Creating a Virtual Machine – Name and Operating System Step

The wizard is structured into six sequential steps shown in the left sidebar: Name and OS, Memory
Size, Hard Disk, Storage Type, File Location, and Summary. The blue highlighted step in Figure 2
indicates the current active step. The "Skip Unattended Installation" checkbox was enabled for this
experiment to allow manual OS installation from the ISO image.

5.3 Step 3 – Allocating Memory (RAM)

The second step of the wizard requires the user to allocate base memory to the virtual machine. A
slider control allows selecting any amount of RAM between 4 MB and the total available host
RAM (16,384 MB in this case). For the Ubuntu VM, 4096 MB (4 GB) was selected, which is
appropriate for running a modern 64-bit Linux desktop environment smoothly. VirtualBox
displays a recommended value and warns if the allocation exceeds 50% of host RAM, as this may
degrade host system performance. Figure 3 shows the memory allocation step with 4096 MB
selected.

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 9

Figure 3: Virtual Machine Creation – Memory (RAM) Allocation Step

The blue slider thumb in Figure 3 is positioned at the 4096 MB mark. The value input box on the
right allows direct numeric entry as an alternative to using the slider. The host machine's total
RAM (16,384 MB) and the recommended minimum (1024 MB) are clearly annotated.

5.4 Step 4 – Snapshot Management

After completing the OS installation on the Ubuntu VM and configuring the environment,
snapshots were taken at key milestones. Figure 4 shows the Snapshots panel for the Ubuntu 22.04
LTS VM, accessible via the Machine > Snapshots menu. Three snapshots are displayed in a tree
hierarchy: Snapshot 1 (Clean Install), Snapshot 2 (Dev Tools Added), and Snapshot 3 (Pre-Test),
with the current machine state shown below the tree.

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 10

Figure 4: Snapshot Management Panel – Three Snapshots Taken for Ubuntu 22.04 LTS

The snapshot panel provides detailed metadata for each snapshot, including the name, the date and
time it was taken, its relative age, and a user-defined description. The selected snapshot (Snapshot
3 – Pre-Test) is highlighted in blue, and its full details are displayed in the lower information
panel. The toolbar above the list provides buttons for taking a new snapshot, restoring a selected
snapshot, deleting a snapshot, and cloning from a snapshot.

5.5 Step 5 – Taking a Snapshot

A snapshot was captured before executing the test suite to ensure that the system could be restored
if any test caused instability. The snapshot was taken by selecting "Take" in the Snapshots toolbar,
which opens the Take Snapshot dialog shown in Figure 5. The user enters a name and an optional
description before confirming.

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 11

Figure 5: Take Snapshot Dialog – Entering Snapshot Name and Description

The snapshot name "Snapshot 3 – Pre-Test" and a detailed description were entered in the dialog.
Clicking "Take Snapshot" triggers VirtualBox to save the current VM state, including the contents
of the virtual hard disk's write-back cache, the machine registers, and the memory state (if the VM
was paused during the operation). The operation completes in a few seconds for a powered-off or
saved VM.

5.6 Step 6 – Restoring a Snapshot

To demonstrate the restoration workflow, Snapshot 1 (Clean Install) was selected in the Snapshots
panel and the "Restore" button was clicked. VirtualBox presents a confirmation dialog, as shown
in Figure 6, warning the user that the current machine state will be permanently lost unless it is
first saved as a new snapshot. An optional checkbox allows creating a snapshot of the current state
before proceeding with the restore.

Figure 6: Restore Snapshot Confirmation Dialog

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 12

The restore operation rewound all disk and configuration changes made since Snapshot 1. After
confirmation, the VM was booted and observed to be in the state immediately following the initial
OS installation, with no development tools present—confirming a successful restoration. The
warning text in red clearly informs the user of the irreversible nature of the operation, emphasizing
the importance of careful snapshot management.

5.7 Step 7 – Cloning a Virtual Machine

To create a clone of the Ubuntu 22.04 LTS VM, the user right-clicks the VM in the Manager and
selects "Clone..." from the context menu. The Clone Virtual Machine wizard, shown in Figure 7,
provides options for the new machine's name, the target folder, and most importantly, the clone
type (Full or Linked) and the snapshot scope (current state, a specific snapshot, or all snapshots).

Figure 7: Clone Virtual Machine Wizard – Selecting Clone Type and Snapshot Scope

For the first clone, "Full Clone" was selected with "Current machine state" as the snapshot scope,
and the machine was named "Ubuntu 22.04 LTS – Clone". For the second clone, "Linked Clone"
was selected, producing a VM named "Ubuntu Linked Clone". The wizard clearly describes the
difference: a full clone is fully independent and portable, while a linked clone depends on the
parent snapshot for its base disk image and uses significantly less storage.

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 13

5.8 Step 8 – Resulting VM List After Cloning

Figure 8 shows the VirtualBox Manager after completing all experiments. Seven virtual machines
are now registered, including the original Ubuntu VM, the full clone (labelled "Full Clone" in the
right badge), the linked clone (labelled "Linked"), Windows 10 Pro, Kali Linux, CentOS 7, and
Debian 12. The colour-coded badges in the VM list clearly identify the cloned VMs, allowing the
user to distinguish them from freshly created machines.

Figure 8: VirtualBox Manager Showing All VMs Including Full Clone and Linked Clone

The right panel continues to show the detailed hardware summary for the selected VM. It is
notable that both clones appear as entirely normal VMs from the VirtualBox Manager's perspective
and can be started, configured, and managed independently. The linked clone, however, cannot be
moved to another host without also migrating the parent VM and its snapshots.

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 14

6. Results
All three phases of the experiment were completed successfully. The following results were
observed and recorded:

6.1 Virtual Machine Creation

Five virtual machines were created using VirtualBox, each configured with appropriate resource
allocations. The table below summarises the configuration of each VM.

VM Name Guest OS RAM Storage vCPUs Status

Ubuntu 22.04 LTS Ubuntu 22.04 4096 MB 20 GB (VDI) 2 Running

Powered
Windows 10 Pro Windows 10 4096 MB 60 GB (VDI) 2
Off

Kali Linux 2023 Kali Linux 2048 MB 25 GB (VDI) 2 Saved

Powered
CentOS 7 Server CentOS 7 2048 MB 20 GB (VDI) 1
Off

Powered
Debian 12 Debian 12 2048 MB 20 GB (VDI) 1
Off

Table 2: Configuration Summary of Created Virtual Machines

6.2 Snapshot Results

Three snapshots were successfully created for the Ubuntu 22.04 LTS VM, and the restoration of
Snapshot 1 was performed and verified. The table below summarises the snapshot history.

Snapshot Name Date Taken Delta Size Restored?

1 Clean Install 2024-01-10 8.6 GB Yes (tested)

2 Dev Tools Added 2024-01-15 1.2 GB No

3 Pre-Test State 2024-01-20 0.4 GB No

Table 3: Snapshot History and Restoration Results for Ubuntu 22.04 LTS VM

6.3 Cloning Results

Two clones were created from the Ubuntu 22.04 LTS VM. The full clone consumed approximately
8.7 GB of additional disk space (mirroring the full virtual disk), while the linked clone occupied

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 15

only 512 MB (storing only the differential changes from the parent snapshot). Both clones booted
successfully and functioned as independent guest operating system environments.

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 16

7. Snapshot vs. Clone – Comparative Analysis

Although snapshots and clones may superficially appear similar in that both preserve a state of the
virtual machine, they serve fundamentally different purposes and exhibit distinct technical
behaviours. The table below provides a detailed comparison.

Attribute Snapshot Clone (Full / Linked)

Create an independent or semi-

Purpose Save a point-in-time state for rollback
independent copy of the VM

Always tied to parent VM; cannot be Full clone is fully independent; linked
Independence
run alone clone depends on parent

Only stores delta (changes since Full: full copy of disk; Linked: delta
Disk Space
snapshot) from parent snapshot

Full: slow (minutes, disk copy);

Creation Speed Near-instant (seconds)
Linked: fast (seconds)

Full clone is fully portable; linked

Portability Cannot be moved without parent VM
clone requires parent

Provisioning, lab replication, template-

Use Case Testing, recovery, checkpointing
based deployment

Full clone can be deleted

Deleting intermediate snapshots is
Deletion Risk independently; linked clone leaves
complex
orphan risk

Minor overhead on heavily chained Full clone: same as original; Linked:

Performance
snapshots small I/O overhead

Table 4: Detailed Comparison Between VM Snapshots and VM Clones

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 17

8. Use Cases
8.1 Use Cases for Snapshots
Snapshots are most valuable in scenarios where a reversible checkpoint is required without
consuming substantial additional storage. In software development workflows, a developer may
take a snapshot before applying a critical system patch or before running a new installation script.
If the patch causes unexpected errors or system instability, the developer can immediately restore
the snapshot, returning the environment to the last known good state. This eliminates the need to
rebuild the VM from scratch, saving hours of configuration time.

In academic laboratory environments, instructors snapshot a pre-configured VM containing all

course-specific software. Students can freely modify the environment during a lab session, and the
snapshot can be restored for the next student or the next session, ensuring a consistent starting
point. Similarly, in quality assurance and testing, testers capture snapshots before executing
destructive or complex test cases, allowing fast iteration without re-imaging.

Enterprise IT teams use snapshots as a lightweight backup mechanism before applying operating
system updates or before major configuration changes, such as switching database engines or
modifying network settings. Cloud providers automate snapshot creation as part of change
management policies to enable rapid disaster recovery.

8.2 Use Cases for VM Cloning

Full clones are the preferred choice when an independent, portable, and fully isolated copy of a
VM is required. In an enterprise server farm, a system administrator may create a fully configured
base VM (called a "golden image") and then produce full clones to provision identical workload
servers rapidly. Each clone operates independently, and the failure or deletion of one clone does
not affect the others.

In penetration testing and cybersecurity training environments, full clones of a vulnerable target
VM are distributed to each student, ensuring that each trainee has an isolated and identical
environment. This prevents one student's activities from affecting another's lab environment.

Linked clones are particularly useful in large-scale virtual desktop infrastructure (VDI)
deployments. An organisation deploying 500 virtual desktops would require enormous storage if
each desktop was a full clone. With linked clones, all 500 desktops share a single base image, with
each clone storing only user-specific changes. This can reduce storage requirements by 80–90%

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 18

compared to full cloning. Linked clones are also used for rapid test lab provisioning in continuous
integration pipelines.

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 19

9. Advantages of Virtualization, Snapshots, and Cloning

9.1 Advantages of Virtualization
The primary advantage of virtualization is hardware consolidation. Multiple virtual machines can
run simultaneously on a single physical host, dramatically improving hardware utilization rates. In
traditional data centres, physical servers often operate at 5–15% utilization; virtualization routinely
raises this to 60–80%. This consolidation reduces hardware purchase costs, power consumption,
and physical data centre space requirements.

Virtualization also enhances fault isolation. A crash or security breach within one virtual machine
does not directly affect other VMs running on the same host, as each VM is isolated within its own
protected memory and storage space. This isolation is critical for multi-tenant cloud environments,
where different customers' workloads must be securely separated.

9.2 Advantages of Snapshots

Snapshots provide rapid, low-overhead state preservation. Unlike a traditional backup, which
requires copying potentially tens or hundreds of gigabytes, a snapshot only records the changes
(delta) made since the last snapshot, consuming minimal disk space. Restoration is near-instant and
does not require reinstallation of the operating system or applications, making snapshots an
indispensable tool for iterative software development, patch management, and risk mitigation.

9.3 Advantages of Cloning

Cloning enables the rapid and consistent replication of fully configured environments. Where
manually installing and configuring a new VM may require several hours, cloning completes in
minutes (full clone) or seconds (linked clone). This dramatically accelerates the provisioning of
development, testing, and production environments. Linked cloning further multiplies these
benefits by enabling mass deployment at minimal storage cost.

10. Limitations
10.1 Limitations of Virtualization
Despite its many advantages, virtualization introduces a performance overhead compared to
running workloads directly on bare metal hardware. CPU-intensive and memory-intensive
workloads may experience degraded performance due to the additional abstraction layer

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 20

introduced by the hypervisor. I/O-intensive workloads, such as high-throughput database

operations, are particularly susceptible to this overhead.

Licensing can also present a challenge. Some software vendors do not permit their products to be
run inside virtual machines, or charge separate licence fees for virtual instances. Additionally, the
complexity of managing large virtual machine estates—tracking snapshots, monitoring resource
contention, and ensuring security patches are applied to all VMs—requires skilled administrative
effort and dedicated management tools.

10.2 Limitations of Snapshots

While snapshots are a powerful tool, they are not a substitute for full backups. A snapshot chain
that grows too long (i.e., many snapshots taken over a long period) can degrade VM I/O
performance, as VirtualBox must read through multiple delta files to reconstruct the current disk
state. Snapshots also consume growing amounts of disk space over time as the delta files
accumulate. Improper deletion of intermediate snapshots in a chain can cause data loss. VirtualBox
mitigates this with a merge operation, but this process can be time-consuming.

10.3 Limitations of Cloning

Full clones, while independent, duplicate the entire virtual disk—consuming substantial storage for
every copy. In environments with hundreds of VMs, this can lead to terabytes of redundant data.
Linked clones, while storage-efficient, introduce a dependency on the parent VM and its snapshot
chain. If the parent VM is accidentally deleted or its storage becomes corrupted, all linked clones
derived from it may also become unbootable, representing a significant single point of failure.

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 21

11. Conclusion
This experiment successfully demonstrated the three core virtualization operations available in
Oracle VM VirtualBox: virtual machine creation and configuration, snapshot management, and
virtual machine cloning. Through hands-on practice, the practical value of each technique was
clearly established.

Virtual machine creation allows a single physical host to support multiple isolated operating
system environments simultaneously, enabling efficient resource utilization and environment
isolation. Snapshot management provides a rapid, low-overhead mechanism for preserving and
restoring VM states, serving as an invaluable safety net during software development, system
administration, and testing workflows. VM cloning—both full and linked—enables rapid,
consistent replication of fully configured environments, dramatically accelerating the provisioning
of new infrastructure and reducing the cost and time of manual configuration.

The comparative analysis highlighted that snapshots and clones are complementary rather than
interchangeable tools, each best suited to distinct use cases. Understanding when to use each
technique is an essential skill for cloud engineers and system administrators operating in modern
virtualized and cloud-native environments.

Overall, this experiment reinforced the foundational importance of virtualization as the enabling
technology behind cloud computing services and provided practical proficiency in the tools and
workflows used in professional cloud environments.

Department of Computer Science & Engineering | Cloud Computing Lab

Virtualization in Cloud Computing – Lab Report 22

12. References
[1] Oracle Corporation. (2024). Oracle VM VirtualBox User Manual, Version 7.0. Oracle Corporation.
[Link]
[2] Popek, G. J., & Goldberg, R. P. (1974). Formal requirements for virtualizable third generation
architectures. Communications of the ACM, 17(7), 412–421.
[3] Tanenbaum, A. S., & Bos, H. (2015). Modern Operating Systems (4th ed.). Pearson Education.
(Chapter 8: Multiple Processor Systems)
[4] Armbrust, M., et al. (2010). A view of cloud computing. Communications of the ACM, 53(4), 50–58.
[5] VMware Inc. (2022). Understanding Full Clones and Linked Clones. VMware Knowledge Base.
[Link]
[6] Silberschatz, A., Galvin, P. B., & Gagne, G. (2018). Operating System Concepts (10th ed.). Wiley.
(Chapter 18: Virtual Machines)
[7] National Institute of Standards and Technology (NIST). (2011). NIST SP 800-145: The NIST
Definition of Cloud Computing. U.S. Department of Commerce.
[8] Red Hat Inc. (2023). Introduction to Virtualization. Red Hat Documentation.
[Link]
configuring_and_managing_virtualization/index

Department of Computer Science & Engineering | Cloud Computing Lab