Proxmox Cluster - Basic
Create Cluster
pvecm create <cluster_name>
Add node
Run following command from new node
pvecm add <target_node>
pvecm create <cluster_name>
Run following command from new node
pvecm add <target_node>
When using UI Web interface to add node into cluster, the following error occurred
ERROR: TFA-enabled login currently works only with a TTY. at /usr/share/perl5/PVE/APIClient/LWP.pm line 100
Use command line below to add node via Shell
pvecm add <target ip> -link0 <source ip>
If got error on key validation, try node name instead
pvecm add <target_dns_name>
When adding the Proxmox node into existing cluster, the IP to DNS reverse lookup has different name, miss configuration. Then the new node thought it is already a member of cluster, but other nodes are not.
Convert the node back to local mode
Stop the corosync
and pve-cluster
services on the node:
systemctl stop pve-cluster
systemctl stop corosync
Start the cluster file system again in local mode:
pmxcfs -l
Delete the corosync
configuration files:
rm /etc/pve/corosync.conf
rm -r /etc/corosync/*
Start the file system again as a normal service:
killall pmxcfs
systemctl start pve-cluster
The node is now separated from the cluster.
Deleted it from any remaining node of the cluster if it is already a node of cluster
pvecm delnode oldnode
If the command fails due to a loss of quorum in the remaining node, you can set the expected votes to 1 as a workaround:
pvecm expected 1
And then repeat the pvecm delnode command.
This ensures that the node can be added to another cluster again without problems.
rm /var/lib/corosync/*
Remove /etc/pve/nodes/<node_name>
from other nodes.
Remove ssh key from /etc/pve/priv/authorized_keys file
If same certificate can be used for multiple domains in Proxmox clusters' nodes, then can use following steps to synchronous certificates.
/etc/pve/nodes/<target_node_name>
pveproxy-ssl.pem
and pveproxy-ssl.key
in /etc/pve/nodes/<source_node_name>
directory into target node directory.pveproxy
service using command systemctl restart pveproxy
.After install custom certificate, the Proxmox UI could not be displayed.
Remove two files pveproxy-ssl.pem
and pveproxy-ssl.key
in /etc/pve/nodes/<node_name>
directory. Then restart Proxmox.
Unable to access GUI after uploading my certificates
Proxmox Certificate Management
Run following command to convert vmdk to qcow2
qm importdisk <VM_ID> <Virtual Disk>.vmdk <storage> --format qcow2
Here, VM_ID is a number. After completed a newly created disk appears in VM
Double click the newly created disk, then select VirtIO Block device.
Select Write Back as cache method
Double click the newly created disk, then select SATA device.
Select Write Back as cache method
apt remove --auto-remove open-vm-tools
apt remove --auto-remove xserver-xorg-video-vmware
apt purge open-vm-tools
apt purge open-vm-tools-desktop
yum remove open-vm-tools open-vm-tools-desktop
root@proxmox:~# cat /sys/module/kvm_intel/parameters/nested
Y
Intel CPU
echo "options kvm-intel nested=Y" > /etc/modprobe.d/kvm-intel.conf
AMD CPU
echo "options kvm-amd nested=1" > /etc/modprobe.d/kvm-amd.conf
Install Module
modprobe -r kvm_intel
modprobe kvm_intel
Note: more info, check https://pve.proxmox.com/wiki/Nested_Virtualization
Download ISO, such as VMware-VMvisor-Installer-7.0U2a-17867351.x86_64.iso
General Tab
OS Tab
System Tab
Hard Disk Tab
CPU Tab
Memory Tab
Network Tab
Nested Virtualization
How to Install/use/test VMware vSphere 7.0 (ESXi 7.0) on Proxmox VE 6.3-3 (PVE)
When press FN-F11 key to VNC browser window of Proxmox VM console, it only shows the desktop.
To send the F11 key to ESXi installation screen, press FN-CMD-F11 instead.
Currently CentOS 9 doesn't support KVM or QEMU CPU type. Use host
as CPU type instead.
In Proxmox web interface, there is no option to convert back template to VM. In order to do this, use Shell session, delete template: 1
line in the configuration file under /etc/pve/qemu-server/<vm_id>.conf
file.