Lab 0C — HP Elitebook 2570p (16 GB) profile
Lab 0C — HP Elitebook 2570p · 16 GB RAM lab profile
Concrete profile for a spare HP Elitebook 2570p with 16 GB RAM, used as the single-server lab for this NixOS volume (Labs 0A + 0B on the same chassis).
The 2570p is ~2012 Ivy Bridge hardware. It is excellent as a quiet lab server for learning NixOS. It is not a modern workstation: respect thermals, disk, and CPU age.
Hardware snapshot (typical 2570p)
| Component | Typical | Lab implication |
|---|---|---|
| CPU | Intel Core i5/i7-3xxxM (Ivy Bridge) | 2 cores / 4 threads class; VT-x yes |
| RAM | Up to 16 GB DDR3 (you have 16 GB) | Comfortable for 1 heavy + 1 light VM |
| GPU | Intel HD 4000 | Fine for console/light desktop host; not GPU passthrough playground |
| Disk | Factory HDD or aftermarket SATA SSD | SSD strongly recommended |
| Display | 12.5” | Treat as headless-ish; external monitor helps |
| NIC | Intel wired + WiFi | Prefer Ethernet for long SSH sessions |
| Firmware | HP BIOS | Enable Virtualization Technology |
Exact CPU SKU varies (lscpu after boot). Confirm:
lscpu | rg -i 'Model name|Virtualization|CPU\\(s\\)|Thread'
free -h
lsblkBIOS checklist (do this first)
- Virtualization Technology (VTx) — Enabled
- VT-d — Enable if present (not required for basic KVM)
- Boot mode — UEFI preferred if disk allows; legacy OK for lab
- Disable unused boot devices if they slow POST
- Set fans/thermal to a sane default; keep vents clear
Save & reboot.
Disk strategy for this laptop
Best
| Disk | Use |
|---|---|
| Internal SATA SSD 512 GB+ | Host root + /nix + libvirt images |
| Optional USB3 SSD | Overflow images / backups |
Acceptable
| Disk | Use |
|---|---|
| Internal SSD 256 GB | Host + one VM; external for second VM images |
| HDD only | Usable but painful; prioritize SSD upgrade |
Partition sketch (NixOS host, single disk)
ESP 512 MB FAT32
root rest ext4 or btrfs
/nix (same FS is fine; optional subvol on btrfs)If dual-booting is tempting: don’t for this spare. Dedicate the machine to lab.
RAM budget (16 GB fixed)
| Consumer | Allocation | Notes |
|---|---|---|
| Host OS + desktop/ssh | 4–5 GB | Prefer lightweight DE or none |
| nixlab VM | 4–6 GB | Primary journey |
| deploy-a VM | 2 GB | Stop when idle |
| Headroom / browser | 2–3 GB | Close browser during big builds |
| Total | ≤16 GB | Never overcommit hard on this chassis |
Suggested virsh memory
# examples
# nixlab: 4096 or 6144 MiB
# deploy-a: 2048 MiBDuring Stage IV (DB + proxy + observability): prefer 6 GB nixlab and powered-off deploy-a unless needed.
CPU budget
| Setting | Value |
|---|---|
| nixlab vCPUs | 2 |
| deploy-a vCPUs | 1–2 |
Host nix.settings.max-jobs |
1–2 |
Host nix.settings.cores |
2 |
Ivy Bridge will thermal-throttle under sustained compile. That is normal—not a broken Nix.
What this machine is good for (curriculum map)
| Stage | On 2570p? |
|---|---|
| I Foundations | Yes |
| II One NixOS host (in VM) | Yes |
| III HM + layout | Yes |
| IV Secrets + small services | Yes (watch RAM) |
| V Packaging | Yes (be patient; use caches) |
| VI Deploy two VMs | Yes |
| VI k3s / heavy observability | Optional/light only |
| VII Internals | Yes |
| VIII Capstone | Yes (scope to hardware) |
| Nested libvirt | Avoid |
| Multi-node k8s + desktop | No |
Networking on the Elitebook
| Mode | Recommendation |
|---|---|
| WiFi only | OK for browsing; flaky for long rebuilds |
| USB Ethernet / dock | Preferred for lab evenings |
| Bridged VM to LAN | Optional; NAT default is safer |
Port-forwarding example (if you must reach a guest service from another PC): use host SSH tunnel rather than exposing VMs broadly.
ssh -L 8080:192.168.122.10:80 user@elitebook-hostPower & thermals
- Use AC power for builds and VM sessions
- Elevate rear for airflow if temps high
tlp/ power-profiles: on host, prefer performance when labbing on AC
- Expect fan noise under
nix build—plan quiet hours
Firmware & drivers notes
| Area | Note |
|---|---|
| WiFi | Prefer linux-firmware; some cards need allowUnfree for redistributable firmware |
| CPU microcode | hardware.cpu.intel.updateMicrocode = true; on NixOS host |
| GPU | Modesetting is enough; no NVIDIA complexity on stock 2570p |
| Fingerprint / WWAN | Ignore for lab |
| Ethernet | Older Intel NICs sometimes need offload disabled (ethtool -K …); put that in the host flake with a comment (pattern in Lab 0A Part 8), not only in a one-off root shell |
Host is fully yours (but still a lab)
On appliance hypervisors you are often discouraged from “messing with the host.” On NixOS host, you can install an editor, run a local cache, or attach a display—and still recover via generations. That does not mean the Elitebook should become your Stage IV app zoo. Keep metal useful; keep journey risk in VMs.
Concrete “day zero” procedure (you)
- Backup anything left on the 2570p.
- Install SSD if still on HDD (worth it).
- BIOS: enable VT-x.
- (Optional but wise) On another machine or live USB workflow: draft
hosts/elitebook-sim.nixand boot it as a VM first (Lab 0A “simulate host”).
- Install NixOS 26.05 as host (Lab 0A Option H1).
- Apply host config from git: libvirt or Incus (pick one primary), ssh, flakes, microcode, your user.
- Create nixlab (4–6 GB) + deploy-a (2 GB).
- Snapshot blank/fresh installs.
- Clone/create
~/src/nix-configflake (Lab 0B); commit host + guest stubs.
- SSH from your daily laptop into Elitebook; from Elitebook into VMs.
- Only then start Day 1.
Optional extras that fit this chassis
| Extra | Why |
|---|---|
| Automatic libvirt start | nixlab available after host boot |
External USB SSD labeled nix-lab |
Images + nix copy backups |
| UPS not required | Laptop battery is a mini-UPS for short blips |
| Second-hand 8 GB→16 GB already done | Good—don’t bother 32 GB (max 16 on this platform) |
| Replace thermal paste | Only if throttling is extreme |
What not to run on the 2570p
- Desktop + gaming + three 8 GB VMs
- Full Observability stack + k3s + browser on host simultaneously
- Treating host as wipe-target for Stage II installs (use nixlab)
- Expecting modern Secure Boot/TPM2 demos (Stage VI Secure Boot day may be document-only on this hardware)
For Lanzaboote/TPM chapters: complete theory + skip or use a newer machine if you have one later.
Elitebook readiness checklist
- 16 GB confirmed in
free -h
- VT-x enabled;
kvm-okor equivalent happy
- SSD or external fast disk for images
- Host NixOS (or Debian+Nix) installed
- libvirt works; nixlab defined
- RAM split written down and enforced
max-jobs≤ 2
- Ethernet or stable WiFi plan
- Lab 0A + 0B checklists done
- Wipe boundary: guests only
After this page
You are ready for Day 1 — Why Nix exists.
When Day 11 says “install NixOS,” install into nixlab (or replace its disk), not by reinstalling the Elitebook host unless you intentionally redesign Lab 0A.