clean-up
reorganize the wiki using only two-levels of directories
This commit is contained in:
lukas
@ -74,4 +74,4 @@ When it comes to its longevity and number of variants, the UNIX family is by far
|
||||
|
||||
---
|
||||
|
||||
*[**Go to parent page**](/virt/)*
|
||||
*[**Go to parent page**](https://wiki.phyllo.me/)*
|
||||
@ -1,52 +0,0 @@
|
||||
---
|
||||
title: ReactOS reference
|
||||
description:
|
||||
published: true
|
||||
date: 2022-01-20T13:26:56.588Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2022-01-06T21:53:31.225Z
|
||||
---
|
||||
|
||||
# ReactOS reference
|
||||
|
||||
## State of support
|
||||
|
||||
> *Support for ReactOS in Phyllome OS is very limited.*
|
||||
{.is-warning}
|
||||
|
||||
| **Hardware** | ReactOS 4.13 | ReactOS 4.14 |
|
||||
| :- | :-: | :-: |
|
||||
| *[Chipset](/virt/vm/chipset)* | i440fx | i440fx |
|
||||
| *Firmware* | SeaBIOS [^1] | SeaBIOS |
|
||||
| *virtio-gpu* | No | No |
|
||||
| *virtio-video* | No | No |
|
||||
| *virtio-snd* | No | No |
|
||||
| *virtio-blk* | No | No |
|
||||
| *virtio-scsi* | No | No |
|
||||
| *virtio-fs* | No | No |
|
||||
| *virtio-net* | No | **Yes** [^2] |
|
||||
| *virtio-keyboard* | No | No |
|
||||
| *virtio-tablet* | No | No |
|
||||
|
||||
|
||||
> Porting new paravirtual devices to ReactOS would significantly improve the experience of running ReactOS inside Phyllome OS, and other virtualization solutions leveraging [paravirtual hardware](https://wiki.phyllo.me/e/en/virt/virtio). See [here](https://reactos.org/contributing/) on how you can contribute to ReactOS
|
||||
{.is-info}
|
||||
|
||||
## Resources
|
||||
|
||||
* [Official resource](https://reactos.org/wiki/QEMU) on running ReactOS with QEMU
|
||||
* [Hardware support list](https://reactos.org/wiki/Supported_Hardware) for ReactOS
|
||||
* [Git repository](https://github.com/hectorm/docker-qemu-reactos) providing a Docker image for the ReactOS operating system
|
||||
* [Current effort](https://github.com/QubesOS/qubes-issues/issues/2809) to integrate ReactOS and QubesOS
|
||||
* [GSoC 2018 project idea](https://reactos.org/wiki/Google_Summer_of_Code_2018_Ideas#Paravirtualization_Support) to port more paravirtualized devices to ReactOS
|
||||
|
||||
---
|
||||
|
||||
***[Go back to parent page](/virt)***
|
||||
|
||||
---
|
||||
#### Footnotes
|
||||
|
||||
[^1]: Support for [UEFI](https://reactos.org/wiki/UEFI), and potentially OVMF, is under-way.
|
||||
[^2]: See [here](https://doxygen.reactos.org/d1/dc8/virtio__types_8h.html#a5a27dcd221caab788e973f6964d84aa9) for the source code reference for `virtio-net`
|
||||
@ -75,4 +75,4 @@ With this software stack deployed on virtualization-friendly hardware, an operat
|
||||
|
||||
---
|
||||
|
||||
*[**Go back to parent page**](/virt)*
|
||||
*[**Go to parent page**](https://wiki.phyllo.me/)*
|
||||
14
virt/host.md
14
virt/host.md
@ -1,14 +0,0 @@
|
||||
---
|
||||
title: Host operating system
|
||||
description:
|
||||
published: true
|
||||
date: 2022-01-20T10:16:29.183Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2022-01-20T10:16:29.183Z
|
||||
---
|
||||
|
||||
# Host operating system
|
||||
|
||||
> *Under construction*
|
||||
{.is-warning}
|
||||
@ -129,4 +129,8 @@ failover # "Generic failover infrastructure/interface"
|
||||
|
||||
## Ressources
|
||||
|
||||
* https://storpool.com/blog/nested-virtualization-with-kvm-and-opennebula/
|
||||
* https://storpool.com/blog/nested-virtualization-with-kvm-and-opennebula/
|
||||
|
||||
---
|
||||
|
||||
*[**Go to parent page**](https://wiki.phyllo.me/)*
|
||||
@ -34,4 +34,8 @@ The Nvram contains the saved state of the UEFI configuration.
|
||||
|
||||
* Any new virtual machines will be saved there :
|
||||
|
||||
`/var/lib/libvirt/images`
|
||||
`/var/lib/libvirt/images`
|
||||
|
||||
---
|
||||
|
||||
*[**Go to parent page**](https://wiki.phyllo.me/)*
|
||||
@ -245,3 +245,7 @@ This is the description of an XML file associated to a virtio-based virtual mach
|
||||
## Reference
|
||||
|
||||
For a more thorough description, see https://libvirt.org/formatdomain.html
|
||||
|
||||
---
|
||||
|
||||
*[**Go to parent page**](https://wiki.phyllo.me/)*
|
||||
@ -115,4 +115,4 @@ Virtualization is used to better isolate resources on a physical computer and to
|
||||
|
||||
---
|
||||
|
||||
*[**Go back to parent page**](/virt)*
|
||||
*[**Go to parent page**](https://wiki.phyllo.me/)*
|
||||
@ -457,3 +457,7 @@ https://specs.openstack.org/openstack/nova-specs/specs/train/approved/allow-secu
|
||||
* Linux System Programming 2ed
|
||||
* The Linux Programming Interface: A Linux and UNIX System Programming Handbook (English Edition)
|
||||
* Linux-insides : https://0xax.gitbooks.io/linux-insides/content/
|
||||
|
||||
---
|
||||
|
||||
*[**Go to parent page**](https://wiki.phyllo.me/)*
|
||||
16
virt/vm.md
16
virt/vm.md
@ -1,16 +0,0 @@
|
||||
---
|
||||
title: Anatomy of a virtual machine
|
||||
description:
|
||||
published: true
|
||||
date: 2022-01-25T16:19:33.102Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2021-11-13T11:56:31.018Z
|
||||
---
|
||||
|
||||
> *Section under construction*
|
||||
{.is-warning}
|
||||
|
||||
---
|
||||
|
||||
***[Go back to parent page](/virt/)***
|
||||
@ -58,4 +58,4 @@ The `virt` virtual chipset is the most modern chipset, compatible with PCI-Expre
|
||||
|
||||
---
|
||||
|
||||
*[**Go back to parent page**](/virt/vm)*
|
||||
*[**Go to parent page**](https://wiki.phyllo.me/)*
|
||||
@ -128,3 +128,7 @@ It will look like that when launched:
|
||||
* [Official resource](https://libvirt.org/formatdomain.html#graphical-framebuffers) for libvirt-compatible displays, including various XML examples
|
||||
* [Libmks](https://gitlab.gnome.org/chergert/libmks) provides a "Mouse, Keyboard, and Screen" to QEMU using the D-Bus device support in QEMU and GTK 4.
|
||||
* [QEMU D-Bus display experiment](https://gitlab.com/marcandre.lureau/qemu-display/) is a WIP Rust crates to interact with a -display dbus QEMU
|
||||
|
||||
---
|
||||
|
||||
*[**Go to parent page**](https://wiki.phyllo.me/)*
|
||||
@ -42,4 +42,4 @@ The [Rust Hypervisor Firmware](https://github.com/cloud-hypervisor/rust-hypervis
|
||||
|
||||
---
|
||||
|
||||
*[**Go back to parent page**](/virt/vm)*
|
||||
*[**Go to parent page**](https://wiki.phyllo.me/)*
|
||||
@ -8,10 +8,7 @@ editor: markdown
|
||||
dateCreated: 2021-11-13T17:52:22.554Z
|
||||
---
|
||||
|
||||
> Section under construction.
|
||||
{.is-warning}
|
||||
|
||||
# Graphics cards
|
||||
# Graphic cards
|
||||
|
||||
Phyllome leverages 3D acceleration within guest operating systems extensively, in three different modes depending on the situation.
|
||||
|
||||
@ -26,3 +23,7 @@ Phyllome leverages 3D acceleration within guest operating systems extensively, i
|
||||
| *Driver* | No special driver in the guest | No special driver in the guest | Requires a special driver in the guest |
|
||||
| *Number of host GPUs* | Two GPUs in most situations | A single GPU | A single GPU |
|
||||
| *GPU support* | Mostly GPU agnostic | Recent Intel integrated GPUs and some professional grade Nvidia GPUs | Mostly GPU agnostic |
|
||||
|
||||
---
|
||||
|
||||
*[**Go to parent page**](https://wiki.phyllo.me/)*
|
||||
@ -64,5 +64,6 @@ Edit the virtual machine's definition and replace `MOUSE_NAME` and `KEYBOARD_NAM
|
||||
|
||||
* In-depth [Passthrough Post article](https://passthroughpo.st/using-evdev-passthrough-seamless-vm-input/) about evdev.
|
||||
|
||||
---
|
||||
|
||||
|
||||
*[**Go to parent page**](https://wiki.phyllo.me/)*
|
||||
|
||||
@ -87,4 +87,4 @@ In this section, the focus is oriented towards Virtual I/O Devices (VIRTIO), bet
|
||||
|
||||
---
|
||||
|
||||
*[**Go back to parent page**](/virt/vm)*
|
||||
*[**Go to parent page**](https://wiki.phyllo.me/)*
|
||||
Reference in New Issue
Block a user