21 Commits
Author SHA1 Message Date
ari ed558a196f ensuring only relevant access is provided 2026-10-26 12:26:19 -04:00
ari 5b2621acbc networking tests 2026-10-11 00:59:32 -04:00
ari f1622fae84 splitting host.nix 2026-10-10 22:56:24 -04:00
ari 30427e3975 doc clean 2026-10-09 14:35:12 -04:00
ari 32edfbd111 added flags for virt devices 2026-09-29 11:33:33 -04:00
ari d5afd6510f safer bridge mode 2026-09-23 19:29:28 -04:00
ari 42e903909c fixing test failures 2026-09-23 13:24:07 -04:00
ari c8ff8b1f25 simpler derivation 2026-09-18 12:33:33 -04:00
ari a538f70bf7 another attempt at fixing it 2026-09-17 17:27:56 -04:00
ari 4313e043bc fixing nats 2026-09-17 17:00:35 -04:00
ari 2d35fd973c detailed versioning + no dest 2026-09-17 15:29:06 -04:00
ari d47c401013 hooks + devenv 2026-09-17 14:14:14 -04:00
ari 45d2d9e489 completions 2026-09-17 12:35:04 -04:00
ari 21e87b6bfa new single file with fixes 2026-09-17 12:15:53 -04:00
ari f5f6a98152 all nuing with versions 2026-09-16 22:15:07 -04:00
ari 1e1da2f7a1 all nuing 2026-09-16 22:09:42 -04:00
ari e5f150b17e fixed issue with networking 2026-09-16 11:40:45 -04:00
ariandClaude Sonnet 5 5ea64e88d5 Fix two disk-setup bugs: byte/gigabyte size mix-up, wrong ownership
1. truncate -s treats a bare number as bytes, not gigabytes - typing
   "50" at the size prompt (instead of "50G") silently made a 50-byte
   file, which then failed mkfs.ext4 with "Device size reported to be
   zero." Added normalize-size: a bare integer answer now gets a "G"
   suffix appended (matching what the prompts' own defaults imply),
   anything with an existing suffix passes through unchanged.

2. Every disk-creation step runs through `priv` (sudo/root), so
   subvolumes and disk images always ended up root-owned - but
   hermes-vm.service runs as the unprivileged hermes-vm account, which
   only had read access via the "other" bits. QEMU failed to open
   system.raw for read-write. Added explicit `chown hermes-vm:hermes-vm`
   after every creation point (both make-subvol branches, and after
   each truncate/mkfs) - also self-heals already-existing
   wrongly-owned disks on a re-run, not just fresh ones.

Both confirmed live on hl-fwdesk during tonight's incident. Verified
with a unit test of normalize-size and a full sandboxed interactive
dry run of `setup` (fake sudo/btrfs/truncate/chown/mkfs.ext4) showing
the correct truncate -> chown ordering for both disks.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-15 22:33:09 -04:00
ariandClaude Sonnet 5 d961d38974 Fix hermes-vm.service crash-loop: drop mismatched multi_queue tap flag
QEMU's -netdev tap line never requests queues=N, so a persistent tap
created with `multi_queue` fails TUNSETIFF with EINVAL on every attach
attempt ("could not configure /dev/net/tun: Invalid argument"),
crash-looping the VM indefinitely. Confirmed live on hl-fwdesk via
`ip tuntap show` (tap flagged multi_queue, numqueues 0 - never
successfully attached).

vhost is already off in this design, so multiqueue bought nothing here
anyway - just drop the flag from tap creation instead of adding
matching queues= plumbing.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-15 14:33:39 -04:00
ariandClaude Sonnet 5 2b33b98bae Rename project to hermenix; convert host scripts to a Nu CLI
services.hermesVm -> services.hermenix throughout. setup.sh and
migrate-docker-hermes.sh are replaced by nu/hermenix.nu (setup + migrate
subcommands), packaged as a flake output (packages.${system}.hermenix,
pkgs.writers.writeNuBin) so it's installable without cloning conventions
beyond the repo itself. Both subcommands verified end-to-end against a
sandboxed dry run (stubbed disk/cache tools, a local ssh stand-in for the
migrate path) before landing.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-15 13:26:18 -04:00
ariandClaude Sonnet 5 12227460fd Initial hermex: Hermes Agent in a hardened, self-managing NixOS VM
Two-disk (system/state) btrfs-backed QEMU VM, nftables-isolated by default,
adapted from a design provided as loose files. Adds a hermesHome option to
the host module and migrate-docker-hermes.sh so an existing flat HERMES_HOME
(e.g. from a prior Docker deployment) can be carried over intact.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-15 12:20:45 -04:00