[GH-ISSUE #366] Issue creating QEMU VMs with Pool scoped users or API tokens #89

New issue

Closed

opened 2026-02-28 00:40:31 +03:00 by kerem · 1 comment

kerem commented

2026-02-28 00:40:31 +03:00

Owner

Originally created by @mpywell on GitHub (Oct 16, 2024).
Original GitHub issue: https://github.com/Telmate/proxmox-api-go/issues/366

After the Pool config refactor QEMU VMs are created against /vms then moved into /pool/%s if a Pool is configured.

Pools are often used in hosted or enterprise Proxmox environments to scope user or API Token access , to avoid seeing/modifying the VMs of other users or teams.

VMs cannot be created without giving access to /vms after #335 .

Configured Pools need to be passed into API requests to /nodes/%s/qemu to resolve the issue.

Originally created by @mpywell on GitHub (Oct 16, 2024). Original GitHub issue: https://github.com/Telmate/proxmox-api-go/issues/366 After the Pool config refactor QEMU VMs are created against `/vms` then moved into `/pool/%s` if a Pool is configured. Pools are often used in hosted or enterprise Proxmox environments to scope user or API Token access , to avoid seeing/modifying the VMs of other users or teams. VMs cannot be created without giving access to `/vms` after #335 . Configured Pools need to be passed into API requests to `/nodes/%s/qemu` to resolve the issue.