Talk:OS-level virtualization: Difference between revisions

Revision as of 15:05, 4 June 2022

Revision as of 10:37, 13 June 2022

Line 30:

::[[User:MrMizo|@MrMizo]] process name space, disk, network, etc. Any time you slice up a host system into separate rescources, from the process point of view, you are doing virtualization. You don't have to explicitly define abstract hardware, Virtualization is a general computing concept. For instance all of the following can be considered virtual machines:

:: - some programming language interpreters

:: - a machine defined in an FPGA

:: - common programs

:: This is also why processes are addressed Virtual Memory, which is memory multiplexing on a finite resource to give the process the view that it can utilize all of that resource (eg. you have 16GB of ram. The process perspective is that it has the full 16GB ram to utilize. Actually excess is written out as a page file, swap, or compressed memory) [[Special:Contributions/96.245.205.88|96.245.205.88]] ([[User talk:96.245.205.88|talk]]) 15:05, 4 June 2022 (UTC)

::: @talk:96.245.205.88 By that definition, introducing any boundary between system level APIs can be called virtualization. '''This dilutes the concept of virtualization down to the point of it being completely useless.'''

::: For example, by this logic, introducing any privilege boundaries between different processes on a system API level becomes virtualization. Since when privilege separation ⊂ virtualization? It's grotesque.

::: Your examples also aren't correct nor applicable here:

::: - Virtual memory virtualizes a resource called "address space". Paging is a separate technique which that virtualization makes easier; it has nothing to do with virtualization itself, you can page real memory address spaces too.

::: - Programming language interpreters often utilize a virtual machine that operates on virtual compute, with virtual bytecode (JVM / Python VM / etc.). The compute is what is virtualized via a ''virtual'' processing, with its own ISA that uses its own bytecode.

::: - FPGA is a class of a hardware component. It doesn't virtualize anything. They do real things using real hardware, it's just that the hardware is flexible enough to accomodate a vast ___domain of designs.

::: - Common programs - exactly how? Are you going to include "Hello World" under the virtualization umbrella at some point?

::: '''All of this still ignores the fact that the rename in question has been done unilaterally.'''

::: --[[User:MrMizo|MrMizo]] ([[User talk:MrMizo|talk]]) 10:37, 13 June 2022 (UTC)