Scribd
Upload
44 views

Operating System Theory Projrct Report

This document discusses virtual machines and some of their common problems. It provides details on virtual machine sprawl wasting resources when organizations don't properly manage VM creation. It also discusses potential network congestion issues from too many VMs on one server. The document then outlines some state-of-the-art virtualization techniques like tightly vs loosely coupled hypervisors. It describes a process VM that runs as a normal application. Results show benchmark tests of different virtualization systems. The conclusion discusses optimizations made to address bottlenecks between guest and host processes and memory protection operations.

Uploaded by

fgjjwdjhvf
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
44 views

Operating System Theory Projrct Report

This document discusses virtual machines and some of their common problems. It provides details on virtual machine sprawl wasting resources when organizations don't properly manage VM creation. It also discusses potential network congestion issues from too many VMs on one server. The document then outlines some state-of-the-art virtualization techniques like tightly vs loosely coupled hypervisors. It describes a process VM that runs as a normal application. Results show benchmark tests of different virtualization systems. The conclusion discusses optimizations made to address bottlenecks between guest and host processes and memory protection operations.

Uploaded by

fgjjwdjhvf
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

OPERATING SYSTEM REPORT

SUPPORT FOR VIRTUAL


MACHINE
RIPHAH INTERNATIONAL UNIVERSITY LAHORE
GROUP MEMBERS NAME :
M.IRFAN ALI
FARRUKH BASHIR
ANAS MEHMOOD

WHAT IS VIRTUAL MACHINE?


A virtual machine (VM) is an operating system (OS) or application environment that is
installed on software, which imitates dedicated hardware. The end user has the same
experience on a VM as they would on dedicated hardware.

Virtual Machine abstracts the hardware of our personal computer such as CPU, disk
drives, memory, NIC (Network Interface Card) etc, into many different execution
environments as per our requirements, hence giving us a feel that each execution
environment is a single computer. For example, VirtualBox.
When we run different processes on an operating system, it creates an illusion that
each process is running on a different processor having its own virtual memory, with
the help of CPU scheduling and virtual-memory techniques.

Problem Statement:
VM sprawl wastes valuable computing resources:
Organizations often virtualize a certain number of workloads and then have to buy more
servers down the line to accommodate more workloads. This occurs because
companies usually don't have the business policies in place to plan or manage VM
creation.

VMs can congest network traffic


Network congestion is another common problem. For example, an organization that
routinely runs its system numbers might notice that it has enough memory and CPU
cores to house 25 VMs on a single server. But once IT admins load those VMs onto the
server, they might discover that the server's only network interface card (NIC) port is
already saturated, which can interrupt VM communication and cause some VMs to
report network errors.
Consolidation will multiply the effect of server hardware failures
Consider 10 VMs all running on the same physical server. Virtualization provides tools
such as snapshots and live migration that can protect VMs and ensure their continued
operation under normal conditions

Application performance can still be marginal in a VM


Organizations that decide to move their 25-year-old custom-written corporate database
server into a VM might discover that the database performs slower than molasses.

State-of-the-art technique:

Depending on the virtualization technique used, hypervisors can be designed to be


either tightly or loosely coupled with the guest operating system. The performance of
tightly coupled hypervisors is higher than loosely coupled hypervisors . On the other
hand, tightly coupled hypervisors require the guest operating systems to be explicitly
modified, which is not always possible. One of the Cloud infrastructure design
challenges is to have hypervisors that are loosely coupled, but with adequate
performance.

Having hypervisors that are operating system agnostic increases system


modularity, manageability, maintainability, and flexibility, and allows upgrading or
changing the operating systems on the fly.

Methodology:
A process VM, sometimes called an application virtual machine, or Managed Runtime
Environment (MRE), runs as a normal application inside a host OS and supports a
single process. It is created when that process is started and destroyed when it exits.

Results:
kernel-build compiles the complete Linux 2.4.18 kernel . SPECweb99 measures web
server performance, using the 2.0.36 Apache web server. We configure SPECweb99
with 15 simultaneous connections spread over two clients connected to a 100 Mb/s
Ethernet switch. kernel-build and SPECweb99 exercise the vir tual machine intensively
by making many system calls.

They are similar to the I/O-intensive and kernel-inten sive workloads used to evaluate
Cellular Disco . All experiments are run on an computer with an AMD Athlon 1800+
CPU, 256 MB of memory, and a Samsung SV4084 IDE disk. The guest kernel is Linux
2.4.18 ported to UMLinux, and the host kernels for UMLinux are all Linux 2.4.18 with
different degrees of support for VMMs. All virtual machines are configured with 192 MB
of «physical» memory.

The virtual hard disk for UMLinux is stored on a raw disk partition on the host to avoid
double buffering the virtual disk data in the guest and host file caches and to prevent the
virtual machine from benefitting unfairly from the host’s file cache. The host uses the
same hardware and software installation as the virtual-machine systems and has access
to the full 256 MB of host memory.

Conclusion:
First, the host OS required a separate host user process to control the main guest-
machine process, and this generated a large number of host context switches. We
eliminated this bottleneck by moving the small amount of code that controlled the guest-
machine process into the host kernel. Second, switching between guest kernel and
guest user space generated a large number of memory protection operations on the
host. We eliminated this bottleneck in two ways.

We eliminated this bottleneck by allowing a single host process to maintain several


address space definitions.

You might also like