Professional Documents
Culture Documents
ASSIGNMENT
1
Mubashir-Ahmed, Iddrisu Bamie
bamie147@gmail.com
Student ID
PG0124321
2
1. (a) The operating systems has so many functions, which includes;
Keeping track of information, its location, status and enforces access permissions
set by users
Keeping track of memory, which parts are in use and which parts are free for easy
memory are used by which user program. The memory addresses that have
already been allocated and the memory addresses of the memory that has not yet
been allocated
Keeping track of processes and the status of each process, the resource demands
of each process. The resource demands of each process are handled by the OS.
The OS decides the order in which processes have access to the processor, and
(b) A virtual machine (VM) is an Operating system (OS) that imitates a computer hardware
when installed. The user experience on a virtual machine is the same as the dedicated hardware.
VMs provide an isolated environment for running its own OS and applications independently
from the host system. Some reasons why users will prefer a virtual machine to a real machine
are:
i. A single physical machine can run many virtual machines, each of which appears to be a
complete machine.
3
ii. Another use of virtualization is for end users who want to be able to run two or more operating
systems at the same time, say Windows and Linux, because some of their favorite application
iii. The VM depends on the host physical resources but these resources are virtualized and can be
reassigned across the VM and this makes it possible to run different environments from the host.
iv. Virtualization streamlines disaster recovery by replicating your servers in the cloud. Since
VMs are independent of the underlying hardware, organizations do not need the same physical
servers offsite to facilitate a secondary recovery site. In the event of a disaster, employees can be
back online quickly with a cost-effective backup and disaster recovery solution.
(c). The microkernel known for high reliability because they splitting the operating system up
into small, well-defined modules, only one of which—the microkernel—runs in kernel mode and
the rest run as relatively power less ordinary user processes. In particular, by running each device
driver and file system as a separate user process, a bug in one of these can crash that component,
but cannot crash the entire system. But in a monolithic system with all the drivers in the kernel, a
buggy audio driver can easily reference an invalid memory address, crash the entire system and
be most efficient because it runs directly on the host machine's physical hardware without
loading the underlying operating system, and it is referred to as a bare-metal hypervisor. Type 1
hypervisors often provide support for software-defined storage and networking, which creates
additional security and portability for virtualized workloads. The typical type 1 hypervisor can
scale to virtualize workloads across several terabytes of RAM and hundreds of CPU cores. Also,
4
type 1 hypervisors allow for over-allocation of physical resources. VMs themselves do not
consume all the RAM you allocate to them. In fact, they only use the amount of RAM needed to
perform specific tasks. That is why they are resource efficient but a type 2 hypervisor is typically
because it relies on the host machine's preexisting operating system to manage calls to CPU,
memory, storage and network resources and do not have direct access to the host hardware and
resources, all hypervisor and VM activities must pass through the host OS, which inevitably
results in latency and wasted resources. In addition, security flaws and vulnerabilities in the host
OS could potentially compromise all VMs running on it hence inefficient as compared to type 1
hypervisors. For these reasons, type 1 hypervisor is more efficient than type 2 hypervisor.
(e). It is unwise to give user processes the power to turn off interrupts because if one of the
processes turn the interrupts off and never turned them on again, that could be the end of the
system. This is the reason why it is unwise to let user processes turn interrupt off themselves.