Home/Notes/Virtualization & Concurrency
Board Exam Notes

Virtualization & Concurrency Notes

Questions

1–2 questions in university papers

Difficulty

Medium

Importance

Fundamental conceptual weight

Overview

Virtualization and Concurrency are fundamental OS concepts that dictate how modern systems optimize resource utilization. Understanding these allows students to grasp how multiple processes and threads interact within a single hardware environment, which is a frequent area for theoretical exam questions.

Multithreading Models

Multithreading models define the relationship between User-level threads and Kernel-level threads, influencing performance and scalability. Examiners often test the mapping strategies used to manage thread execution in different OS architectures.

  • Many-to-One Model: Multiple user threads mapped to a single kernel thread.
  • One-to-One Model: Each user thread mapped to a unique kernel thread.
  • Many-to-Many Model: Multiplexes user threads to a smaller or equal number of kernel threads.
  • Two-level Model: A variation of M:M that allows binding of a user thread to a kernel thread.
  • Blocking behavior: One-to-one models support concurrency even if one thread blocks.

Virtual Machines Basics

Virtualization abstracts the underlying physical hardware to create isolated environments known as Virtual Machines (VMs). This section typically covers the role of the Hypervisor in partitioning resources effectively.

  • Type-0 Hypervisor: Hardware-based solutions.
  • Type-1 Hypervisor: Bare-metal hypervisors (e.g., Xen, VMware ESXi).
  • Type-2 Hypervisor: Hosted hypervisors running on top of a conventional OS.
  • Guest OS: The operating system running inside the virtual machine environment.
  • Resource Isolation: Each VM acts as a separate system with its own virtualized resources.

Exam Tip

When answering questions on multithreading models, always prioritize drawing a simple diagram showing the mapping between user threads and kernel threads to maximize marks.

Common Mistakes

  • Confusing the role of a Hypervisor (VMM) with that of a standard operating system scheduler.
  • Failing to mention that Many-to-One models cannot exploit multicore systems for true parallel thread execution.
  • Overlooking the performance overhead introduced by Type-2 hypervisors due to guest-to-host system call transitions.

More Revision Notes

Ready to test yourself?

Play topic-wise Virtualization & Concurrency questions in Aspirant Arcade — gamified MCQ practice.

Download Free