What is our primary use case?
Proxmox VE is used for many sectors, such as medical, IT, and electronics. It is an open-source server management platform.
What is most valuable?
The most valuable features of Proxmox VE are the ease of containerization. Overall the solution is generic, feature-rich, and has compatibility.
What needs improvement?
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.
For how long have I used the solution?
I have been using Proxmox VE for approximately one year.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.