docs: update phyllomeos/purpose

This commit is contained in:
lukas 2022-01-17 15:10:56 +00:00
parent d7e4d19f1c
commit c3d393832c

View File

@ -2,7 +2,7 @@
title: Purpose title: Purpose
description: description:
published: true published: true
date: 2021-11-12T15:31:30.659Z date: 2022-01-17T15:10:53.963Z
tags: tags:
editor: markdown editor: markdown
dateCreated: 2021-11-12T15:31:30.659Z dateCreated: 2021-11-12T15:31:30.659Z
@ -10,32 +10,31 @@ dateCreated: 2021-11-12T15:31:30.659Z
## Purpose ## Purpose
Why would one prefers to use an operating system installed on virtual hardware ? > *Why would one prefers to use an operating system running in a virtual machine?*
Adding a layer of abstraction between the operating system and the virtualization-friendly hardware allows for support of newer operating systems, beyond what the physical hardware can support. There are muliple reasons one would want to rely on virtual machines. Let's list some advantages, but also some limitations.
* By using Phyllome OS on Apple hardware that do not support the latest iteration of macOS, one could create a virtual machine and install the latest iteration of macOS anyway, further extending the life of hardware.
* **Note:** Phyllome OS does not and will **not** support running macOS on anything but Apple hardware, as it is -- sadly -- not allowed by Apple.
* Windows 11 requires a Trusted Platform Module (TPM). By using a virtual machine alongside a virtual TPM on unsupported hardware, one could still run Windows 11. The passthrough of a real TPM may also be supported.
### Advantages ### Advantages
More generally, a software-based/backed computer, or simply a virtual machine, has many advantages over a silicon-based computer : A software-based/backed computer, or simply a virtual machine, has many advantages over a silicon-based computer:
* **Cost** : the cost of creating a virtual machine tends to zero * **Cost**: the cost of creating a virtual machine tends to zero. Virtual machines are made out of computer code, and it is basically free to copy or to duplicate them.
* **Flexibility** : a software-backed computer, alongside its operating system, can be migrated to new physical hosts. In other * **Flexibility**: a software-backed computer, alongside its operating system, can be migrated to new physical hosts. In other words, when a user acquires a new physical computer, the entire computing environment may be copy/pasted to the new machine.
words, when a user acquires a new physical computer, the entire computing environment may be copy/pasted to the new machine. * **Compatibility**: contrary to silicon-based computers, which tend to be optimized to work at most with only a handful operating systems, a virtual machine can be designed to work with most operating systems.
- **Compatibility** : contrary to silicon-based computers, which tend to be optimized to work at most with only a handful operating * **Support**: Adding a layer of abstraction between the operating system and the virtualization-friendly hardware allows for support of newer operating systems, beyond what the physical hardware can support. Windows 11 requires a Trusted Platform Module (TPM) to be present. By using a virtual machine alongside a virtual TPM on unsupported hardware, one could still run Windows 11.
systems, a virtual machine can be designed to work with most operating systems.
### Limitations ### Limitations
Alas, it also comes with limitations, including but not limited to : Alas, it also comes with limitations, including but not limited to :
* Limited out-of-the box hardware support : hardware-assisted virtualization is available on many computers but rarely activated by default and not always correctly implemented. Users remain a the mercy of good platform firmware and may have to explicitly activate hardware-assisted virtualization in the BIOS/UEFI. Hardware components are often not correctly isolated in IOMMU groups. * **Limited out-of-the box hardware support**: hardware-assisted virtualization is available on many computers but rarely activated by default and not always correctly implemented. Users remain a the mercy of good platform firmware and may have to explicitly activate hardware-assisted virtualization in the BIOS/UEFI. Hardware components are often not correctly isolated in IOMMU groups.
* Offering first-class support for only a handful of curated computers might provide an answer, at the price of compatibility. * Offering first-class support for only a handful of curated computers might provide an answer, at the price of compatibility.
* When it comes to IOMMU groups, a workaround might have to be used for models that do not offer well-isolated IOMMU groups, a workaround that has security implications. * When it comes to IOMMU groups, a workaround might have to be used for models that do not offer well-isolated IOMMU groups, a workaround that has security implications.
* Reliance on devices or controllers passthrough to cover edge cases: virtual hardware do not cover all features a user may expect to have, including out of the box support for Bluetooth, wireless, or sound adapters. For those cases, USB or PCI Passthrough might be used. * Reliance on devices or controllers passthrough to cover edge cases: virtual hardware do not cover all features a user may expect to have, including out of the box support for Bluetooth, wireless, or sound adapters. For those cases, USB or PCI Passthrough might be used.
* Again, offering first-class support for only a handful of curated computers might provide an answer, at the price of compatibility. * Again, offering first-class support for only a handful of curated computers might provide an answer, at the price of compatibility.
* New virtual hardware are expected, including paravirtualized sound cards, which will improve the situation. * New virtual hardware are expected, including paravirtualized sound cards, which will improve the situation.
---
*[**Go back to parent page**](https://wiki.phyllo.me/)*