# REPORT — Felhom in a virtual machine on OpenMediaVault 8, and a Hungarian guide for the pilot tester (2026-10-15)

Written in ASD-STE100 Simplified Technical English. Baselines read 16:25: felhom.eu `3263bb26bc`, felhom-controller
`85f65c70d8` (v0.314.0), felhom-agent `d2053e7d47`. Read first: `runbooks/target-selection.md`, `operations/nodes.md`,
`runbooks/day0-install.md`, `runbooks/VOLUNTEER-first-hour.md`, `architecture/15-media-library.md`,
`architecture/07-backup-architecture.md` §7.5, R-548. Evidence: `documentation/audits/omv-vm-2026-10-15/`.

## What waits on you

1. **Send the guide to Ferenc.** Its first section is five lines for an e-mail: `documentation/pilot/GUIDE-omv-kvm-hu.md`.
   If you do nothing: he has no steps for the call.
2. **Delete the test customer Tester4 in the hub** (browser only). The VM is gone; the host record stays until then.
3. **Two decisions, no hurry:** R-1071 (should Jellyfin read films from a NAS share?) and R-1073 (Felhom in a VM cannot
   see disk health — is that acceptable?).

## 1. Did it work end to end? — Yes, on an exact copy

- I built a copy of his box on demo-hp: OMV 8.5.11-1, kernel 7.2.6, 16 GB, a small system disk, a fake Samsung NVMe,
  and the KVM plugin 8.3.4. All the same versions as on his screenshots.
- I did every OMV step in OMV's own web pages, with a headless browser. Screenshots are in the evidence.
- **Firmware:** the plugin's default (BIOS) boots our ISO. I did not need UEFI.
- **The bridge:** it works, but OMV gets a **new address**, and the open page hangs. OMV's own screen shows the
  old address. `http://<name>.local` or the router finds it. Copying the card's hardware address did not keep the old
  address.
- **Autostart:** I restarted OMV with Felhom running. OMV shut Felhom down cleanly and started it again by itself.
  The dashboard was back in 1 min 52 s.

## 2. Memory

- The VM has 12 GB. Felhom's guest got **7.7 GB** (7,863 MB). The rule „total minus 4 GB" held.
- The estimator has no 12 GB size. By its own rule: the household set „fits, but tight"; without Immich „fits well".

## 3. Backups on a one-disk box

- Work: the whole-guest copy on the same disk (645 MB), and each app's first copy.
- Cannot exist: the second copy on another drive.
- The household sees: „Csak egy másolat készül (nincs második meghajtó)…" and „…így hibás fájlok ellen véd, lemezhiba
  ellen nem." Clear and true. The two sentences mix formal and informal Hungarian (R-1072).
- Off-site was not switched on for this test customer.

## 4. Jellyfin reading an OMV share — No

- Felhom mounts the OMV share (it needs a user name and a writable share).
- Jellyfin still gets only local drives. This is the design (R-108). Your decision: R-1071.

## 5. Problems Ferenc would meet, and what the guide does

| Problem | Guide |
|---|---|
| OMV's address changes after the bridge; the page hangs | says so before; `<name>.local`, router list, monitor steps |
| The bridge form shows no network card | delete the card's setting first, apply once |
| The VM hangs at „Booting from Hard Disk…" (old films partition) | wipe the NVMe in OMV first |
| The disk list also offers OMV's own disk | „never `/dev/sda` or `/dev/sdb`" |
| The plugin's default network is wrong | Modell = `bridge`, Híd = `br0` |
| The pool starts stopped | Állapot → Indítás |
| The installer refuses the default e-mail and hostname | the table says what to type |
| Jellyfin refused on one disk (R-1068) | „call me, we do it together" |
| A second disk on `virtio` cannot be formatted (R-1069) | use `sata` |
| The plugin pages are English | the guide uses their English words |

## 6. Rows, commits, clean-up

- **Register: 157 → 163.** Opened 6 (R-1068 to R-1073), closed 0.
- **Capability map:** new row A23, PARTIAL. `unproven.py`: unchanged (35 of 55 not walked).
- **Clean-up:**
  - Machine: the Felhom VM was switched off from its dashboard, then `omv-sim` and all its disks were destroyed. Yes.
  - Host: the browser container and the OMV ISO are removed. The nested setting was on before; I did not touch it. Yes.
  - Tester 1: started 17:16, ONLINE on the hub at 17:16:54, its guest runs. Yes.
  - Hub: Tester4 remains (yours to delete). No tunnel or DNS name was made. Nothing on ep0.
- **My mistake, recorded:** I first used low-level disk calls for the second disk. The box then sent two
  „Meghajtó váratlanul leválasztva" error events for Tester4. The dashboard's own „Csatlakoztatás" worked at once.
- **No product code changed.** No changelog entry: this repo has changelogs only for hub, scripts, website and
  marketing, and this run changed none of them.
- Secrets (passwords, the bind link, the codes, the owner phrase) stayed in the session's scratch folder. None is in a
  committed file.