Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs/concepts: Fix description for Figure 1 #451

Merged
merged 1 commit into from
Aug 28, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions content/docs/concepts/virtualization.mdx
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
title: Virtualization
description: |
Through virtualization, multiple operating systems (OSes) are able to run on
the same hardware, independently, thinking that each one of them controls the
entire system.
Through virtualization, multiple operating systems (OSes) are able to run on
the same hardware, independently, thinking that each one of them controls the
entire system.
---

Virtualization can be done using a hypervisor, which is a low-level software
Expand Down Expand Up @@ -55,12 +55,12 @@ The hypervisors can be classified in 2 categories: Type 1 and Type 2:
In Figure 1 a comparison between different virtualization systems is illustrated
and demonstrates how the degree of separation between a "guest application" and
the hardware and “host” becomes further removed.
The defined job of the host OS and kernel or hypervisor became that of
1) to juggle the runtime of multiple applications and environments;
2) to present a subset or non-contiguous representation of hardware resources
virtually and translate operations, and provide emulation and compatibility
between guest and host; and,
3) to ultimately guard access to them to prevent corruption or malicious attacks.
The defined job of the host OS and kernel or hypervisor became that of 1) to
juggle the runtime of multiple applications and environments; 2) to present a
subset or non-contiguous representation of hardware resources virtually and
translate operations, and provide emulation and compatibility between guest and
host; and, 3) to ultimately guard access to them to prevent corruption or
malicious attacks.

## Supported platforms

Expand Down
Loading