Zum Inhalt springen
Produkte

// Benutzung · Steuerung

Controlling a Proxmox VM

Start, stop, reboot, or shut down a VM (or CT) from the admin UI. Every action is dispatched to the location's agent, run against the live Proxmox API, and written to the control audit log.

Requires the control.execute permission (the built-in admin role has it; operator/viewer don't).

Per-VM controls

  1. Open the location → Resources tab.
  2. Under Discovered, each Proxmox VM card has four buttons: Start, Reboot, Shutdown (graceful), Stop (force off).
  3. Click one → confirm in the dialog (it names the VM and action) → the action is dispatched. Status refreshes automatically within a second or two.

Buttons are disabled while the location's agent is unreachable (nothing could carry the command).

Containers (LXC) are listed as Proxmox VMs too, and the same buttons work on them. Before acting, the agent asks Proxmox (/cluster/resources) whether the VMID is a VM or a container and sends the action to the matching endpoint, on the node Proxmox reports the guest on now (so a guest migrated since it was discovered is still reached). If Proxmox does not list the guest, the action is refused and nothing is sent. A container cannot be reset (Proxmox has no reset for containers); use Reboot.

Bulk actions

Tick the checkboxes on several VMs, then use the Start / Reboot / Shutdown / Stop bar above the grid. One confirmation lists every selected VM, then the action is sent to each; a summary reports per-VM success/failure.

The audit log

Every action — single or bulk — is recorded: open the Agents tab → Control path to see who ran what, when, and the result. Reading it needs control.view.

Prerequisite: the Proxmox token needs power privileges

Fleeger talks to Proxmox with the API token stored on the Proxmox node resource's credential. A token created for monitoring only has audit rights (see creating the read-only monitoring token), so a power action comes back 403 Forbidden. Grant the token VM.PowerMgmt and VM.Audit on the node/VMs (least privilege). VM.Audit is needed because the agent first looks the guest up in Proxmox to tell a VM from a container; a token with VM.PowerMgmt alone gets "guest N is not listed". For example, a custom role:

# on a Proxmox node, as root — replace with your Fleeger token id
pveum role add FleegerControl -privs "VM.Audit VM.PowerMgmt Sys.Audit Datastore.Audit"
pveum acl modify / --tokens 'user@realm!tokenid' --roles FleegerControl --propagate 1

On Proxmox 8, not 9? Older guides added VM.Monitor to this privilege list. PVE 9.0 removed the VM.Monitor privilege (basic monitor access is now covered by Sys.Audit), so including it makes the pveum role add above fail on a PVE 9 host — leave it out. The list above works on both 8 and 9, and covers everything Fleeger's power path (start/stop/reset/…) calls. See required permissions by Proxmox version.

If the token has Privilege Separation enabled, the permission must be granted to the token itself, not just its user. The built-in PVEVMAdmin role also works but is broader than needed.

// Zusammenarbeit

Bereit, Ihre digitale Infrastruktur zu bauen?

Ob individuelle Automatisierung für Ihr Unternehmen oder ein durchgeplantes Netzwerk für Ihr Zuhause — lassen Sie uns über das Projekt sprechen.