Proxmox Virtual Environment is an open source server virtualization management solution based on QEMU/KVM and LXC. Users can manage virtual machines, containers, highly available clusters, storage and networks via a web interface or CLI. Proxmox VE code is licensed under the GNU Affero General Public License, version 3. The project is developed and maintained by Proxmox Server Solutions GmbH.
$7.50
per month
Pricing
Hyper-V
Proxmox VE
Editions & Modules
Developer
$24.95
per month
Bronze
$49.00
per month
Silver
$89.00
per month
Gold
$135.00
per month
Platinum
$199.00
per month
Community
€ 90
year & CPU socket
Basic
€ 280
year & CPU socket
Standard
€ 420
year & CPU socket
Premium
€ 840
year & CPU socket
Offerings
Pricing Offerings
Hyper-V
Proxmox VE
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Proxmox Virtual Environment's source code is published under the free software license GNU AGPL, v3 and thus is freely available for download, use and share. A Proxmox VE Subscription is an additional service program that helps IT professionals and businesses keep Proxmox VE deployments up-to-date. A subscription provides access to the stable Proxmox VE Enterprise Repository delivering software updates and security enhancements, technical help and support.
While Hyper-V did stack better for our needs than Proxmox VE or KVM, it did not offer the features that ESXi did for our needs and we had to forgo choosing Hyper-V for the promiscuous mode needs.
Proxmox VE is cheaper than VMware, especially upscaling an HA architecture. Compared with other free or less expensive solutions, Proxmox VE is high compatible with more types of hardware solutions and more VM types. From my point of view, Proxmox VE has no competitor at the …
Director Of Information Technology and HIPAA Privacy Officer
Chose Proxmox VE
With an incredibly easy to use interface, quick setup, and wide support for different hardware we found it was the perfect lab tool for our department to build, stage, and eventually move VMs into production with.
If budgets are stretched, Hyper-V is a very cost effective solution. Any veteran MS Windows administrators will have little issue in getting to grips with this. If you are familiar with VMware solutions, then you may find Hyper-V a little frustrating as it does lack some of the functionality of those products, however nothing that will prevent you from managing your virtual workloads and estate. Since rolling out Hyper-V 2019 we have had no real issues with it; ESXi seemed to have more issues and was less forgiving with hardware compatibility.
We used Proxmox to implement private cloud services, for clusters of a small number of servers, from 3 to 11 with and without high availability. Allways with ZFS file systems, and we used to install the root pool in SSDs mirrored and use other pools with RAID 10 in groups of four, for the virtual machines and containers, for the backups and snapshots, we used magnetic disks with RAID 10, in groups of four. Do not use an even number of servers because does not facilitates the implementation of High Availability, because the corosync service must have an odd number of servers to detect a failed server for the quorum system. We used a variety of servers, from clone PCs with AMD Ryzen with 6 cores and 12 threads with 64 GB of RAM no ECC, to high end servers with 64 cores and 128 threads per cpu and 2 cpus per server, with AMD EPYC Rome or Milan, 2 terabytes of RAM ECC.
Easy to use GUI - very easy for someone with sufficient Windows experience - not necessarily a system administrator.
Provisioning VMs with different OSes - we mostly rely on different flavors of Windows Server, but having a few *nix distributions was not that difficult.
Managing virtual networks - we usually have 1 or 2 VLANs for our business purposes, but we are happy with the outcomes.
The only issue I have with Hyper-V is I am unable to use Veeam on my Windows 2016 Server to backup my FreeBSD HAProxy VM.
There is some sort of checkpoint issue that I have been unable to figure out, but it works just fine on my Windows 2012 Servers. I do believe this is a Microsoft issue and not a Veeam issue though.
Another thing that could be useful that Hyper-V does not have would be some sort of GUI that shows the status of all the VM's on a given server to help us manage them easier and know what is going on. However, I do have Zabbix for this and that does a good job at monitoring all my servers.
Cheap and easy is the name of the game. It has great support, it doesn't require additional licenses, it works the same if it is a cluster or stand-alone, and all the servers can be centrally managed from a system center virtual machine manager server, even when located at remote sites.
Proxmox VE provides the most capable, yet stable virtualization platform in the market today. Licensing options are also competitive and cost-effective for support, and support is extremely fast and knowledgable of getting issues resolved as quickly and soundly as possible.
It is very easy to configure new virtual machines and manage them. But you have to use different interfaces to perform various tasks. Especially as soon as it comes to clustering you have to use at least two different interfaces (Hyper-V Manager and Failover-Cluster Manager) to perform all necessary tasks. The newly released Windows Admin Center is a way into the right direction to get all management tasks into one single interface.
Out of every product I have used for this, Proxmox VE is the most concise, clear, and functional I have ever seen. I continue to use Proxmox VE even after occasionally comparing alternatives available because of it's usability, design concept, and great support of features. It's very unlikely I will find a product that can even compete with Proxmox VE in every angle of what Proxmox VE provides.
In the past 2 years our Hyper-V servers have only had a handful of instances where the VM's on them were unreachable and the physical Hyper-V server had to be restarted. One time this was due to a RAM issue with the physical box and was resolved when we stopped using dynamic memory in Hyper-V. The other times were after updates were installed and the physical box was not restarted after the updates were installed.
Proxmox VE's ha-cluster functionality is very much improved, though does have a not-very-often occurrence of failure. In a 2-node cluster of Proxmox VE, HA can fail causing an instance that is supposed to migrate between the two nodes stop and fail until manually recovered through the command-line tools provided. Other than this, the HA clustering capability of Proxmox VE has proven to be reliable in 3 or more clustered environments with much less chance of these failures to occur.
Hyper-V itself works quickly and rarely gave performance issues but this can be more attributed to the physical server specifications that the actual Hyper-V software in my opinion as Hyper-V technically just utilizes config files such as xml, and a data drive file (VHD, VHDX, etc) to perform its' duties.
Proxmox VE's interfacing is always fast to load, both the Web interface and the command-line tool interfaces. Reporting is practically real time almost all the time, and you can see everything in mere seconds, easily able to identify if something is wrong or it everything is in tip-top shape as always desired
Hyper-V is greatly supported by techs around the world. There are tons of forums, help websites and individuals ready to answer questions. I've never needed to contact Microsoft for help...because help is so easy to find out there. Do a search online for anything related to Hyper-V and you will certainly find an article with spelled out steps on how to do what you are looking to do.
We had in person training from a third party and while it was very in depth it was at a beginner's level and by the time we received the training we had advanced past this level so it was monotonous and redundant at that point. It was good training though and would have provided a solid foundation for learning the rest of Hyper-V had I had it from the beginning.
The training was easy to read and find. There were good examples in the training and it is plentiful if you use third party resources also. It is not perfect as sometimes you may have a specific question and have to spend time learning or in the rare case you get an error you might have to research that error code which could have multiple causes.
initial configuration of hyper-v is intuitive to anyone familiar with windows and roles for basic items like single server deployments, storage and basic networking. the majority of the problems were with implementing advanced features like high availability and more complex networking. There is a lot of documentation on how to do it but it is not seamless, even to experienced virtualization professionals.
VMware is the pioneer of virtualization but when you compare it with Hyper-V, VMware lacks the flexibility of hardware customization and configuration options Hyper-V has also GPU virtualization still not adequate for both platforms. VMware has better graphical interface and control options for virtual machines. Another advantage VMware has is it does not need a dedicated os GUI base installation only needs small resources and can easily install on any host.
Proxmox VE is cheaper than VMware, especially upscaling an HA architecture. Compared with other free or less expensive solutions, Proxmox VE is high compatible with more types of hardware solutions and more VM types. From my point of view, Proxmox VE has no competitor at the same price level, it offers the most complete and production-ready HA solution.
Nothing is perfect but Hyper-V does a great job of showing the necessary data to users to ensure that there is enough resources to perform essential functions. You can also select what fields show on the management console which is helpful for a quick glance. There are notifications that can be set up and if things go unnoticed and a Hyper-V server runs out of a resource it will safely and quickly shut down the VM's it needs to in order to ensure no Hardware failure or unnecessary data loss.
Proxmox VE provides everything you need to quickly add new storage mediums, network and local, as well as networking interfaces, such as using Linux standard bridges and now Open-vSwitch bridges which can be even more scalable than before. Proxmox VE 4.0 dropped support for OpenVZ in favor of the more well supported and native LXC and made an upgrade path to it very simple.
Hyper-V has provided for an extremely cost-effective virtual environment with disaster recovery. For the size of our business, it's all we need to ensure our desired level of continuity of services and protection against hardware failures.
Since we are a Windows shop, deploying Hyper-V means we don't have the added cost of a hypervisor, since it's included in the cost of the Windows Server license. It's all we needed to achieve our goal of running all our virtual machines on a single server with another, less expensive server on tap for replication and failover.
We wanted easy deployment and management with disaster recovery while having the ability to leverage our years of Windows SysAdmin experience. Hyper-V fit the bill.
Proxmox has allowed to us to do more with less. We can invest in a single (or multiple if clustering) host with a decent specification, and run most of our infrastructure on it.
Open source technologies allowed us to re-use previous skills and knowledge. There was very little onboarding required because we already knew Debian, KVM, ZFS, etc.
Virtualisation has vastly reduced the amount of time required to maintain all our systems. Everything is so much more organised and lends itself to automation (with Ansible, in our case).
