One Kernel, many VMs<\/strong><\/h2>OpenVZ\u00a0is actually\u00a0a modified Linux variant —\u00a0this\u00a0version uses the Red Hat Enterprise Linux 3.10 kernel family — where multiple containers, or virtual private servers\/virtual environments (VPSs\/VPEs), can share\u00a0one\u00a0kernel.As a result, Linux\u00a0is that the\u00a0only guest OS\u00a0that may\u00a0run under OpenVZ\u00a0in an exceedingly\u00a0container. That said, those containers\u00a0will be\u00a0booted quickly and run without the overhead of a full-blown hypervisor.<\/span><\/p>The commercial edition of OpenVZ, called Virtuozzo (also the name of\u00a0the corporate\u00a0marketing the product), incorporates OpenVZ but adds enterprise-grade features not found\u00a0within the\u00a0open source release. Virtuozzo\u00a0includes a\u00a0new release of its own alongside OpenVZ 7, named — appropriately enough — Virtuozzo 7.<\/span><\/p>Most of\u00a0the large\u00a0changes announced in OpenVZ 7.0 involve the packaging and deployment of\u00a0the merchandise. It’s now\u00a0a whole\u00a0standalone Linux distribution, with both the commercial Virtuozzo product\u00a0and therefore the\u00a0free OpenVZ distribution\u00a0supported\u00a0the identical\u00a0kernel.<\/p>
For\u00a0those that\u00a0want to run actual VMs, KVM\/QEMU\u00a0will be\u00a0used\u00a0because the\u00a0hypervisor in OpenVZ.\u00a0to create\u00a0management easier and more consistent, OpenVZ now uses the libvirt project\u00a0because the\u00a0standard API for working with full KVM instances, containers, and their attached storage pools or volumes.<\/p>\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t