project console vm cpu cores pending restart 20260715T111619

---

name: Console (VM 103) has 12 cores configured but guest still sees 8, needs full stop/start description: Proxmox qm config 103 already shows cores: 12 for Console, but the guest is running on 8; applying it requires a full VM stop/start, not an in-guest reboot. type: project

---

As of 2026-07-15, qm config 103 on Finn already has cores: 12 set for Console (VM 103), but the guest currently only sees 8 cores. This is a Proxmox limitation: changing vCPU count only takes effect on a full qm shutdown 103 && qm start 103, an in-guest reboot does not re-negotiate the CPU topology.

Why: this session and all its workers/tmux sessions live on Console, so doing the restart is disruptive and needs the reboot-preflight steps (tmux socket wipe risk, per [[reference_reboot_preflight_tmux_socket_wipe]]) before executing.

How to apply: next time Justin wants the 12th core (or asks why Console still looks like 8 cores), the fix is already configured host-side, just needs a scheduled qm shutdown 103 && qm start 103 from Finn with the reboot-preflight checklist run first, not a reboot from inside Console.

[auto-memory session 60d132de-4659-485c-8044-427af0ccce7f, confidence 0.68, mode staged]