Proxmox VE Reviews

It's used for server virtualization on a client-facing network.

Its compatibility is most valuable. For any VM or specification, if I have the license, there could be one cluster for it.

The management can be better. It's not like VMware where you can get all clusters on a single dashboard. In VMware, you can literally see all the VMs running in one cluster regardless of the host.

I've been using this solution for just a year.

I'd rate it a six out of ten in terms of stability. Because we don't have a professional engineer for Proxmox VE, we are very reliant on our suppliers. So far, we haven't experienced any bugs, but as an IT specialist, I haven't had any formal training for Proxmox VE. It's an open-source virtualization platform.

It's scalable, but it lacks automation. You have to configure the memory for the system to be automated. I'd rate it a six out of ten in terms of scalability.

It's for our external servers, and we probably have more than five thousand users.

We are very reliant on our supplier for support. I haven't got any chance to get in touch with Proxmox support.

I've used other solutions. Proxmox VE is much harder to use than ESXi and AHV.

It's easy, but the management is not really that efficient for us, so I'd rate it a seven out of ten.

It usually takes two days to conclude. There is also migration. Migrating less than twenty VM to a newly configured Proxmox would approximately take two to three working days.

It's very cheap.

I'd recommend it for a small business or a startup business. It's very helpful for those who are starting up and have fewer users. For DR scenarios or use cases, it would be worth it.

Overall, I'd rate it a seven out of ten.

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.

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.

Proxmox VE is used for many sectors, such as medical, IT, and electronics. It is an open-source server management platform.

The most valuable features of Proxmox VE are the ease of containerization. Overall the solution is generic, feature-rich, and has compatibility.

The documentation in Proxmox VE could improve.

I'm new to this type of solution, there are all these features and options to select in various scenarios, but there's not much documentation out there to explain which option you should be choosing for what, and why. I know there are a lot of YouTube articles, Reddit documentation, and other information where people say if you want to do task A, here's is how, and people follow it blindly. However, nobody understands what they're doing, and why.  I'll tackle any task and develop a solution but I need to understand what I'm doing. I need to understand why I'm selecting certain options, what makes that appropriate, what would make the other option inappropriate, the pros and cons, the whole run-through. I find the documentation lacking.

What I have noticed while I'm running a firewall, FireHOL, which works with DNS, and a media server all runs on my Gen 8 MicroServer. It's an I3350 with 10 gigs of RAM, and I do find that the RAM usage is pretty high. I know I do not have all the RAM allocated to the containers, but I find that the overheads there seem to be pretty high. The high RAM usage comes with input-output latency. I don't seem to have the same problem on the dual Xeon, but again that has infinitesimally more computational power, one would expect that to run quicker.

When it comes to the firewall and other aspects, I'm only looking for a simple solution, low power consumption, good performance at home, to keep my home network on. If the documentation went into a bit more detail on what the overhead requirements of Proxmox VX are and why, and how to optimize, especially when you start bringing in Oracle ZFS and VFS power systems. The RAM usage increases a lot. There's practically nothing about that in the documentation. You have to hunt down the details in VFS, and its functionality elsewhere to figure it out.

On the dual Xeon, for distributed computing, it is running fine. The system is running 24/7 without any problems.

At the moment, one of the limitations is hardware passthrough into containers. To do that, you have to start getting privileged containers. I know there's a lot of hype in the public domain as to the pros and cons of that, and some parts are supported and some are not. It would be interesting to see if technology could develop to the point where we could pass through hardware into containerized applications.

I have been using Proxmox VE for approximately one year.

Proxmox VE is stable and reliable.

Server stability's been phenomenal and I'm running it on several old HP MicroServers. They're Gen 7, using the AMD Turion chips. I've been running it on the Gen 8, I3, 350, and dual CPU E3 in Xeon. there are some performance differences based on what the hardware's capable of, but no matter what platform I run it on there has not ever been any stability problems whatsoever.

The scalability is good. If you're working with generic processor models, it's easy to shift them across different platforms once you place the CPUs.

I have not needed to use the support from Proxmox VE. I have found all the answers I have needed online from user groups and Wiki support pages.

I rate the documentation and community support from Proxmox VE a three out of five.

I have used previously VMware and VirtualBox. Both are installs that have been on Microsoft Windows, and I found them both to be very limiting, very difficult to set up and manage. Proxmox VE, I found to be the easiest to use, quickest in terms of response, and has the best functionality.

The initial setup is very easy. Once you get the hang of it, setting up the VMs, containers, and deploying them is incredibly quick.

