Why don't we support Xen, OpenVZ and VirtualBox anymore?

This is something we're constantly asked. Virtualization is a complicated balancing act. Sure, anyone can write a control panel to start and stop VPS but to do it well, is another challenge all-together. Our developers started with the intention to support as many Virtualization systems as possible, however as time went on we gained experience which taught us three things.
  1. Some virtualization software is better than others.
  2. Some updates to such software force us to waste time by working around changes which were poorly announced.
  3. Providing a single virtualization stack has allowed us to fine-tune and excel.
Since we exclusively support Qemu/KVM, our providers have benefited from secure, high performance VPS for years and we keep improving our control panel to do it even better.

  1. Favoured by the worst hosts in the industry, OpenVZ is always used to oversell beyond belief. This creates angry end users and "overnight hosts" that disappear, leaving people angry with VirtPanel and giving our software a cheap reputation.
  2. OpenVZ uses bean-counters to limit the resources of a container. This can work great if your VPS are trusted, however with third party VPS, it won't be long before your server comes to a stand-still and you will struggle to SSH in to find the cause. Often cryptically named bean-counters were only fully utilized by Parrallel's Virtuozzo.
  3. OpenVZ updates have required total code overhauls and bean-counters to randomly break our software.
  1. The Xen Hypervisor is hard for people to install. While this has recently improved, we just don't see the point in dom0. We prefer the server to have access to the full resources available.
  2. Moniting and limiting disk speed was impossible without heavily modifying the Xen kernel source code. When it came around to adding this feature to VirtPanel, the dom0 limitations showed exactly why Xen was not a match for VirtPanel.
  3. Xen VPS are nearly always cross-compatible with Qemu/KVM, so it is possible to migrate a Xen server to be a KVM server.
  1. Around the time Oracle acquired VirtualBox, the stability of the software was unacceptable. Entire servers would crash.
  2. Updates broke a lot of our code, several times. The VirtualBox command line changed drastically during our trials and showed almost no code maturity, making it very hard to have a stable control panel.

Next: VPS Templates
Previous: Getting Started » Check if disk I/O throttling is supported by running kernel