pve_disk_move
Move a guest disk to another storage. Dry-run shows source→target plan; set confirm=true to execute. Use delete_source with caution as it removes the original copy.
Instructions
MUTATION: move a guest disk to another storage. Dry-run by default — the PLAN shows source->target and whether the source copy is deleted (delete_source=True is HIGH, no easy undo). confirm=True to execute. Async — returns a task UPID (poll with pve_task_status). To grow a disk in place instead of relocating it use pve_disk_resize.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| disk | Yes | Disk key to move, e.g. `scsi0` or `rootfs`. | |
| 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 — VMID for a QEMU VM or CTID for an LXC container. | |
| confirm | No | Leave `false` (default) to get a dry-run PLAN; set `true` to execute the move. | |
| delete_source | No | If true, delete the source copy after the move (HIGH risk); if false (default), keep it. | |
| 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. | |
| target_storage | Yes | Storage backend name to move the disk to. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |