You run a hypervisor on the server before you run anything else on it. EXT3 file system seemed to be the trick - so if you get stuck and are having trouble with the Ubuntu crashing on reboot (and tons of grub errors) you might want to keep that in mind. What it came down to for me after I got it set up was the realization that EXT2 (which 12 uses as default I believe) running those Ubuntu templates messed with Grub. I do have Ubuntu 12 and 14 running on Xen, and I know there are steps that you can use to modify the template to create the VM, and yes, install fresh, but the challenge is that the templates didn't work well even with modification. Containers are implemented via other solutions like LXD, systemd-nspawn, containerd and others.I would rather you run Hyper-V (and I'm a Xen guy) or perhaps KVM, as Xen is going to be a challenge to set up and maintain Ubuntu 12 unless they've bettered their templates which last time I checked with 6.2 XenServer they hadn't. While virtualisation is similar to containers in many ways, they are also different. QEMU provides the user-space backend for the KVM experience, but it also can be used for hardware without virtualisation extensions through its Tiny Code Generator (TCG) mode. KVM is also available for IBM Z and LinuxONE, IBM POWER, and ARM64. For Intel and AMD hardware, KVM requires virtualisation extensions. The default virtualisation technology supported by Ubuntu is KVM. If you are a systems administrator, you can use virtualisation to more easily separate your services and move them around based on demand.

If you are a developer, virtualisation provides you with a contained environment where you can safely do almost any sort of development without messing up your main working environment. Virtualisation is being adopted in many different environments and situations.

Multi-node configuration with Docker-Composeĭistributed Replicated Block Device (DRBD)

Ubuntu server virtualization