What is a characteristic of para-virtualization?

Question

Options

• APara-virtualization guest servers are unaware of one another
• BPara-virtualization allows direct access between the guest OS and the hypervisor
• CPara-virtualization allows the host hardware to be directly accessed
• DPara-virtualization lacks support for containers

• B
  91% (20)
• C
  5% (1)
• D
  5% (1)

Explanation

Para-Virtualization Explained

Para-virtualization is a virtualization technique where the guest operating system is modified to be aware it is running in a virtualized environment, allowing it to communicate directly with the hypervisor through special APIs called "hypercalls" - this direct, cooperative communication channel is what makes Option B correct. Option A is incorrect because guest servers in para-virtualization are actually aware of the virtualized environment (and in some implementations, can be aware of each other's existence); it is full virtualization where guests are typically isolated and unaware. Option C is wrong because para-virtualization does not allow direct hardware access - the whole point is that the guest talks to the hypervisor, which then manages hardware access, whereas direct hardware access describes bare-metal or pass-through configurations. Option D is a distractor with no meaningful connection to para-virtualization, as container support is a separate architectural concern unrelated to whether virtualization is para or full.

Memory Tip: Think of the prefix "para-" meaning "alongside" - in para-virtualization, the guest OS works alongside the hypervisor through direct communication, rather than being tricked into thinking it has real hardware. If the guest "knows" it's virtual, it's para-virtualization!

No community discussion yet for this question.