Proxmox 9.0.3 "Requires 'VM.Monitor' Privileges" in Summary instead of listing IP addresses

F

fransesco

Member
Jun 16, 2022
15
2
8
Hello everyone,

I upgraded from 8 to 9 without any major issues, but after getting my VM's running none of them are showing their IP addresses anymore in the summary. Instead, it says
"Requires 'VM.Monitor' Privileges" instead. All other statistics like CPU, mem etc are showing as expected.

By searching the forum this was mentioned few times in the beta discussion chain, but I couldn't really see if there was a proper answer for this.

Has anyone else seen the same or found a fix for it?
 
SteveITS said:
VM.Monitor was removed: https://pve.proxmox.com/wiki/Roadmap
Click to expand...
I see... However Proxmox should tell more in detail what to do in order to show VM's ip address in 9.x's Summary box. It's kind of out-of-box feature. The roadmap doc telling it's replaced by Sys.Audit doesn't tell too much how to migrate.

And also the user in question (root in my case), seems to have Sys.Audit permissions by default. So, if root has Sys.Audit permissions, why the ip address isn't shown in the summary..?
 
Last edited:
Landed here for same issue. Ctrl-F5 and it shows. Was going crazy figuring out why 1 of 3 nodes was doing this. Thank you all.
 
  • Like
Reactions: Janko
Same issue, but clearing browser cache, Ctrl+F5, or even using another browser, with even a different user account than root. Still just shows "Requires 'VM.Monitor' Privileges" in the summary window for the IP of my VMs accept for those that are off which then it says, "Guest Agent not running" instead.
 
Hi,
beldred said:
Same issue, but clearing browser cache, Ctrl+F5, or even using another browser, with even a different user account than root. Still just shows "Requires 'VM.Monitor' Privileges" in the summary window for the IP of my VMs accept for those that are off which then it says, "Guest Agent not running" instead.
Click to expand...
please post the output of pveversion -v for the node you are connected to.
 
pve01 is the one system having the issue. My other system pve02 in the same cluster isn't have the issue.

Code: 
root@pve01:~# pveversion -v
proxmox-ve: 9.0.0 (running kernel: 6.14.8-2-pve)
pve-manager: 9.0.3 (running version: 9.0.3/025864202ebb6109)
proxmox-kernel-helper: 9.0.3
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
proxmox-kernel-6.14: 6.14.8-2
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8: 6.8.12-13
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
amd64-microcode: 3.20250311.1
ceph-fuse: 19.2.3-pve1
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.9
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.3
libpve-network-perl: 1.1.6
libpve-rs-perl: 0.10.7
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2
lxc-pve: 6.0.4-2
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.9-1
proxmox-backup-file-restore: 4.0.9-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.1.1
proxmox-kernel-helper: 9.0.3
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.0
proxmox-widget-toolkit: 5.0.4
pve-cluster: 9.0.6
pve-container: 6.0.9
pve-docs: 9.0.7
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.16-3
pve-ha-manager: 5.0.4
pve-i18n: 3.5.2
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.16
smartmontools: 7.4-pve1
spiceterm: 3.4.0
swtpm: 0.8.0+pve2
vncterm: 1.9.0
zfsutils-linux: 2.3.3-pve1
 
beldred said:
pve01 is the one system having the issue. My other system pve02 in the same cluster isn't have the issue.
Click to expand...
What does grep VM.Monitor /usr/share/pve-manager/js/pvemanagerlib.js say? If there is output, then the package is not installed correctly and you should run apt install --reinstall pve-manager and reload the UI, if there is no output, that means that the browser is not using the current version.
 
Code: 
root@pve01:~# grep VM.Monitor /usr/share/pve-manager/js/pvemanagerlib.js
        if (!caps.vms['VM.Monitor']) {
            me.updateStatus(false, Ext.String.format(errorText, 'VM.Monitor'));
        if (caps.vms['VM.Monitor'] && !template) {

Edit: When logging into pve02 and running the same I get nothing back.
 
Last edited:
You must log in or register to reply here.
Top Bottom