Comments on Installing And Using OpenVZ On Ubuntu 13.04 (AMD64)
Installing And Using OpenVZ On Ubuntu 13.04 (AMD64) In this HowTo I will describe how to prepare an Ubuntu 13.04 server for OpenVZ. With OpenVZ you can create multiple Virtual Private Servers (VPS) on the same hardware, similar to Xen and the Linux Vserver project. OpenVZ is the open-source branch of Virtuozzo, a commercial virtualization solution used by many providers that offer virtual servers. The OpenVZ kernel patch is licensed under the GPL license, and the user-level tools are under the QPL license.
5 Comment(s)
Comments
i can't booting with vz kernel.
i've got error in boot process:
ALERT! /dev/mapper/ubuntu-root does not exist. Dropping to a shell!there is no /dev/mapper directory and no uuid for lvm in /dev/disk/by-uuid.
i think that vz's kernel have no modules for lvm so can't mount lvm's root filesystem.
during install rpms, we can see below messages
WARNING: could not open /lib/modules/2.6.32-042stab078.28/modules.builtin: No such file or directory
WARNING: could not open /tmp/mkinitramfs_vXC6YN/lib/modules/2.6.32-042stab078.28/modules.builtin: No such file or directory
So i think something is missing in this tutorial.
any idea?
got the same problem bro :/
Simple question. Why? As in "why bother?"
There's a simple reason the OpenVZ kernel is no longer included in Ubuntu. The reason is LXC and Linux containers. What real, practical, advantage does OpenVZ (more specifically the OpenVZ custom patched kernel) offer over that of the mainline 3.x kernel?
We now have cgroups and namespaces in the main-line kernel and the need for this custom patched ongoing maintenance headache (PITA) is largely alleviated. The OpenVZ user space (vzctl et al) will even run over top of the main-line kernels (3.x and a few prior). There are some limitations, but not many and generally requirement specific. The OpenVZ developers have been contributing to the Linux kernel containers and namespace development effort. I routinely see the same names on both -devel mailing lists. Many of the remaining limitations are being addressed.
All that's even if you really want to run the OpenVZ user space. Quite frankly, I migrated off of OpenVZ over to LXC a couple of years ago and not looked back. While it has its limitations, LXC has some versatility that is sadly lacking in OpenVZ (like arbitrary container names, not just numerical IDs). Last time I looked (and this could have very easily changed over the last two years) the OpenVZ kernel patches were also not compatible with the cgroups options and using an OpenVZ kernel disabled your ability to use cgroups for other process management. I would have hoped they would have resolved that by now but it was true back then.
Linus made it abundantly clear years ago that the OpenVZ / Virtuoso
patches would not be accepted into the upstream sources. He had his
reasons and the OpenVZ people shifted gears to support getting
containers into the kernel. That is where we are going. The OpenVZ patched kernel has always lagged and will always lag behind the mainstream kernel and bug fixes will be similarly delayed.
The reference to the Linux Vserver project is also amusing (I use to use them too) since that project hasn't been updated in a couple of years. I abandoned that one years and years ago after they broke IPv6 networking and found OpenVZ to be superior to that.
Thank you for explain!
Ok... So, I should migrate to LXC because I can put some arbitrary name to a container ?
That's a definitive reason... xD
On my opinion live migration, templates, control panels completly overcomes LXC, on a future when LXC is more mature it will rock, but now, LXC isn't for a production enviorenment. Just for testing on that computer no body uses...