Global VMs

Purpose

• See all VMs across the active root account and every descendant account in one inventory.
• Identify each VM's owning account, cluster, host, and Proxmox ID.
• Open a read-only detail view (Details, Monitoring, Backup, Logging) for any account's VM.
• Live-migrate one or more VMs to another host in the same cluster.

Prerequisites

• Available to root accounts only; the Platform section is hidden for non-root accounts.
• Minimum permission to view: platform.globalvms.read
• Permission to migrate a VM: platform.globalvms.update
• Global VMs is a read-only inventory: VMs are not created or deleted here (do that from Compute → Virtual Machines).

View global VMs

1. Open Platform → Global VMs (root account only).
2. Review the columns: Name, Account, Cluster, Host, and Proxmox ID.
3. Select a single running VM and choose Connect to open its console.
4. Expected result: the inventory lists VMs across the active account and all descendant accounts.

Open a VM's detail view

1. Open Platform → Global VMs (root account only).
2. Click a VM name to open its detail view.
3. Switch between the Details, Monitoring, Backup, and Logging tabs.

These tabs are read-only and do not switch your active account; make changes from the VM's own account.

Migrate VMs

1. Open Platform → Global VMs (root account only).
2. Select one or more VMs that all belong to the same cluster.
3. Choose Migrate VM (shown only with platform.globalvms.update).
4. On the Migrate VMs page, review the selected VMs, then pick a Target node.
5. Choose Migrate to queue the migration.
6. Expected result: one migration job is queued per VM and appears in the Task Manager.

Only online hosts in the selection's cluster that aren't already running a selected VM can be chosen; if none remain, or the selection spans clusters, Migrate is unavailable.

Best Practices

• Migrate within a single cluster — Proxmox cannot migrate a VM across clusters.
• Track queued migrations in the Task Manager; a rejected VM produces no task, so re-check any that fail to queue.
• Use the Account column to confirm a VM's owner before acting on cross-account VMs.