Two sweeps:
1. .30 is a PHYSICAL box (Lenovo ThinkCentre M83, Ubuntu 26.04), not a Jupiter
VM — the VM was decommissioned 2026-06-12. Fixed inventory tables and the
gururmm-build system page (overview, index, jupiter, gururmm-build,
POWER_FAILURE_RUNBOOK).
2. Windows build chain: Beast (GURU-BEAST-ROG, tailnet 100.101.122.4, i9-14900K)
is PRIMARY; Pluto (172.16.3.36) is FALLBACK. Verified against build-windows.sh
(`attempt_build beast || attempt_build pluto`). Fixed overview, index,
projects/gururmm (build-host table + flow + host detail), systems/pluto, and
the reference_pluto_build_server memory.
Submodule advanced: build-pipeline doc comments corrected to match.
NPM → 443 routing: iptables PREROUTING rule on Jupiter: dpt:443 → 172.17.0.2:443 (NPM Docker bridge IP). Persisted in /boot/config/go so it survives reboots.
Virtual Machines (virsh)
VM
IP
State
Role
GuruRMM
172.16.3.30
decommissioned 2026-06-12
Former GuruRMM VM — migrated to a physical box that took the .30 IP (2026-06-11); virsh domain destroyed + disk deleted 2026-06-12. No longer on Jupiter.
Claude-Builder (Pluto)
172.16.3.36
running
Windows Server 2019 — MSI + cargo builds
OwnCloud
172.16.3.22
running
OwnCloud file sync VM (cloud.acghosting.com)
Unifi
(IP not documented)
running
UniFi Network controller
Windows 7
—
shut off
—
Windows Server 2016
(none — APIPA)
running
Windows guest ACG-DWP-X-BB; e1000 NIC vnet8 on br0, DHCP not leasing — see Known Issues
iptables PREROUTING for port 443 persists via /boot/config/go — if NPM routing breaks after a reboot, check this file first.
iDRAC IP is DHCP (172.16.1.73) — may drift. Verify before relying on it for OOB access.
guruRMM API proxy stale — see NPM table above. Fix before it causes a routing incident.
Post-power-failure recovery order matters — see .claude/POWER_FAILURE_RUNBOOK.md for the full recovery sequence (Tailscale routes, libvirt/VMs, Seafile, NPM/DNS in order).
VM "Windows Server 2016" (ACG-DWP-X-BB) — no LAN (2026-06-07): guest stuck on APIPA 169.254.157.152, no DHCP lease. Host side is healthy (vnet8 bridged to br0, forwarding, receiving LAN broadcast); fault is guest-side — single e1000 NIC set to DHCP, pfSense (172.16.0.1) not leasing it. Diagnose via virsh domifaddr 9 --source agent and qemu guest-exec ipconfig /all. Fix path: ipconfig /renew in-guest (stuck-client case) or assign a static IP if that is the intended config. PAUSED pending Mike's DHCP-vs-static decision.
Backlinks
systems/gururmm-build — GuruRMM was a VM here (virsh domain "GuruRMM"); decommissioned 2026-06-12, now a physical box at 172.16.3.30
systems/pluto — Claude-Builder VM hosted here (virsh domain "Claude-Builder")