fixup! koyomi: Init

machines/koyomi/README.md

@@ -8,14 +8,29 @@ SPDX-License-Identifier: CC-BY-SA-4.0
 
 ## Hardware
 
-TBD
+System from [Hetzner Online Serverbörse](https://www.hetzner.com/sb).
 
-mdadm --create /dev/md/boot --homehost=koyomi -n 2 -l 1 -e 1.0 /dev/nvme0n1p2 /dev/nvme1n1p2
-mdadm --create /dev/md/main --homehost=koyomi -n 2 -l 1 -e 1.2 /dev/nvme0n1p3 /dev/nvme1n1p3
+- Motherboard: FUJITSU D3401-H1
+- CPU: Intel Core i7-6700
+- RAM: 4×16 GB Samsung [M378A2K43CB1-CRC](https://semiconductor.samsung.com/dram/module/udimm/m378a2k43cb1-crc/)/[M378A2K43BB1-CPB](https://semiconductor.samsung.com/dram/module/udimm/m378a2k43bb1-cpb/) (DDR4 2400/2133 MHz)
+- SSD: 2×512 GB M.2 NVMe SAMSUNG MZVLB512HAJQ-00000
+
+## Setup
+
+As it is a physical server (not a VM) in a remote location,
+extra care must be taken when installing.
+Fortunately, Hetzner provides an automated way to reset the server (by sending Ctrl+Alt+Del or force resetting)
+and a rescue system that can be activated before a reboot.
+Additionally, there is also a *vKVM* rescue system,
+that boots a hypervisor from the network and runs a VM which boots from the physical disks.
+
+The rescue system can be used to start a kexec installer generated by [nixos-generators](https://github.com/nix-community/nixos-generators).
+Ideally, everything goes well and the next reboot works,
+but in the case it does not, the vKVM rescue system can be used for debugging.
 
 ## Purpose
 
-TBD
+Hypervisor. Exact scope is to be determined.
 
 ## Name