ProxMox Notes, Settings & Solutions to Issues

Proxmox CLI Quick Reference

Backup VM through CLI to a Proxmox Backup Server Storage

vzdump VMIDNUM -storage PBS-UNRAID

Force Shut Down Non-Responsive VM

# Option 1:
qm shutdown VMIDNUM --forceStop --skiplock

## Option 2: Really FORCE it
qm list
# And then: 
kill -9 PROCESSIDFROMQMLIST

Unlock VM

Happens if backup fails or gets cancelled ungracefully
https://community.spiceworks.com/how_to/17877-proxmox-vm-locked

qm unlock VMNUMBER

Start Windows VM in safe mode

F8 key while system is booting up
- If not working: possible workaround: https://forum.proxmox.com/threads/how-to-enter-safe-mode-in-windows-2003-f8-does-not-work.20031/

Best Practices and Performance Tweaks

Arch Linux (EndevourOS):

No DE:
- EOS-Installer needs at least 2 GB ram to install, 10 GB of Storage for easy Swap creation (No Hibernate) (Arch will use up 5GB)
  - When installing, set static IP through XFCE to save work later
https://forum.proxmox.com/threads/cpu-type-host-vs-kvm64.111165/
- use HOST as CPU for better performance. (Keep in mind, VM will most likely CRASH after doing live migration due to hardware differences)

Windows:

https://pve.proxmox.com/wiki/Performance_Tweaks
https://pve.proxmox.com/wiki/Windows_10_guest_best_practices
https://forum.proxmox.com/threads/cpu-type-host-vs-kvm64.111165/
- use HOST as CPU for better performance. (WILL possibly CRASH after doing live migrate though)

Install qemu-guest-agent on Ubuntu

https://www.snel.com/support/nstall-qemu-guest-agent-for-debian-ubuntu/

sudo apt update && apt -y sudo install qemu-guest-agent

Expanding VM Storage

Depending on the VM OS, the extra disk space can show up after the next reboot, or you will have to manually expand the partitions
- Windows and EndevourOS automatically recognize the extra disk space. You just have to expand it within Disk Management/gparted
https://kb.vander.host/disk-management/how-to-enlarge-an-ext4-disk-on-an-ubuntu-proxmox-vm/

Changing VM IDs

https://samuel.kadolph.com/2020/11/change-proxmox-vm-id-with-zfs-root-storage/
- Need to test if this works

VMWare ESXI Migration

From VmWare ESXI, shutdown Virtual Machine, export is as a .ova template file to location ProxMox can access it, Extract the .ova file with 7zip to get contents and then import the .vmdk file to ProxMox virtual machine using steps:
https://www.itsfullofstars.de/2019/07/import-ova-as-proxmox-vm/
qm importdisk VMIDNUM VMDKFILENAME.vmdk local-lvm -format qcow2

- https://www.reddit.com/r/Proxmox/comments/i4ogy2/comment/i1v7rin/?utm_source=share&utm_medium=web2x&context=3

sed -Ezi.bak "s/(Ext.Msg.show\(\{\s+title: gettext\('No valid sub)/void\(\{ \/\/\1/g" /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js && systemctl restart pveproxy.service

Ran into this issue when i changed one of the node’s IP addresses. once the node rebooted, no longer able to login through WebUI. SSH worked fine though.
https://forum.proxmox.com/threads/proxmox-ve-login-failed-please-try-again.55488/page-2

systemctl stop pve-cluster corosync
pmxcfs -l
rm /etc/corosync/*
rm /etc/pve/corosync.conf
killall pmxcfs
systemctl start pve-cluster

Get Sensor Info

https://forum.proxmox.com/threads/temperature.67755/

apt install xsensors ; sensors

ZFS storage on root disk

https://www.reddit.com/r/HomeServer/comments/vxgut2/should_i_still_use_a_separate_boot_drive_for/

Migrating Virtual Disks Between VMs

https://dae.me/blog/2340/how-to-add-an-existing-virtual-disk-to-proxmox/

/mnt/pve/<STORAGE_ID>/

https://pve.proxmox.com/wiki/Storage:_CIFS

ProxMox Networking

View list of network cards and Status

ip -c a

permission denied - invalid PVE ticket (401) error

Usually due to system time mismatches between nodes.
https://forum.proxmox.com/threads/3-node-cluster-permission-denied-invalid-pve-ticket-401.56038/
SSH into nodes having issue and restart following services:

systemctl restart pvedaemon pveproxy

Changing VM IDs

https://samuel.kadolph.com/2020/11/change-proxmox-vm-id-with-zfs-root-storage/
- Need to test if this works

Replacing Failing/Failed Drive in ZFS Array

https://blog.fahadusman.com/proxmox-replacing-failed-drive-in-zfs-pool/

Config Locations

Unknown option “Affinity” error when trying to increase Core/Socket count for VM

Parameter verification failed. (400)
delete: unknown option 'affinity'

Solution: Update all nodes in cluser and do a restart

- This is from a package version incompatability between nodes
- https://forum.proxmox.com/threads/unknown-option-affinity.119038/

Cannot Change Display Resolution for Windows VM in ProxMox

If needing the ability to change display resolutions for Windows Virtual Machine, set Display to virtIO-GPU under Hardware
Then install the virtio Display drivers through device manager. (Add virtio drivers as CD in VM hardware)

ProxMox Hard Disk Speed Comparisons (IDE/SATA/VIRTIO/VIRTIO SCSI)

Removing Proxmox Node From Cluster

https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_remove_a_cluster_node
https://forum.proxmox.com/threads/deleted-cluster-node-still-shows-up-in-my-gui.11614/ Sometimes the node will still appear in the GUI after it’s been deleted. To fix, delete it’s directory in /etc/pve/nodes/

Last updated on July 09, 2024. For any questions/feedback, email me at blog@zinchuk.xyz.

Yuriy's Notes