The setup for most of the configurations is similar, once you understand the concepts and the principles, it comes down to basics. You know your hardware and what you're setting up, and what it's capable of doing. You can't set up older generation hardware and then expect to have PCI Express Passthrough or GPU Passthrough, because the hardware doesn't support it.

You can't expect the solution to do what the base hardware is not capable of doing. Work within the constraints of the hardware, understand your hardware, and the OS.

You can download the solution and it is an open-source installation, it is exactly the same as their commercial solution.

The maintenance of the solution depends on how you've set it up. If you've only set it up as a functional hypervisor, you have your VMs running, and that's the last thing you did, then you're going to have to come back every two weeks or every month to check on your OS updates, upgrades, and security patches, et cetera. However, you can automate a lot of that with Cron jobs. It's about learning the system which is based on Debian. If you understand Linux and Debian, you will understand how powerful the system is and what you can actually do with it. When you start running things, such as Monits or syslogs, you can automate any error messaging or any problems and it can be sent to your system administrator in an email.

Whether it's a case of regular backups that are happening, if everything is working well, then great, but if one fails, an I/O error or other errors pop up and you get notified of it quickly, then you can fix it easily. If you're only coming in every four weeks to have a look at it and see what's going on, things could have gone horribly wrong.

I would suggest to anybody who's running a hypervisor, is schedule regular backups. Back up your VMs regularly. Schedule it. Automate it, and make sure it happens on a separate machine, onto a separate machine, onto a separate host- because you don't want to lose your VM with all its backups.

If you've taken the time to set it up well with all your Cron jobs and automation, there will be almost zero maintenance.

I rate the implementation of Proxmox VE a five out of five.

To use Proxmox VE there is not a license required. However, you can purchase a support license, which you access, but it doesn't change the functionality of the solution.

Their licensing is very similar to other solutions, such as Canonical and Ubuntu. The full OS is available to you. If you want the support, you will need to pay a license fee.

My advice to others wanting to implement this solution is if you're looking to virtualize, ask yourself why. In terms of bringing your costs and energy consumption down, never mind the whole global eco-footprint hype that everybody wants to get onto. The reality is, for any business, keeping a business afloat is about dollars and cents, and if you can accomplish your IT tasks at a lower cost and expense, have better utilization of hardware, you've probably already hacked a path to what way to move forward.

Instead of spending hundreds of thousands on multiple servers, to then have a less than 5% utilization on each machine, while they using up 500, 600 watts of power, is not efficient. With virtualization, you're running multiple VMs on one physical piece of hardware. You get much better utilization out of it, you're getting much more for the money you are paying, and without any significant drop in performance.

When one considers the internal networking on the VM, where you have different VMs and your containers are running on internal networks. You're not limited to gigabits or 10-gigabits throughputs. It runs on the PCI Express speeds on the board, it is a lot quicker.

I rate Proxmox VE an eight out of ten.

At the moment, it's used for the virtualization of everything within my test environment.

I'm not using the newest version of Proxmox.

It brings all those benefits that virtualization brings. It reduces cost. I don't have to invest so much in buying many servers. I can go buy one new server with enough resources, and I can virtualize using that server. I can also layer features, such as routing, firewall, HTTP, and VLANs, on top of that.

In addition to the virtualization, the firewall and the routing functions that it provides are valuable.

Its user interface can be improved. In the version that I am using, not all functions can be performed by using the UI. There can be some improvement on that. I'm assuming that it has already been improved in the latest version.

I have been using this solution for the past three years or so.

It has been absolutely wonderful in terms of reliability and performance.

I see the options for scalability, but for my own use case, I don't have the need to have several instances. It is just for my test environment, but the options that they provide sound interesting. There are some high availability configurations for multiple Proxmox instances.

My environment has about 30 users. It is being used every day. It is an operational tool because the environment has to be up.

The way the licensing is structured is that you have to pay for the support. My use case is just for my test environment. I have not deployed it on production, so I've not had any need for technical support.

I've worked in environments where other solutions, such as VMware, have been used, but personally, I have not used any other solution. This is the first solution I am using as far as virtualization is concerned.

For me, it was straightforward. There are different user levels for things like this, but it was straightforward for me. It takes about a day or two.

I implemented it myself. For its deployment and maintenance, you need a minimum of one and a maximum of two people. The second person is for backup reasons when the primary resource is not available.

I have absolutely seen an ROI. I am not able to measure the actual value in terms of returns, but because I've invested nothing, apart from the cost of the server or the hypervisor upon which the Proxmox is installed, the value that we've got from it has been huge.

The way the licensing of Proxmox is structured, you can use it for free. It is an open-source solution, and you can use it for free, but if you do need support, then you have to pay for the support. So, you can use it in a way that you don't have to pay anything, which is a plus point for me. For people or users who have huge and more intense use cases, the advice or the recommendation is to always pay for support. In case something goes wrong, you can fall back on the team that will attend to your request. For me, at the moment, the cost is zero.

I would advise that you weigh your use cases very well before deciding whether to use Proxmox or not. It meets the needs of my use case, and I don't have any reason to complain. If there is a switch or change in my use case, I might decide to not use Proxmox. I might consider some other solution.

If you want to run Proxmox without paying for support, like any open-source solution, you have to read the documentation and be familiar with all the dependencies and requirements for your environment. Once you have all of that covered, you are good.

I would rate it a nine out of 10.

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.

With Proxmox, we use the hypervisor of Proxmox and Proxmox backups. In VMware, I see all the production, like vSphere, vCenter, vRealize Operations Manager, vSAN, Workspace ONE, and VMware Horizon. Right now we are working with NSX. 

For VMware, as a partner, I have many cases of vSAN as a hyperconvergence solution. This solution is very popular in my country, mostly with banks. There are many solutions that we have implemented and that are very successful. Horizon is another solution that is highly requested by clients. Because of the pandemic, the VDI and Remote Desktop are often requested from our clients. Those two are very good solutions. From my experience, I don't have many problems with them.

Proxmox is free, very stable, and doesn't require more resources for memory RAM. It's fine for a small data center.

One issue with Proxmox is that some processes are not automatic. For some processes, you have to do it manually by command line. I don't know about the last version of Proxmox, but I had that problem with this version.

I've been using this solution for one year. In my last job I was a final client, so I worked with vSphere and the vCenter. I did a migration from vSphere to Proxmox, and I was in charge of this infrastructure using Proxmox. I am working for a partner of the VMware product as a presale VMware specialist.

Most implementations are on-premise. We really don't have implementation on cloud. I'm from Bolivia, and we recently have been introducing on-cloud solutions, but most of the solutions are on-premises.

Proxmox is very stable.

For deployment, we used eight blade servers.

Proxmox is is free.

I've worked with VMware, vSphere, vCenter, and vRealize Operations Manager. VSphere works perfectly. The enterprise version is very complete, and you get almost everything you need in data center.

I would rate Proxmox VE 7 out of 10.

We sell Proxmox VE solutions to our customers. The workload to help our customers may be the biggest use case to be on the cloud. We use a bunch of statuses, and different ways to deliver databases, and SQL Servers. So, that's the natural way we use the platform on the cloud.

It has a good performance and you can cluster it.

It's more about the clusters. The clusters are pretty much good and have a high performance and impact.

For now, we're planning to migrate to another solution because there seems to be a lot of backups that we have set up. We have reviewed Proxmox VE but we want to focus more on our customers. In fact, we have already finished our first deployment and we will receive more features that will go to the cloud.

I have been using Proxmox VE for the past five years.

You don't have to be very observant. We have maybe three times the hard one, but it seems as if this is an open-source solution that is supported by the community, and it's okay.

If you feel you have the skills to do it, you can go hands-on by yourself to do these deliveries, and it's going to be very useful for the solution. You need to have the training and the right skills.

For now, we are pretty much working on that, but I think someday, we will make it solve another class from our class which is very good because we have an installation. If you start from the beginning, it's the third one, maybe you have the profile, so you will deploy it in maybe four days.

So it's what you have to like to go there, but it can work because if you have some problems, you have that resource to go and I found things they will need. They will keep you updated and will help you a lot. So if you ask me, their service is good. The community forum is very technical, and they're quick to respond when they are messaged.

The setup is very easy, but the problem is when you have to customize the solution they're talking about more episodes. You have to be more hands-on to have a very good draft, it will be more helpful to have a very good delivery.

For the price, performance is going to be the first takeaway we can offer to our customers.

It's one of those things for me to move things on to the cloud. It's not so easy. I am always on the laptop and have to monitor that because if you want to make strides; you need to stay online. Though we intend to go with a third party to look for another solution, we hope they will fix that in the next release.

The work panel is very good for intake. It's very easy to use and you can scale from other areas which is not a very technical way, so you can use them, including the panel. They can manage their integrated solutions, and that's very good because it's the thing that you want to scale. If the customer wants to operate a downgrade and do something with Proxmox VE, that is what will take you there. You can integrate Proxmox VE with other solutions. Proxmox VE is one thing if you want to start with cloud deployment.