Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form

Cluster creation in Proxmox VE

Posted on 11/04/201617/08/2026 Christian By Christian No Comments on Cluster creation in Proxmox VE
  1. Home
  2. Virtualization
  3. Cluster creation in Proxmox VE
An illustration showing a cloud with the Proxmox logo, connected to multiple servers with arrows indicating communication or data flow.

The Proxmox VE cluster manager pvecm is a tool to create a group of physical servers. Such a group is called a cluster. We use the Corosync Cluster Engine for reliable group communication, and such clusters can consist of up to 32 physical nodes (probably more, dependent on network latency). Kindly refer to this related guide on how to extend Proxmox Local Container Storage. In this article, you will learn about Cluster creation in Proxmox VE.

After logging in, it is now time to create our cluster. The commands below are used to create a Proxmox cluster.

Proxmox VE 4.x (and all versions above) cluster enables central management of multiple physical servers.

Note: First, install the Proxmox VE on all nodes.

Also, make sure that each Proxmox VE node is installed with the final hostname and IP configuration.

Note: Changing the hostname and IP is not possible after cluster creation. Currently, the cluster creation has to be done on the console, you can log in to the Proxmox VE node via ssh.

Please see Fix INACCESSIBLE_BOOT_DEVICE in Windows and Windows Server, How to fix Windows Boot Error 0xc0000098 (winload.efi), and Fix Veeam Proxmox VE Backup Error: Failed to prepare disk for backup.

Create Proxmox VE Cluster

Kindly Follow the steps below to create your cluster!

pvecm create <cluster_name>

The cluster does not operate on master/slave basis, but on Quorum. In order to achieve healthy cluster status, all nodes need to be online. Let’s execute the following command and create the cluster:

root@pmxvm01:~# pvecm create pmx-cluster

After cluster creation is complete, check its status by using the following command:

root@pmxvm01:~# pvecm status

Now that the cluster has been created. The next step is to add Proxmox nodes into the cluster. Securely log in to the other node and run the following command:

root@pmxvm02:~# pvecm add 192.168.1xx.1

Verify the node to ensure it is now joined with the cluster with the command below.

root@pmxvm02:~# pvecm nodes

Now let’s view the status of each node

root@pmxvm02:~# pvecm status
Quorum information
------------------
Date: Wed Apr 20 12:02:05 2016
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00xxx001
Ring ID: 4
Quorate: Yes
Votequorum information
----------------------
Expected votes: 1
Highest expected: 1
Total votes: 1
Quorum: 1
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name

I hope you found this blog post helpful. Now you have learned about Cluster creation in Proxmox VE. If you have any questions, please let me know in the comment session.

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
Virtualization Tags:proxmox, Proxmox Container, Proxmox Server, Proxmox VE

Post navigation

Previous Post: Administer LXC Containers: Easy Guide
Next Post: Fix Outlook Not Responding and Outlook Crashing or freezing

Related Posts

  • VMware
    The validation process found problems on the server to which you want to install features, the features are not compatible with the current configuration of your server Virtualization
  • images copy
    HA-Proxy Configuration File: Copy Between Nodes on Proxmox VE Virtualization
  • disaster recovery checklist e1782394730353
    Disaster Recovery Test Checklist: What to Capture Before You Start Backup
  • savds
    VM is not accessible: Fix Taking ownership of a VM failed Virtualization
  • 87a26c60 0001 0004 0000 000001423515 w948 r1.77 fpx54.99 fpy56.04
    Administer LXC Containers: Easy Guide Virtualization
  • VMware Aria
    VMSA-2022-0026: An arbitrary file read vulnerability in VMware Aria Operations Security | Vulnerability Scans and Assessment

More Related Articles

sandbox How to Configure Windows Sandbox Virtualization
Add Hyper V to VRO e1773748172543 Integrate Hyper-V [SCVMM] with Veeam Recovery Orchestrator Virtualization
VMware How to install Windows Server 2022 on VMware Workstation Virtualization
HyperV 1 An error occurred while attempting to connect to the server: Check if the Virtual Machine Management service is running or you are not authorized to connect to this server Virtualization
Azure Local New Policy fix How to Resolve New WDAC Policy Issues in Azure Stack Virtualization
Failedcluster Failover Cluster Manager failed while managing one or more clusters, the error was unable to determine if the computer exists in the domain Virtualization

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

vexpert-badge-stars-5

Virtual Background

VEEAMLEGEND

Categories

Top 30 Sysadmin blog

veeaam100

Veeam Vanguard

  • images 5
    IP Address UNREACHABLE: HTTP connection pool Max exceeded Configuration Management Tool
  • prometheus feature image
    How to use Prometheus for Monitoring Linux
  • csdfg
    What is Cortona: How to disable Cortana via the registry or GPO Windows
  • windows1019h2
    Synchronize your Domain Controller with an external time source Windows Server
  • screenshot 2020 02 07 at 20.59.01
    How to use the PsInfo utility from SysInternals Windows Server
  • duplicate image
    How to Migrate Your WordPress Site with WordPress Duplicator Network | Monitoring
  • Windowsfilesystemxx
    Failed to remove network for the build, Job failed error: Invalid volume specification: “/cache” Containers
  • S3 Bucket Replication
    Set up Cross-Region Replication for S3 Buckets AWS/Azure/OpenShift

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,745 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Contact
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon
  • Bsky

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2026 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.