Search
The Nodes, Guests and Storages lists have a search box, in both list and card view. It filters on name, description, tags and the other text columns at the same time, and on hostname when Show OS Info is on. The other grids filter by column.
Real-time inventory and operations, for the selected cluster, on every kind of Proxmox VE resource: clusters, nodes, guests, storage, networks, disks, partitions and snapshots.
The Nodes, Guests and Storages lists have a search box, in both list and card view. It filters on name, description, tags and the other text columns at the same time, and on hostname when Show OS Info is on. The other grids filter by column.
On Nodes, Guests and Storages, switch from List to Card layout to see all the resources at a glance. A card shows the status icon, the name, the health score, CPU / RAM / disk usage bars and the tags. Its arrow expands the same detail as the row of the list.
One health score, shown as a badge or a gauge, computed from CPU, memory, disk usage and resource type. A tooltip explains the score. The score goes from 0 to 100: 80 and above is Good, 60 to 79 is Warning, below 60 is Critical.
Start, shutdown, reboot, stop, reset, pause, resume, unlock or open a console without leaving the page. The buttons are in the Summary tab of a row's expanded detail. Snapshots are managed from the same expanded detail.
Open a NoVnc console for nodes, VMs and containers, or an Xterm.js console for nodes and containers, from the resource view.
Click a node name, VM ID, storage or snapshot to jump to its detail page. The cluster context is kept.
The Networks → Diagram tab draws an interactive SVG topology of nodes, bridges, VNets and guests, built with `cv4pve-api-dotnet`. You can save it for your documentation.
The Export button in the toolbar of the lists (nodes, guests, storages, networks, disks, partitions, snapshots, cluster logs) saves the list as an Excel file.
Why this view when PVE already shows resources per cluster?
Resources lists VMs, nodes, storage and snapshots of the whole selected cluster in one filterable grid.
The grids have multi-column sort, grouping, a column picker and free-text search. For example, find the one VM with prod in its tags among 200.
Start, stop or open a console without opening the page of the VM: expand the row and use the buttons of its Summary tab.
The Networks page shows bridges, bonds, SDN and the diagram in one place. PVE shows them split between the tabs of each node.
ip (dhcp) when the configuration says dhcp) · SDN (zones, VNets) · Diagram (interactive SVG topology)More columns than the default ones are available from the column picker of each list (tags, pool, lock, disk and network I/O, assigned CPU and memory, a link to the same resource in Proxmox VE, and others).
Expanding a row (or a card) on Nodes, Guests and Storages opens the detail of that resource, organised in tabs. Tabs and buttons that need a permission the user does not have are hidden.
| Resource | Tabs |
|---|---|
| Node | Summary · Performance · Replication · Disks · Task History |
| Guest | Summary · Config · Guest Info (QEMU only) · Performance · Task History · Backups · Replication · Snapshots |
| Storage | Summary · Performance |
The buttons at the top of the Summary tab run the actions on the resource:
Guest
Node
Every action except starting a guest and opening a console asks for confirmation.
Unlock and Memory Cleanup need the Power Management permission on that guest or node, and each run is recorded in the audit log.
Memory Cleanup flushes the page cache and compacts the memory of the node. It runs over SSH, so it needs the SSH credentials of the cluster.
The Snapshots tab of a guest creates, deletes and rolls back snapshots.
The Backups tab of a guest lists its backups on the storage chosen in the drop-down: the active storages of the node of the guest that hold backups.
snapshot, suspend or stop), Compression (None, ZSTD, GZIP or LZO), Protected and NotesNew, edit and Delete need VM: Backup manager on the guest; Restore File and Show configuration need VM: Backup Restore File.
Storages → Usage shows the space used on each storage, by storage or by guest.
Sizes can differ from real disk usage: On storages with compression or deduplication (PBS, ZFS, CEPH, Btrfs) the page shows uncompressed sizes, which can differ significantly from the disk space actually used.
In Networks → Diagram, Download saves the diagram as network-diagram-<cluster>.svg.
Enterprise enables snapshot size data on Resources:
Snapshot size calculation is switched on per cluster, in the Feature section of the cluster settings. The sizes are read from these storage types: ZFS (zfspool), Ceph RBD (rbd), LVM-thin (lvmthin), Btrfs (btrfs) and CephFS (cephfs). The values are cached for 5 minutes.
A snapshot removed in Proxmox VE can stay on the underlying storage: the removal does not always reach the dataset, and the space stays occupied. Proxmox VE no longer lists the snapshot, so nothing in its UI shows it. The disk looks fuller than the snapshots explain.
In Resources, the Snapshots tab of a guest lists these snapshots first, marked as orphans, with a warning that sums the space they hold. You cannot roll back, edit or delete them from here, because Proxmox VE has no snapshot to act on. To remove one, work on the storage directly, on the node. Snapshots created by storage replication are not reported as orphans.
Sizes are read per storage type. On ZFS the reported size is the space the snapshot actually occupies. On other backends it is currently an approximation.
Node console requires a PAM user: Node console (NoVnc, Xterm.js) requires the WEB API user to be a PAM user (e.g. root@pam). Users authenticated via other realms (PVE, LDAP, …) cannot open a node console because Proxmox VE requires OS-level authentication. The console button is disabled if the WEB API user is not a PAM user.
VM/CT console requires Credential authentication: VM and container console (QEMU, LXC) requires the WEB API to use Credential authentication (username/password). The console button is disabled when the WEB API is configured with API Token authentication, because Proxmox VE requires a user session to open a VM console.
The module gives 8 widgets to the Dashboard:
| Widget | Description |
|---|---|
| Resources Status | Shows the status of cluster resources |
| Resources Usage | Shows resource usage metrics |
| Cluster Usage Gauge | Arc gauges side by side for the CPU, memory, storage and snapshot usage of a cluster (the first one selected) |
| Cluster Usage Gauge Stacked | The same values as concentric rings in one gauge |
| Cluster Usage Grid | Grid view of cluster usage metrics |
| Clusters Maps | Geographic map with one pin per cluster |
| VM/CT Locked | Shows VMs and containers in locked state |
| Nodes Status | The offline nodes, with the number of nodes online |
The module has no settings. Each page has its own permission:
| Permission | Key | Grants |
|---|---|---|
| Resources | Status.Link |
Access to the module and to its Overview page |
| Cluster | Status.Link.cluster |
Cluster page |
| Nodes | Status.Link.nodes |
Nodes page |
| Guests | Status.Link.guests |
Guests page |
| Storages | Status.Link.storages |
Storages page |
| Networks | Status.Link.networks |
Networks page |
| Disks | Status.Link.disks |
Disks page |
| Partitions | Status.Link.partitions |
Partitions page |
| Snapshots | Status.Link.snapshots |
Snapshots page |
The built-in role Admin for module Resources includes all of them, together with one permission per dashboard widget of the module (Status.Widget.<widget>).
Inside the pages, the cluster permissions of the user decide which nodes, guests and storages are listed and which actions are offered on them (power management, console, snapshots, backups, replication, audit). This holds also for Disks, Partitions, Snapshots and the Networks tabs and diagram, which show only the readable nodes, guests and storages; the SDN tab, a setting of the whole cluster, needs Read on every VM, node and storage of the cluster. Without it the Diagram also leaves out the VNets.
Roles and permissions are assigned in Admin Area → Security EE.
Proxmox VE privileges: the base (PVEAuditor) plus the following, each one only for its action.
| Privilege | Used for |
|---|---|
VM.PowerMgmt | Start, stop, shutdown, reboot, reset, suspend, resume a guest |
VM.Console | Guest console |
VM.Snapshot | Create, edit, delete a snapshot |
VM.Snapshot.Rollback | Roll back a snapshot |
VM.Replicate | Replication: Schedule Now |
VM.Backup, Datastore.AllocateSpace | Backups tab: list, configuration and deletion of backups |
Sys.Console | Node console |
Sys.PowerMgmt | Shut down, reboot a node |
The base and the rules common to all modules are in Proxmox VE Permissions.