roots/wiki
1
0
Fork 0
Code Pull Requests Activity

clean-up

Browse Source 
reorganize the wiki using only two-levels of directories
This commit is contained in:
lukas
2023-05-27 21:34:15 +02:00
parent 6988e58855
commit 676136cb05
59 changed files with 488 additions and 892 deletions
Download Patch File Download Diff File Expand all files Collapse all files

130
gofurther/checks.md
View File

@@ -1,130 +0,0 @@
---
title: Performs a few checks on Phyllome OS
description:
published: true
date: 2022-01-28T08:45:03.356Z
tags:
editor: markdown
dateCreated: 2021-11-13T11:39:13.790Z
---
# Checkup
Before creating your first virtual machine, it is a good idea to check if everything is correctly set up.
## Perform a global checkup
The command-line tool `virt-host-validate` allows you to check whether virtualization features are activated or not.
* Use the following command to check your system:
```
virt-host-validate
```
* Make sure the result look like this:
```
[groot@phyllome ~]$ virt-host-validate
QEMU: Checking for hardware virtualization : PASS
QEMU: Checking if device /dev/kvm exists : PASS
QEMU: Checking if device /dev/kvm is accessible : PASS
QEMU: Checking if device /dev/vhost-net exists : PASS
QEMU: Checking if device /dev/net/tun exists : PASS
QEMU: Checking for cgroup 'cpu' controller support : PASS
QEMU: Checking for cgroup 'cpuacct' controller support : PASS
QEMU: Checking for cgroup 'cpuset' controller support : PASS
QEMU: Checking for cgroup 'memory' controller support : PASS
QEMU: Checking for cgroup 'devices' controller support : WARN[^1] (Enable 'devices' in kernel Kconfig file or mount/enable cgroup controller in your system)
QEMU: Checking for cgroup 'blkio' controller support : PASS
QEMU: Checking for device assignment IOMMU support : PASS
QEMU: Checking if IOMMU is enabled by kernel : PASS
```
[^1]: The warning message for *cgroup devices* can be disregarded, as it won't show up if the `virt-host-validate` command is executed as *root*. [Related discussion](https://gitlab.com/libvirt/libvirt/-/issues/94).
> *If `/dev/kvm` is not found, please ensure that your hardware [is indeed compatible](/deploy/prepare#meet-the-requirements) and that hardware-assisted virtualization [has been activated](/deploy/prepare#enable-hardware-assisted-virtualization) in the BIOS/EFI.*
{.is-info}
## Specific checkup
### Hardware-assisted virtualization (1st gen)
* For Intel CPUs, you can use the following more specific command to check whether *hardware virtualization* is activated:
```
cat /proc/cpuinfo | grep vmx
```
* For AMD CPUs, the following command can be used:
```
cat /proc/cpuinfo | grep svm
```
* Look for `svm` for AMD-based processors, or `vmx` for Intel-based processors.
```
[groot@phyllome ~]$ cat /proc/cpuinfo | grep svm
flags : fpu vme de [...] svm [...] sme sev sev_es
```
### Hardware-assisted virtualization (2st gen, IOMMU-based)
Your computer may be compatible with advanced hardware virtualization features (*AMD Vi* or Intel *VT-d*).
* Check the presence of IOMMU-based hardware-assisted virtualization using the following command [^2]:
[^2]: Courtesy of the [Archlinux wiki](https://wiki.archlinux.org/title/PCI_passthrough_via_OVMF#Enabling_IOMMU).
```
dmesg | grep -i -e DMAR -e IOMMU
```
* Make sure the result looks like this:
```
[ 0.600228] iommu: Default domain type: Translated
[ 0.624416] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
[ 0.624444] pci 0000:00:01.0: Adding to iommu group 0
[...]
[ 0.624690] pci 0000:0b:00.4: Adding to iommu group 15
[ 0.627236] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
[ 0.627987] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
```
* You may also want to learn how well isolated your devices are. To do so, copy and paste the following script[^1] in your terminal:
```
for g in `find /sys/kernel/iommu_groups/* -maxdepth 0 -type d | sort -V`; do
echo "IOMMU Group ${g##*/}:"
for d in $g/devices/*; do
echo -e "\t$(lspci -nns ${d##*/})"
done;
done;
```
[^1]: Courtesy of the [Archlinux wiki](https://wiki.archlinux.org/title/PCI_passthrough_via_OVMF#Ensuring_that_the_groups_are_valid)
* In the following case, devices are rather poorly isolated. The use of the ACS override patch may be warranted (more on that later...).
```
IOMMU Group 0:
[...]
01:00.0 Non-Volatile memory controller [0108]: Intel Corporation SSD 660P Series [8086:f1a8] (rev 03)
02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ee]
02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] Device [1022:43eb]
[...]
04:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2)
04:00.1 Audio device [0403]: NVIDIA Corporation GM107 High Definition Audio Controller [GeForce 940MX] [10de:0fbc] (rev a1)
07:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
IOMMU Group 1:
[...]
09:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1)
09:00.1 Audio device [0403]: NVIDIA Corporation GM204 High Definition Audio Controller [10de:0fbb] (rev a1)
[...]
IOMMU Group 14:
0b:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c]
IOMMU Group 15:
0b:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487]
```
---
*[**Go to parent page**](/gofurther/)*

24
gofurther/darwin.md
View File

@@ -1,24 +0,0 @@
---
title: Darwin family
description:
published: true
date: 2021-11-14T18:41:52.601Z
tags:
editor: markdown
dateCreated: 2021-11-13T16:29:34.112Z
---
> Section under construction
{.is-warning}
# Darwin-based operating systems
> Phyllome OS **strongly** discourages users from virtualizing proprietary, darwin-based operating systems on non-Apple hardware. The Phyllome OS Project will take any possible measures to shutdown threads that mention such setup on platforms it has control over.
{.is-danger}
> That being said, it is perfectly legal to virtualize open-source, darwin-based operating systems surch as [PureDarwin](https://www.puredarwin.org/), even on non-Apple hardware. As a result, Phyllome OS **strongly** encourage users to do so.
{.is-info}
## Introduction
`to be done`

2
gofurther/encrypt.md
View File

@@ -407,4 +407,4 @@ Then reboot.
---
*[**Go to parent page**](/gofurther/)*
*[**Go to parent page**](https://wiki.phyllo.me/)*

3
gofurther/evdev.md
View File

@@ -62,3 +62,6 @@ cat /dev/input/by-id/usb-Logitech_G513_RGB_MECHANICAL_GAMING_KEYBOARD_1569307831
* https://libvirt.org/formatdomain.html#input-devices
---
*[**Go to parent page**](https://wiki.phyllo.me/)*

2
gofurther/hack.md
View File

@@ -14,4 +14,4 @@ Current instructions on how to develop Phyllome OS and modify the system can be
---
***[Go to parent page](/gofurther)***
*[**Go to parent page**](https://wiki.phyllo.me/)*

92
gofurther/install-guest.md
View File

@@ -1,92 +0,0 @@
---
title: Netboot for all
description:
published: true
date: 2021-11-25T13:58:10.457Z
tags:
editor: markdown
dateCreated: 2021-11-13T11:43:58.697Z
---
# Use a live guest OS
As of now, `netboot.xyz` is one of the main way to deploy or use a guest operating system inside Phyllome OS. It is compatible with most (but not all) guest operating systems. This small guide will show you how to deploy a live system inside Phyllome OS.
## Preparation
By default, `netboot.xyz.iso` should already be located under `var/lib/libvirt/iso`. If it's not the case, please use the following command to fetch it, or navigate to [the website](https://netboot.xyz/):
```
wget https://boot.netboot.xyz/ipxe/netboot.xyz.iso -P /var/lib/libvirt/iso/
```
## Run the script
The following script, which also doesn't require root privileges, will create a virtual machine called `my-first-live-vm`. This virtual machine will be started automatically and added to `virt-manager`.
```
/usr/sbin/create-live-vm.sh
```
*Notice the new icon under QEMU/KVM: this is the new virtual machine that has just been created. Go to the section to learn how to interact with it.*
![post-install-conf-2.png](/assets/post-launch/post-install-conf-2.png)
## Access your virtual machine display
* Double-click on *my-first-live-vm* to open its virtual display, then click on *Connect to console*.
![post-install-conf-3.png](/assets/post-launch/post-install-conf-3.png)
> Phyllome OS ships with a small ISO crafted by the team behind [netboot.xyz](https://netboot.xyz/), and that can do network boot, allowing it to do network-based installations of the most popular Linux distributions, among other niceties.
{.is-info}
![post-install-conf-11.png](/assets/post-launch/post-install-conf-11.png)
* After a few seconds, you will be greeted by the following screen.
![post-install-conf-4.png](/assets/post-launch/post-install-conf-4.png)
* Under the menu, go to *View* and select *Full Screen*
![post-install-conf-5.png](/assets/post-launch/post-install-conf-5.png)
* Go to *Live CDs*
> There is no disk attached to this virtual machine. As a result, only Live CDs will work out-the-box.
{.is-info}
![post-install-conf-10.png](/assets/post-launch/post-install-conf-10.png)
* Scroll down this list
![post-install-conf-13.png](/assets/post-launch/post-install-conf-13.png)
* Stop at *Tiny Core Linux* and press <kbd>Enter</kbd>
![post-install-conf-14.png](/assets/post-launch/post-install-conf-14.png)
* Select *Tiny Core Linux x86_64*
![post-install-conf-15.png](/assets/post-launch/post-install-conf-15.png)
* Select *Tiny Core Linux CorePure*
![post-install-conf-16.png](/assets/post-launch/post-install-conf-16.png)
* Enjoy your disposable virtual machine
![post-install-conf-6.png](/assets/post-launch/post-install-conf-6.png)
* When you are done messing around, input the following, and you will be back in Phyllome OS
```
sudo poweroff
```
> That's it, congratulations!
{.is-success}
---
*Are you looking for other tasks to execute on your system? If so, go the [suggested tasks section](/gofurther)*

60
gofurther/live.md Normal file
View File

@@ -0,0 +1,60 @@
---
title: Get started with the Live system
description:
published: true
date: 2021-11-22T20:54:09.582Z
tags:
editor: markdown
dateCreated: 2021-11-13T11:36:55.647Z
---
# Phyllome OS as a live system
> Phyllome OS is not production-ready, let alone ready to be used daily as a live system.
{.is-warning}
Using Phyllome OS as a live system is a great way to test it out and make sure your host computer is up to the task, before committing to a [permanent installation](/deploy/live), which is currently the recommended way to use Phyllome OS.
Under certain conditions, you may want to use a live system daily, provided that the disk and [XML configuration](/virt/xml) of your virtual machine disks are stored outside the USB thumb drive.
## Boot from a USB flash drive
By default, when a computer boots up, it will look for an operating system on the internal storage device first. If there is one, it will load this operating system and ignore any other media, such as any USB flash drive that may be plugged to the computer.
To boot from a USB flash drive, one would have to either temporary or permanently alter the so-called boot order. The boot order instructs at what point and where it should look for an operating system. The following section illustrates how to change the boot order *temporary*.
> The process to change the boot order depends on your current computer platform. Please follow the instruction that matches your platform.
{.is-info}
> Booting from a USB flash drive is a **non-destructive** process, which means that it won't affect any pre-existing operating system that may be installed on your computer. As a precautious, it may be good to backup your data or, even better, to use a computer with no personnal data on it.
{.is-info}
### macOS
* Make sure that your computer is turned-off.
* Locate the <kbd>Alt</kbd> / <kbd>Option</kbd> key on your keyboard.
* Turn your computer on and immediately press the <kbd>Alt</kbd> / <kbd>Option</kbd> key continuously.
* The startup manager should appear after a few seconds.
* Click on the option called *EFI* to boot Phyllome OS.
> Other Mac startup key combinations can be found [here](https://support.apple.com/en-us/HT201255).
{.is-info}
### Windows 8 and later versions
> Section under construction
{.is-warning}
### Other computers
> Section under construction
{.is-warning}
## Use it daily
> At the moment, changes applied to a Phyllome OS Live medium do not persist across reboots.
{.is-info}
---
*Are you looking for things to do with your live system? If so, have a look at doing some [suggested tasks](/gofurther)*

12
gofurther/migrate.md
View File

@@ -1,12 +0,0 @@
---
title: Migrate an existing guest to a new host
description:
published: true
date: 2021-11-13T11:42:58.575Z
tags:
editor: markdown
dateCreated: 2021-11-13T11:42:58.575Z
---
> Section under construction
{.is-warning}

196
gofurther/reactos.md
View File

@@ -1,196 +0,0 @@
---
title: ReactOS
description:
published: true
date: 2022-01-20T13:26:23.710Z
tags:
editor: markdown
dateCreated: 2021-11-13T11:52:33.257Z
---
# ReactOS
[ReactOS](https://reactos.org/) is an open-source operating system meant to behave exactly like Windows XP, Windows Server 2003 and later versions of Windows.
In theory, it can run any software and work with any drivers developed for these older versions of Windows. Decades old software or pieces of equipments that no longer ship with drivers to run with the latest iterations of the Windows operating system may work with ReactOS.
In practice, it is still under heavy-development and may not work as expected.
> **Phyllome OS support**
Support for the more modern PCI-Express-enabled Q35 chipset, UEFI or other virtio-devices, which Phyllome OS favors, is still lacking in ReactOS. Performance of the display won't be optimal, resulting in screen tearing. More information can be found [here](/virt/guest/reactos).
{.is-warning}
## Installation
> ReactOS is currently in **Alpha stage** and not production ready.
{.is-warning}
There are basically three steps you need to make before you can use this binary-compatible and open-source replica of Windows:
* Download a medium to install the system
* Install the system
* Configure the system
### Download
* *Go fetch the latest build of the *Boot CD* version of ReactOS on the official website*: https://reactos.org/getbuilds/
> Alternatively, the latest stable release could be downloaded.
{.is-info}
* *Unzip it using p7zip* (`dnf install p7zip`).
```
7za x reactos-bootcd-0.4.15-dev-3628-ga6bf77e-x86-gcc-lin-dbg.7z
```
* *Copy the resulting ISO under* `/var/lib/libvirt/images/`
```
mv reactos-bootcd-0.4.15-dev-3628-ga6bf77e-x86-gcc-lin-dbg /var/lib/libvirt/images/
```
### Launch the installer
* *[Clone]() the `legacy model` of virtual machine and, optionally, [rename]() it*
* *[Add the ISO file]() you just downloaded and [add a disk]() of at least 1GB using the Virtual Machine Manager*
> As of 2022, a full installation of ReactOS takes around 750Mb.
{.is-info}
* *[Power-on the virtual machine]()*
* *[Connect to the console]()*
* *Just as in the good ol' days, you need to press a key to start the installer. Notice the fact that an open firmware, [SeaBIOS](https://www.seabios.org/SeaBIOS), is able to boot an open-source NT-based kernel. A rare sight.*
![reactos_installation-0.png](/assets/reactos/reactos_installation-0.png)
> The installer supports navigation using the keyboard only.
{.is-info}
* *Choose the language for the installation process, using the keyboard Arrows Keys*
![reactos_installation-1.png](/assets/reactos/reactos_installation-1.png)
* *Press <kbd>ENTER</kbd>*
![reactos_installation-2.png](/assets/reactos/reactos_installation-2.png)
* *Press <kbd>ENTER</kbd> once again*
![reactos_installation-3.png](/assets/reactos/reactos_installation-3.png)
* *Navigate to "Accept these device settings" and press <kbd>ENTER</kbd>*
![reactos_installation-4.png](/assets/reactos/reactos_installation-4.png)
* *Press <kbd>ENTER</kbd> again to select the Unpartitionned space*
![reactos_installation-5.png](/assets/reactos/reactos_installation-5.png)
* *Press <kbd>ENTER</kbd> to select the FAT file-system.*
![reactos_installation-6.png](/assets/reactos/reactos_installation-6.png)
> *Amazingly, the [BTRFS](https://en.wikipedia.org/wiki/Btrfs) file system is also supported.*
{.is-info}
* *Press <kbd>ENTER</kbd> again to format the targeted partition using the selected file system.*
![reactos_installation-7.png](/assets/reactos/reactos_installation-7.png)
* *Once the formatting is done, press <kbd>ENTER</kbd> again to install ReactOS to the selected disk*
![reactos_installation-8.png](/assets/reactos/reactos_installation-8.png)
* *Wait for the setup to complete. It is fast, so there won't be enough time for a coffee.*
![reactos_installation-9.png](/assets/reactos/reactos_installation-9.png)
* *Once the setup is done, install the bootloader on the hard disk. The default choice seems fine. Press <kbd>ENTER</kbd> to reach the next step.*
![reactos_installation-10.png](/assets/reactos/reactos_installation-10.png)
* *The installation is done, wait a few seconds or press <kbd>ENTER</kbd> to force the system to reboot right away.*
![reactos_installation-11.png](/assets/reactos/reactos_installation-11.png)
### Go through the first boot and initial setup
* *Freeloader: ReactOS' bootloader in all its glory. Wait a few seconds or press <kbd>ENTER</kbd> to start ReactOS*
![reactos_boot-1.png](/assets/reactos/reactos_boot-1.png)
* *Some devices will be automatically installed. Wait a few seconds...*
![reactos_boot-2.png](/assets/reactos/reactos_boot-2.png)
> Starting now, your mouse can be used to navigate around.
{.is-info}
* *The first boot Wizard for ReactOS should eventually appear. Press <kbd>ENTER</kbd> or click on* "Next"
![reactos_boot-3.png](/assets/reactos/reactos_boot-3.png)
* *ReactOS relies on other Open Source projets to function, which it takes time to acknowledge. Press <kbd>ENTER</kbd> or click on "Next"*
![reactos_boot-4.png](/assets/reactos/reactos_boot-4.png)
* *ReactOS can behave as a server or as a workstation. If you are unsure, choose workstation. Press <kbd>ENTER</kbd> or click on "Next"*
![reactos_boot-5.png](/assets/reactos/reactos_boot-5.png)
* *The system language and local can be customized here. If you are satisfied with the default settings, press <kbd>ENTER</kbd> or click on "Next". Otherwise, please modify the settings.*
![reactos_boot-6.png](/assets/reactos/reactos_boot-6.png)
* *Pick a username and, optionaly, an organization, then press <kbd>ENTER</kbd> or click on "Next" to go to the next screen.*
![reactos_boot-8.png](/assets/reactos/reactos_boot-8.png)
* *Choose an administrator password, and possibly a computer name, then press <kbd>ENTER</kbd> or click on "Next" to go to the next screen.*
![reactos_boot-10.png](/assets/reactos/reactos_boot-10.png)
* *Make sure you pick the right timezone then press <kbd>ENTER</kbd> or click on "Next" to go to the next screen.*
![reactos_boot-11.png](/assets/reactos/reactos_boot-11.png)
* *You can pick the theme of your liking. Press <kbd>ENTER</kbd> or click on "Next" to go to the next screen when you are done.*
![reactos_boot-12.png](/assets/reactos/reactos_boot-12.png)
* *Here, you should not have to configure anything for ReactOS to have LAN and Internet access, through the newly supported `virtio-net` device. Press <kbd>ENTER</kbd> or click on "Next" to go to the next screen.*
![reactos_boot-13.png](/assets/reactos/reactos_boot-13.png)
* *If you wish to share files with other computers on your network, joining a Workgroup would be a first step. Press <kbd>ENTER</kbd> or click on "Next" to go to the next screen.*
![reactos_boot-14.png](/assets/reactos/reactos_boot-14.png)
* *That's it. Press <kbd>ENTER</kbd> or click on "Finish" to reboot your computer.*
![reactos_boot-15.png](/assets/reactos/reactos_boot-15.png)
### Go through the first boot and initial setup
* *Take a few seconds to admire great splash screen*
![reactos_first-boot-1.png](/assets/reactos/reactos_first-boot-1.png)
* *The system will automatically open a session with the user you created (that is pretty clever, as there is no need to remember the password I already forgot :')). A few windows may open, prompting you to install some devices. Unless you know what you are doing, cancel these prompts to land on the pristine desktop.*
![reactos_first-boot-2.png](/assets/reactos/reactos_first-boot-2.png)
* *As already stated, support for the more modern PCI-Express-enabled Q35 chipset, UEFI or other virtio-devices is not yet there. You may still enjoy the ride, try to install these old software that has long been forgotten in a drawer or this decade old printer collecting dust, and that no operating system would dare to interact with anymore*
![reactos_first-boot-3.png](/assets/reactos/reactos_first-boot-3.png)
> Congratulations, you have successfully installed ReactOS!
{.is-success}
---
* *Are you ready to try out other operating systems or learn how to execute certain tasks? If so, please follow [the link](https://wiki.phyllo.me/e/en/gofurther/)*

2
gofurther/resize.md
View File

@@ -94,4 +94,4 @@ On Fedora-related distributions, `virt-resize` is provided by the `guestfs-tools
---
*[**Go to parent page**](/gofurther/)*
*[**Go to parent page**](https://wiki.phyllo.me/)*

19
gofurther/vfio-mdev.md
View File

@@ -19,6 +19,21 @@ Then, these vGPUs can be assigned to virtual machines or containers.
Contrary to paravirtualized GPUs (e.g. *virtio-gpu*), vGPUs can use the same driver as their parent GPU (e.g. a guest compatible with an Intel GPUs will be able to leverage an Intel-based vGPUs)
## Modify the system allocated to the GPU in the BIOS/UEFI
> Some computers allow you to modify the system memory allocated or shared with the integrated GPU, which may allow you to create more vGPUs.
{.is-info}
> For Intel integrated graphics cards only; rarely available on laptops computers.
{.is-warning}
* Before the host operating system boots up, you need to enter the BIOS/UEFI and to look for a setting called *GPU aperture size*, or *GPU shared memory*.
* Use the highest possible value.
> System memory will be reserved for the GPU, so make sure you have enough system memory to accomodate both the GPU and your operating system.
{.is-warning}
## Preparation
* Make sure the GRUB has been updated after [the first boot](https://wiki.phyllo.me/getstarted/disk#update-grub-and-reboot)
@@ -165,3 +180,7 @@ Some computers allow you to modify the memory allocated or shared with the integ
* Official page for vfio-mdev: https://www.kernel.org/doc/html/latest/driver-api/vfio-mediated-device.html
* Archlinux's *must-read entry* on Intel GVT-g: https://wiki.archlinux.org/title/Intel_GVT-g
* DMA-BUF Linux documentation: https://www.kernel.org/doc/html/latest/driver-api/dma-buf.html
---
*[**Go to parent page**](https://wiki.phyllo.me/)*

3
gofurther/virt-install.md
View File

@@ -197,7 +197,6 @@ virt-install \
--location=/tmp/Fedora-Everything-netinst-x86_64-35-1.2.iso \
--initrd-inject virtual-desktop-cdrom.cfg --extra-args "inst.ks=file:/virtual-phyllome-desktop-cdrom.cfg"
```
---
***[Go to parent page](/gofurther)***
*[**Go to parent page**](https://wiki.phyllo.me/)*

21
gofurther/virt-manager.md
View File

@@ -1,21 +0,0 @@
---
title: The Virtual Machine Manager
description:
published: true
date: 2021-11-13T17:33:45.018Z
tags:
editor: markdown
dateCreated: 2021-11-13T11:40:06.083Z
---
> Section under construction
{.is-warning}
# Configure the Virtual Machine Manager
## Forewords
## Automatically
## Manually

3
gofurther/virtiofs.md
View File

@@ -83,3 +83,6 @@ share /mnt/ virtiofs rw,noatime,_netdev 0 0
* In the context of a Windows guest: https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/VirtIO-FS:-Shared-file-system
* https://wiki.archlinux.org/title/Libvirt#Sharing_data_between_host_and_guest
---
*[**Go to parent page**](https://wiki.phyllo.me/)*

12
gofurther/windows.md
View File

@@ -1,12 +0,0 @@
---
title: Windows
description:
published: true
date: 2021-11-13T11:52:19.245Z
tags:
editor: markdown
dateCreated: 2021-11-13T11:52:19.245Z
---
> Section under construction
{.is-warning}

15
gofurther/windows11.md
View File

@@ -1,15 +0,0 @@
---
title: Windows
description:
published: true
date: 2023-05-19T17:24:19.852Z
tags:
editor: markdown
dateCreated: 2023-05-19T17:24:19.852Z
---
# Windows
## Resources
* https://kevinlocke.name/bits/2021/12/10/windows-11-guest-virtio-libvirt/