Proxmox VE Reviews

We are cloud providers. We install the product to serve our customers.

KVM hypervisor is a valuable part of the solution.

We are having some problems with the product. It is suitable for small companies with 20 to 100 servers. My organization has more than 2500 servers in the hypervisor platform. We have problems when we try to migrate some servers to Proxmox. We are facing issues with disk utilization and disk performance. We are considering migrating all the servers back to VMware. The product must improve the disk performance and disc issues in general. The servers in Proxmox freeze sometimes. The file systems become read-only file systems after we restart the server. These are the main problems we are having nowadays.

I have been using the solution for a year.

I rate the tool’s stability a five out of ten.

I rate the tool’s scalability a three out of ten. We set up 50 servers in our environment, which worked well. Then, when the virtual server numbers increased to 100, it worked fine. Later, when it was around 200 to 300, the performance got worse. It is getting worse with time. The more we scale, the more we have problems. Currently, we have 300 to 350 virtual servers. Our customers are small businesses.

We have trouble getting help from the support team.

Negative

I rate the ease of setup a four or five out of ten. The initial setup is not exactly difficult, but it is not easy either.

If the deployment is not very detailed, it takes us one day.

I rate the pricing a three out of ten. The product is free. There is no licensing fee. However, we do have to pay to get support. The support costs are reasonable.

I am using the latest version of the solution. I would recommend the solution for small businesses. I would not recommend it for medium and large enterprises. Overall, I rate the product a four out of ten.

On-premises

The most valuable feature of Proxmox VE is the linked clone.

The solution is not good at upgrading and this is why I using version 6.2 and not version 7. There is no easy way to implement the upgrade. I don't have enough experience to do it safely.

I have been using Proxmox VE for approximately two years.

Proxmox VE is highly stable.

I rate the stability of Proxmox VE a ten out of ten.

The solution can scale but it is not perfect.

We use this solution in the branch office in Beijing. We have approximately 25 people in the office and 15 of them will use something built on Proxmox VE.

I rate the scalability of Proxmox VE a seven out of ten.

I have not used the support from Proxmox VE.

I did not use a similar solution prior to Proxmox VE.

It's straightforward to get started with Proxmox VE, but if you want to do something more advanced, it can become complex. The installation process is simple as long as you set up the cluster correctly. Setting up the cluster is straightforward, but when you try to do something more advanced, the complexity increases significantly.

We are using the free community version of Proxmox VE.

We evaluated VMware ESXi and oVirt from Red Hat before choosing Proxmox VE.

Proxmox VE and VMware ESXi are great options for beginners. I have some experience with Linux, which is sufficient for setting up the Proxmox VE environment and VMware ESXi. These two solutions are ideal choices for a small office.

I rate Proxmox VE a nine out of ten.

Hybrid Cloud

It is implemented in several Private Cloud Data Centers, from 5 to 16 nodes, from 256 GB RAM to 1 TB RAM, all using Supermicro Systems, running SQL servers, Application Servers ( SAP, Prothevs and some tailored Apps developed in house ) VDI and Files Repositories . all smooth and trouble free .

With live migration, there is no downtime when any node needs service or upgrades. Plus, when I need more memory, I just allocate it; more disk space? same. It is possible to administer almost anything remotely, now it takes months till a customer needs a weekend visit to service something, before Proxmox, it used to happens once a month!

Live migration :

Is simplifies the daily work, and reduces the downtime to nearly 0 .

Clonning and Snapshots :

Verry useful for development testing and backup .

Histogram about i/o, memory, CPU and network usage :

Helps to find the issue when some VM are running in some kind of bottleneck .

Mostly simplify web interface, simple things like the use of right mouse button to change VM attributes, make it more intuitive, but it is just cosmetic improvements, the core functions are all there.

Version 6.x improved the support for Containers to the PRO level .

re than 10 years, since version 1.6 all the way to version 6.2 

Never had any issue with stability, even in the very earliest stages of development...

Not for now, the 16 nodes per cluster limit have been removed in the 5.x release !

Customer Service: OK, in fact the little we've used it, the site documentation was really good.Technical Support: Same as above.

Yes, Citrix XEN Server and EMC VMWare Server. I left Citrix for security, there are too many "black box" in the binaries that cannot be audited. In the VMWare case, for licenses politics, it uses a "per socket" schema that punishes high density servers with 2 or 4 sockets .

Is is the tool of choice used in the entire Facebook infra-structure, so it must be "at least" good enough .

The first test was a little complex, in the time of the 1.4 version, but since the 2.0 version it is extremely simple, takes less then an hour to deploy a node and connect it to an existing cluster.

The 6.x release made things even easier, most maintenance tasks are now in the web interface

I am an IT consultant, and I do everything myself (with my team, we are 4 people!)

Outstanding, worth every single cent spent on it!

The deployment itself cost nothing, it is Opensource software! The monthly subscription costs 17 euros per node, and it covers anything we needed so far...There are more options, but it is more then our customers needed until now .

Several, From Red Hat to Ubuntu, and everything I can find with a Google search, I spent 6 months with these research and tests!

