pve_delete_guest
Permanently destroy a Proxmox guest and its disks, with dry-run planning to review cascade effects on backups, HA, and replication before confirmation.
Instructions
MUTATION (DESTRUCTIVE, IRREVERSIBLE): permanently destroy a guest and its disks. Dry-run by default — the PLAN names exactly what will be destroyed, including cascade effects on backup/ HA/replication references. confirm=True to execute. Async — returns the task UPID; poll with pve_task_status. No undo once confirmed.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Guest type: `lxc` for a container or `qemu` for a VM. | lxc |
| node | No | PVE node the guest runs on. Omit to resolve it automatically from the cluster. | |
| vmid | Yes | Numeric ID of the guest to destroy — VMID for a QEMU VM or CTID for an LXC container. | |
| force | No | Force removal even if the guest is still running or the backend reports an inconsistent state. | |
| purge | No | If true, also remove the guest from replication/backup jobs and HA resources referencing it. | |
| confirm | No | Leave `false` (default) to get a dry-run PLAN naming exactly what will be destroyed; set `true` to execute. | |
| proximo_target | No | Which configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |