HYPERVISOR
Your own metal, same control plane.
BETAProxmox and libvirt virtual machines managed with the same jobs, permissions and audit trail as everything else — and a VM you create can become a managed Talos server in one step.
THE MANUAL WAY
The gap between the rack and everything else.
THE SEPARATE TOOL
The Proxmox web UI is a different login, a different permission model and a different audit trail from everything else you run. Access to it is all-or-nothing.
THE TWO-STEP
Creating a VM and then making it a managed server is two disconnected processes, so the inventory is only as current as the last time someone remembered.
THE SNAPSHOT NOBODY TOOK
A change goes badly on a VM that had no snapshot, because taking one was a manual step in a runbook rather than part of the operation.
WHAT TALOS DOES
Virtual machines as tracked jobs.
Proxmox and libvirt
Two adapters behind one interface. Nodes, storage, networks and VMs inventoried from the hypervisor itself.
Lifecycle operations
Create, clone, start, stop and migrate VMs as jobs, each with live output and an audit entry.
Snapshots as part of the operation
Snapshot before a risky change as a step in the job rather than a line in a runbook someone skips.
Browser console
Reach a VM console without a separate hypervisor login or a VPN into the management network.
ISO and template management
Upload images and build from templates so the tenth VM of a shape matches the first.
VM to managed server
A VM you just created becomes a Talos-managed host in one action, with discovery run against it immediately.
HOW IT RUNS
Every action is a tracked job.
WHAT MAKES THIS DIFFERENT
The VM you just made is already a managed server.
On-premise virtualisation usually sits outside whatever tool manages everything else, so the inventory is stale by construction: a VM exists in the hypervisor for weeks before anything else knows about it. Talos closes that loop — creating a VM and registering it as a managed host is one flow, and discovery runs against it as soon as it boots.
RELATED CAPABILITIES
Connect one hypervisor, read-only.
This capability is new and has not been exercised against a wide range of hosts. Inventory first, changes later.