On Mon, 4 Jul 2016 00:20, Ciro Iriarte wrote:
2016-07-03 17:43 GMT-04:00 Yamaban wrote:
On Sun, 3 Jul 2016 23:07, Ciro Iriarte wrote:
Hi!,
I'm building a new NAS box (Leap + btrfs) which is a little over powered so I would love to use it as a personal virtualization lab.
Xenserver/ESXi/Proxmox/Acropolis are out because of software R6 and having a single host, so I'm turning to openSUSE. I've worked a lot with Xen years ago but I understand the guys that get all the attention these days are KVM and docker, and Xen might be a second class citizen.
Given I would like: - Software R6 on the host - Virtualization nesting - PCI passthrough - Some permanent VMs - Lots of temporary VMs
Would you suggest to go with XEN or KVM or Virtualbox in this specific scenario at this point in time?, can I assume docker will place nice with any of them?.
Short, incomplete answer: * XEN, KVM, Virtualbox, and VMware are all full virtual machines, and can run any client system. * LXC, and Docker are 'paravirtual' and as such can only run the same 'base' system, here Linux
- Full virtual systems allow greater freedom at the cost of a higher overhead. - paravirtual systems allow nearly the same compartmentalisation at much less overhead, but effective run the same kernel as the base (bare metal) machine.
It's a trade off.
Docker on Leap 42.1 per se plays nice with most of the images from hub.docker.com (some run better / performanter on a Debian base system, but for most cases that can be safely ignored)
The plus of docker is less configuration needed to start, but also as negative, less configurable compared to, - say KVM for example.
Check what you really need. - just a safe environment to run php? -- Docker wins. - some tricky extra on BSD? -- KVM for the win.
I'm not preaching one or the other, it's a matter of use case and familiarity (and thus ease of use)
- Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Thanks Yamaban, I understand docker is completely different solution (I've played with Solaris containers and Virtuozzo in the past) and it's on my ToDo list, my question was directly related to KVM vs Xen vs Virtualbox for this personal lab :)
I see you mentioned KVM, any reason not to use Virtualbox or Xen?.
Regards,
Honesty here: VMware and Virtualbox have the same problem: Kernelupdates of the Base system. Their Kernel modules need to be recomplied after every Kernelupdate. As long as I do not NEED a grapical interface from the VM I avoid both like pest, AIDS and lepra. On Xen, well I've never gotten warm with it in the past, so my (positive) experiance is very limited, so I'll neither argue for or against. KVM is the VM that is the best documented at this time, fully integrated in the kernel development, no extra compile at Kernel-update, and has a very active community. As it is, in case of troubles, the best help you can get for a VM is on KVM (at least at this time) Docker is great to isolate a single server-app per container and thus limit attack surface from the outside, as well as reducing impact of breaking or corruption of the server-app inside in the container. On "R6" I have no knowledge at all, but VM stacking / nesting I've seen working with KVM, and PCI passtrough is a matter of correct configuration. - Yamaban PS: I'm not the "last instance" on VM, more a opportunistic user. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org