The Facebook contract came well after this tests .

Do it! The simplicity will surprise you!

Private Cloud

The product helps me to use a group of servers and improves the speed.

The solution's most valuable feature is backups.

Proxmox VE needs to make a deal with Veeam. I was also unable to make version upgrades. I have also encountered backup problems.

I have been using the product for seven months.

I rate Proxmox VE's stability a seven out of ten.

I rate the tool's scalability a five out of ten.

The solution's technical support is not good. I find support through the internet.

Neutral

The tools' deployment is easy and I rate it a seven out of ten. It took two hours to complete. Install Proxmox VE on the server, then proceed to install the hard disk. After that, configure it for the work system and install the desired system. Finally, install all the necessary programs on the server. You need one resource to handle the deployment.

The tool's deployment can be done in-house.

The product is open-source and I rate its pricing an eight out of ten. You need to pay for support and it is costly.

I rate Proxmox VE an eight out of ten.

Private Cloud

We are a service provider and we use Proxmox VE. We use the virtualizer mainly.

The most valuable feature of Proxmox VE is its ease of use.

The virtualizer in Proxmox VE could improve.

I have been using Proxmox VE for approximately one month.

I rate the stability of Proxmox VE a seven out of ten.

I do not have any users yet but I have 10 potential users.

I rate the scalability of Proxmox VE an eight out of ten.

I rate the support from Proxmox VE a nine out of ten.

Positive

The initial setup of Proxmox VE is complex. The full deployment took many weeks and I am still configuring it.

I rate the initial setup of Proxmox VE a seven out of ten.

We used two people for the deployment of the solution.

The price of the solution is priced low.

There is a one-time purchase to use this solution.

I rate the price of Proxmox VE a seven out of ten.

I rate Proxmox VE an eight out of ten.

Our primary use case for Proxmox VE is for virtualization and a little bit of SaaS storage, basically for virtual machines.

Proxmox VE is simple to use and it is feature rich. The fact is that it performs,

The only issue I have with Proxmox VE is updating it. You have to manually update it or you have to have a way to update it automatically.

The main area for improvement is with the automatic updates, if it's even possible, even if you have to pay for the cloud services. Updates are very important.

If they could fine tune the updating process that would be good.

I have been using Proxmox VE for two years.

Proxmox VE is stable. We have a few issues where all of a sudden you can't update it, because maybe you have taken too long to update the repository. This is a concern for us. Like I mentioned before, the updating feature is very important to us because there could be some security issues.

There are a lot of actions that you need to do with commands, which have not been automated yet. I believe that with time it will be automated.

In terms of scalability, we didn't have any need for scaling because just the fact that you can put them in a cluster and manage one unit is a very good feature. I don't have to manage it individually, I can just put them together in a cluster and manage them for one single piece. I'm about to test the backup feature and also maybe upgrade it to the next version, which is 7.0. I'm expecting that there will be a lot of improvement.

Right now we have about six users on a project that I'm deploying. I'm still managing the project, but due to COVID it has gone on for two years, but we're just about to hand it over. Because of the COVID issue, nobody wants to come to one place to sit down and do anything. All of last year was just wasted, but this year we're able to do a number of things with them. The manual process of updating one by one is relatively stable. In the account, you have to centralize the management. You have to log in one by one and you can have a different password for for each one, it's not unified. They have not unified the authorization process.

One thing I have noticed is that because I put a password on one it is expecting me to manually put a password on the other node. I would expect that for better management you can have the same propagating password. Maybe there's a better way to do it, but that's what I have been seeing and I found that I have to be doing this for each one on each node. That is an issue, but so far it's been very good. It's been very stable. I never had any issues with it. It's cool stuff.

I  really like the software storage. I used it on one of the cloud servers that we set up and it's working very well.

We do plan to increase the usage in the future.

Proxmox VE is very simple to use.

The deployment took a long time, but it was not because of Proxmox. It was some other issues for other projects. Installing the Proxmox software is very easy. It just takes a day or two.

We did it in-house.

Our license is on a yearly basis.

There are no other costs, just the license fee and the license is flexible. You could decide to go subscription only or you could decide to pay for support.

My advice to anyone considering Proxmox VE is that they should study it to understand it, because it is feature reach, so you have to read the manuals. They have to read the manual and unfortunately the manual training level is on the high side, so for people who are experimenting or who are just coming into the free version, it might be a little bit hard for them. Proxmox should try and market more on the training side so users can speed it up and have a good adoption. I hear that people understand the product very well, because right now I don't think it has a rival. It's trying to beat the Oracle VM or the other VMs in the market.

On a scale of one to ten, I would give Proxmox VE a seven.

On-premises

My company uses Proxmox VE for VDI, so we basically use it for Windows VDI, and a few of our Linux servers run on it.

My company has benefited from the use of Proxmox VE since it has helped us reduce our costs. Earlier in my company, we were using VMware. My organization's costs related to operations were on the higher side when we were using VMware, especially when it came to areas related to management and updates. With VMware, you need to have an active subscription to run a few basic VMs and other stuff, but on Proxmox VE, you don't need to pay for any overhead costs. You only need to pay for support from Proxmox VE, and otherwise, it is a completely free solution.

