<div dir="ltr"><div>Very interesting! <br></div><div><br></div><div>So, after reading this, I installed vzctl-core on my fedora 21 box, from the stock repositories, and just for giggles, I issued the command "vzctl create 101".</div><div><br></div><div>It did the right thing and created a default Centos 6 container. </div><div><br></div><div>However, I immediately noticed that the vzlist command is missing. Excuse the dumb question, but what is the new way to list vz containers?</div><div><br></div><div>Thanks & Regards,</div><div><br></div><div>JJ</div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 28, 2014 at 12:17 PM, James Bottomley <span dir="ltr"><<a href="mailto:jbottomley@parallels.com" target="_blank">jbottomley@parallels.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sun, 2014-12-28 at 11:03 -0800, Keith Keller wrote:<br>
> Hi Kir,<br>
><br>
> On 2014-12-27, Kir Kolyshkin <<a href="mailto:kir@openvz.org">kir@openvz.org</a>> wrote:<br>
> ><br>
> > On 12/27/2014 03:12 AM, Benjamin Henrion wrote:<br>
> >> Any chance to see openvz against mainline one day?<br>
> ><br>
> > Maybe this is rarely visible, but we are working hard on it for the last<br>
><br>
> [snip]<br>
><br>
> It's possible Benjamin may be asking about actually running OpenVZ<br>
> against a mainline kernel. Right now, according to the docs, that is an<br>
> experimental and incomplete feature:<br>
><br>
> <a href="http://openvz.org/Vzctl_for_upstream_kernel" target="_blank">http://openvz.org/Vzctl_for_upstream_kernel</a><br>
><br>
> The quick install docs still recommend using the OpenVZ-supported kernel.<br>
><br>
> <a href="http://openvz.org/Quick_installation" target="_blank">http://openvz.org/Quick_installation</a><br>
><br>
> So maybe a better way of asking this question might be, are there any<br>
> plans to make the upstream kernel the officially supported kernel for<br>
> OpenVZ? It may take a while to transition that direction, but it'd be<br>
> good to know whether that's even planned, or whether the OpenVZ kernel<br>
> will still be maintained and recommended for full OpenVZ functionality.<br>
<br>
</span>Probably not, in the same way the officially supported kernel of RHEL<br>
isn't upstream. What we intend to do is to follow upstream (and<br>
upstream first) in the same way Red Hat does. However, we have the same<br>
problem RHEL does in that we need a kernel that's correctly configured<br>
and has been QA'd and may need some additional patches backporting<br>
(because container features we need in OpenVZ may be ahead of what's in<br>
the current upstream or being pushed upstream) before we can offer<br>
support.<br>
<br>
The goal is to reduce the size of the patch that has to be applied, but<br>
even if the patch diff reaches zero, we'd still have to build the<br>
supported kernel for you because supporting what someone else builds<br>
becomes a massive fishing expedition into how it was built and<br>
configured. Also note that container development doesn't stop just<br>
because everything that was in OpenVZ has gone upstream, so the vzkernel<br>
will probably be the first one to contain the new features on upstream<br>
track and that alone, given that Parallels is the major developer of new<br>
container features, will probably keep the patch diff non-zero.<br>
<br>
However, as of kernel 3.14, enough of OpenVZ is upstream to bring up<br>
OpenVZ containers on the vanilla kernel. To enable this, there are<br>
versions of vzctl in Fedora and Debian at least. You need to make sure<br>
the kernel is configured properly (all the cgroups and namespaces turned<br>
on including CONFIG_USER_NS) and it's still missing the kernel memory<br>
isolation accounting (without this, one container can kill the system by<br>
running it out of kernel resources, like inodes or dentries) but unless<br>
you have hostile applications, this is unlikely to be a problem. Please<br>
don't report bugs against this configuration and even if you use the<br>
mailing list, make sure to say you're using a custom kernel (an<br>
preferably try to see if the bug is still present with the official vz<br>
kernel).<br>
<br>
Finally, we do think that after one more go around at the Linux Storage,<br>
Filesystem and MM summit in March, we should get the kernel memory<br>
accounting patches into 3.19 or 3.20.<br>
<span class="HOEnZb"><font color="#888888"><br>
James Bottomley<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@openvz.org">Users@openvz.org</a><br>
<a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div></div>