When creating snapshot failed, the snapshot can not be deleted via GUI.
qm unlock <vm_id>Use snapshot name to create for each vm disk
zfs snapshot -r <disk_zvol>@<snapshot_name>zpool import <existing_pool_name> <new_pool_name>Create storage via GUI
You have to connect to the node where you create the zpool to create storage in Proxmox Datacenter.
ZFS Pool Import - Proxmox single host reinstall without full backup
zpool not shown when add storage
pve-ssl.pem is emptyGot following error when starting a Proxmox VM with Spice driver.
kvm: warning: Spice: reds.c:2893:reds_init_ssl: Could not load certificates from /etc/pve/local/pve-ssl.pem
kvm: warning: Spice: error:0909006C:PEM routines:get_name:no start line
kvm: warning: Spice: error:140DC009:SSL routines:use_certificate_chain_file:PEM lib
kvm: failed to initialize spice server
TASK ERROR: start failed: QEMU exited with code 1pve-ssl.pem sizeThe file size of /etc/pve/local/pve-ssl.pem is 0.
Regenerate following files using method stated in https://pve.proxmox.com/wiki/Proxmox_SSL_Error_Fixing
/etc/pve/pve-root-ca.pem
/etc/pve/local/pve-ssl.key
/etc/pve/local/pve-ssl.pemCopy following files from other Proxmox node, normally, /etc/pve/pve-root-ca.pem files are the same.
/etc/pve/nodes/<node_name>/pve-ssl.key
/etc/pve/nodes/<node_name>/pve-ssl.pemNote: These certificates can be used for all nodes.
Note: /etc/pve/local is a link to nodes/<node_name>
If the VM got in error and can not do migration, then the VM needs to exit from error state.
ha-manager set vm:100 --state disabledpve-no-subscriptionIn order to update PVE, server needs to be under pve-no-subscription
Following error occurred if the subscription hasn't changed.
starting apt-get update
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.debian.org/debian bullseye InRelease
Get:3 http://ftp.debian.org/debian bullseye-updates InRelease [39.4 kB]
Err:4 https://enterprise.proxmox.com/debian/pve bullseye InRelease
401 Unauthorized [IP: 51.79.159.216 443]
Reading package lists...
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 51.79.159.216 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
TASK ERROR: command 'apt-get update' failed: exit code 100Got to Updates => Repositories, add No-Subscription in the list, and disable pve-enterprise subscription.
After reboot PVE, following error occurred.
# systemctl status pve-cluster
...
Jun 26 09:33:26 pve01 pmxcfs[3506]: [quorum] crit: quorum_initialize failed: 2
Jun 26 09:33:26 pve01 pmxcfs[3506]: [quorum] crit: can't initialize service
Jun 26 09:33:26 pve01 pmxcfs[3506]: [confdb] crit: cmap_initialize failed: 2
Jun 26 09:33:26 pve01 pmxcfs[3506]: [confdb] crit: can't initialize service
Jun 26 09:33:26 pve01 pmxcfs[3506]: [dcdb] crit: cpg_initialize failed: 2
Jun 26 09:33:26 pve01 pmxcfs[3506]: [dcdb] crit: can't initialize service
Jun 26 09:33:26 pve01 pmxcfs[3506]: [status] crit: cpg_initialize failed: 2
Jun 26 09:33:26 pve01 pmxcfs[3506]: [status] crit: can't initialize service
...
# journalctl -u corosync.service
...
Jun 26 09:26:17 pve01 corosync[1826]: [MAIN ] failed to parse node address 'pve01.xx.xx'
Jun 26 09:26:17 pve01 corosync[1826]: [MAIN ] Corosync Cluster Engine exiting with status 8 at main.c:1417.
Jun 26 09:26:17 pve01 systemd[1]: corosync.service: Main process exited, code=exited, status=8/n/a
Jun 26 09:26:17 pve01 systemd[1]: corosync.service: Failed with result 'exit-code'.
Jun 26 09:26:17 pve01 systemd[1]: Failed to start Corosync Cluster Engine.
...Change ring0_addr pve01.xx.xx of node in pve01 corosync.conf to IP address.
VM in Proxmox was locked as Config Locked (Suspended). To unlock it, run following command in shell
qm unlock <vm_id>If two or more nodes down in Proxmox cluster, then user can not login to Proxmox web page. In order to login, the number of Expected votes needs to be changed.
This change is only temporary, and cannot be changed to smaller than current Total votes.
Run following command to check status
pvecm statusRun following command to change Expected votes
pvecm expected 2Change quorum_votes in file /etc/pve/corosync.conf, to set different quorum vote for each node.
The vote of node can be 0, if this node is only a test node in the cluster.
The vote of node can be more than 1, if the node has more important role, such as TrueNAS running.
The reason to move Proxmox VE server to another machine is, I got issue when booting up Proxmox installation USB disk from a MacBook Pro. So I decided to use existing Proxmox VE server USB disk boot from this MacBook Pro.
The previous Proxmox Virtual Environment USB disk, must be an UEFI disk, because MacBook Pro is a UEFI machine.
The network configuration /etc/network/interfaces needs to be changed due to different network interface name.
First, change the interface name, which can be found using ip a command, the two lines need to be updated.
auto lo
iface lo inet loopback
iface enp0s10 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.1.205/24
gateway 192.168.1.254
bridge-ports enp0s10
bridge-stp off
bridge-fd 0The WIFI interface can be disabled if it is not used.
#iface wlp1s0 inet manualWhen try to migrate VM from one node to another, following error encountered
Failed to sync data - could not activate storage 'local-zfs', zfs error: cannot import 'rpool': no such pool availableThe reason is two nodes have different storage pool
Change source node storage pool local-zfs as below.
local-zfs, and click EditAll (No restrictions) to the node the stroage belongs toOK to save the optionMigration of VM between nodes failed - could not activate storage 'local-zfs', zfs error: cannot imp