The most valuable feature of the solution stems from the fact that my company gets to use the open-source version of the product while also getting better features like clustering and redundancy. Compared to the other products in the market, Proxmox VE has an easier setup phase and can be easily managed.

Proxmox VE doesn't offer a good interface for monitoring. From an improvement perspective, Proxmox VE can offer a better interface for monitoring. Other products like Nutanix offer better monitoring capabilities than Proxmox VE. Proxmox VE doesn't have any other product integrated with it for storage. My company has to look for products from other vendors to take care of the storage part in Proxmox VE. Proxmox can offer its users a storage solution integrated with Proxmox VE.

Feature-wise, the console was the only place where my company saw an issue with Proxmox VE. The console provided by Proxmox VE is not much of a console meant for virtual machines. With Proxmox VE, once you have deployed the virtual machines, you realize that the initial console is not very good, because of which the graphics may seem boring. My company also finds many compatibility issues with the tools you need to install for the virtual machines to work in Proxmox VE, like the drivers and other stuff. My company has to look into many logs and other sources to resolve the compatibility issues related to Proxmox VE. In Proxmox VE, my company installs ISO when the setup phase of a virtual machine is carried out. One of the problems my company faced with Proxmox VE was installing a server with MySQL since it didn't function as an out-of-the-box product, because of which we had to shut down the machine and go through a configuration process. The default processor provided by Proxmox doesn't work.

I have been using Proxmox VE for a year.

It is a stable solution. My company does face some performance-related issues with Proxmox VE, but I feel that such issues are mostly related to hardware and not the solution.

My company hasn't used the scalability options provided by the solution because our hardware is currently fixed. My company operates on an on-premises model, and I don't know how we can avail of the scalability options if we plan to move to a higher version of the hardware.

My company has only two servers running for Proxmox, but we have about a hundred VDIs or virtual machines that run on Proxmox.

I have experience with VMware. We had VMware in our company, which is only for service and not for the VDI part. We did not continue with VMware in our company because it was not an open-source platform. My company mostly prefers to stay on open-source platforms over paid tools.

The initial setup of Proxmox VE was very easy. With Proxmox VE, the installation, clustering, and configuration parts are easy.

The solution is deployed on an on-premises model. My company plans to deploy the solution on the cloud in the future.

For the deployment process of Proxmox VE, since my company migrated from VMware to Proxmox VE, we rely on our own hardware. The deployment process didn't require much effort. In our company, we were able to handle the workload related to the deployment process easily.

The migration process from VMware to Proxmox VE was completed in a period of 15 to 20 days. In my company, we had very little workload on VMware. To work on the VDI part in Proxmox VE, my company had to do a fresh setup, meaning we had to start from scratch since we weren't using it with VMware. After looking at the solutions available in the market, my company decided to go ahead with Proxmox VE.

It is an open-source platform.

As a part of my company's evaluation process, we tested VMware.

The solution's maintenance part was very easy.

I recommend Proxmox VE to others considering the online community support and because it is available as an open-source product.

I rate the overall tool an eight out of ten.

On-premises

We are using Proxmox VE for our internal services, we have a few virtual machines that run our mail servers, call center solutions, TDX, and other applications. Proxmox VE is a virtualized platform.

The most valuable feature of Proxmox VE is the speed. Additionally, I can modify the solution if needed because it is open-source and the integration of any kind of API and monitoring is hassle-free.

Proxmox VE can improve the management of virtual discs. For example, if my virtual disc is 200 GB and I want to decrease it is not easy. I have to do a lot of things to decrease the size of existing virtual machines. If the Proxmox VE team can make it easy for customers to instantly increase or decrease the virtual machine hard disc, it will be very helpful for me. However, the containers I can do it easily.

I have been using Proxmox VE for approximately seven years.

I rate the stability ofProxmox VE an eight out of ten.

The scalability of Proxmox VE could improve. The vertical scaling needs improvement. If the vertical scaling was better I could input the resources on the fly without shutting down the system. This would make it a lot easier.

We have approximately six technical support staff using this solution in my company. We plan to increase our usage of this solution.

I rate the scalability of Proxmox VE a six out of ten.

I have not had any issues that I would need to contact support about. 

I used Oracle Virtual Box and VMware prior to Proxmox VE. We choose Proxmox VE because of the cost savings, it is free.

Proxmox VE's initial setup of easy. I started the implementation process by selecting a location, installing the hardware and Proxmox VE, and then I made the cluster without the Proxmox VE. The last step was to implement my virtual machine. The full process did not take more than two hours.

I rate the initial setup of Proxmox VE a nine out of ten.

I did the implementation of this solution myself.

This is a free open-source solution.

My advice to others would be to choose simple solutions for only virtual machines with no extra integration of other features. This is an open-source solution and if someone wants to do something on the backend many things could go wrong. It is best to start with something simple, such as virtual machines with containers only. After they have had some experience then they can expand their knowledge with other solutions.

I rate Proxmox VE an eight out of ten.

On-premises