- 1 Links
- 2 Documentation
- 3 Monitoring proxmox with zabbix
- 4 FAQ
- 4.1 Clustering
- 4.2 Cores, sockets and vCPUs
- 4.3 Check if qemu agent is running
- 4.4 Stop all proxmox services
- 4.5 switch to community repository
- 4.6 W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!
- 4.7 Backups
- 4.7.1 proxmox-backup-client
- 4.7.2 dirty-bitmap status: existing bitmap was invalid and has been cleared
- 4.7.3 unexpected property 'prune-backups' (500)
- 4.7.4 FAILED 00:00:02 unable to activate storage
- 4.7.5 VM 101 Backup failed: VM is locked (snapshot)
- 4.7.6 can't acquire lock '/var/run/vzdump.lock' - got timeout
- 4.7.7 VM 101 Backup failed::= VM is locked (snapshot-delete)
- 4.8 Error: VM quit/powerdown failed - got timeout
- 4.9 a used vhost backend has no free memory slots left
- 4.10 You have not turned on protection against thin pools running out of space.
- 4.11 serial console from command line
- 4.12 enable serial console in guest
- 4.13 TASK ERROR: command 'apt-get update' failed: exit code 100
- 4.14 Import vmdk to lvm
- 4.15 Can't apply changes to memory allocation
- 4.16 Adding hardware shows orange
- 4.17 "Connection error 401: no ticket"
- 4.18 can't lock file '/var/lock/qemu-server/lock-102.conf' - got timeout (500)
- 4.19 The current guest configuration does not support taking new snapshots
- 4.20 WARNING: Device /dev/dm-21 not initialized in udev database even after waiting 10000000 microseconds.
- 4.21 "connection error - server offline?"
- 4.22 Find vm name by id
- 4.23 Started Proxmox VE replication runner.
- 4.24 Find ID by name
- 4.25 Can't migrate VM with local CD/DVD
- Proxmox VE Administration Guide
- https://pve.proxmox.com/wiki Wiki
- Monitoring Proxmox with Zabbix
- Proxmox Backup Server
- Backup and Restore
pvecm status pvecm nodes
Monitoring proxmox with zabbix
Proxmox API call failed: Couldn't authenticate user: zabbix@pve
Funky characters in password string?
Show cluster status
corosync-qdevice: Can't read quorum.device.model cmap key
On the third/quorum node
And "Quorum: 2 Activity blocked"
In my case this meant boot up second real node
Shutting down a node
Should just work. Takes guests down with it when they're not in HA
Cores, sockets and vCPUs
vCPUs is what the vm uses, equals sockets*cores
Check if qemu agent is running
See if IP is shown under Summary, also
qm agent 105 ping
Stop all proxmox services
systemctl stop pve-cluster systemctl stop pvedaemon systemctl stop pveproxy systemctl stop pvestatd
switch to community repository
cat /etc/apt/sources.list.d/pve-enterprise.list #deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise
echo "deb http://download.proxmox.com/debian/pve buster pve-no-subscription" > /etc/apt/sources.list.d/pve-no-subscription.list
W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!
cehck sources.list :)
proxmox-backup-client snapshot list
proxmox-backup-client prune vm/101 --dry-run --keep-daily 7 --keep-weekly 3
dirty-bitmap status: existing bitmap was invalid and has been cleared
unexpected property 'prune-backups' (500)
When for example Add: iSCSI Uncheck "Keep all backups" in "Backup retention"
FAILED 00:00:02 unable to activate storage
VM 101 Backup failed: VM is locked (snapshot)
Check if there's no snapshot running (how?)
qm unlock 101
can't acquire lock '/var/run/vzdump.lock' - got timeout
Check if vzdump is running, otherwise kill it (cluster?)
VM 101 Backup failed::= VM is locked (snapshot-delete)
Check /etc/pve/qemu-server/101.conf for 'snapstate'
If that says 'delete' for a snapshot try deleting the snapshot:
qm delsnapshot 101 snapname
If that throws like Failed to find logical volume 'pve/snap_vm-101-disk-0_saving'
qm delsnapshot 101 snapname --force
to get it out of 101.conf
Error: VM quit/powerdown failed - got timeout
qm stop VMID
if that complains about lock, remove the lock and try again
a used vhost backend has no free memory slots left
You have not turned on protection against thin pools running out of space.
serial console from command line
qm terminal <id}
enable serial console in guest
looks like this is not needed:
systemctl enable serial-getty@ttyS0.service
ttyS0 is for qm terminal, tty0 is for the "console" buttion in UI
- debian based
- redhat based
to /etc/pve/qemu-server/[vmid].conf and restart
agetty: /dev/ttyS0: not a device
systemctl status useless again, means the serial bit is missing from <vmid>.conf
TASK ERROR: command 'apt-get update' failed: exit code 100
subtle way of telling you to get subscription of at least change the sources list
Import vmdk to lvm
Can't apply changes to memory allocation
Maybe try enabling NUMA in CPU settings
Adding hardware shows orange
something is not supported (Options->Hotplug)
"Connection error 401: no ticket"
Login session expired?
can't lock file '/var/lock/qemu-server/lock-102.conf' - got timeout (500)
Maybe someone else has/had webui open
== TASK ERROR: Can't use string ("keep-all=0,keep-last=3") as a HASH ref while "strict refs" in use at /usr/share/perl5/PVE/VZDump.pm line 502. ==
Classic, means incorrect syntax in your /etc/pve/storage.cfg
The current guest configuration does not support taking new snapshots
You're using raw instead of qcow2. Convert: Hardware->Hard disk "Move Disk"
WARNING: Device /dev/dm-21 not initialized in udev database even after waiting 10000000 microseconds.
Until someone fixes it:
"connection error - server offline?"
Try reconnection browser
Find vm name by id
grep name /etc/pve/nodes/*/qemu-server/101.conf |head -n 1
Started Proxmox VE replication runner.
Find ID by name
grep -l "name: <NAME>" /etc/pve/nodes/*/qemu-server/*conf| sed 's/^.*\/\([0-9]*\)\.conf/\1/g'
Can't migrate VM with local CD/DVD
Remove the CD :)