<div dir="ltr"><div>Paulo,</div><div><br></div>The container technology in OpenVZ is OpenVZ. As in:<div><br></div><div>LXD, Rkt, Docker, OpenVZ.</div><div><br></div><div>Here's a little comparison: <a href="https://www.contino.io/insights/beyond-docker-other-types-of-containers">https://www.contino.io/insights/beyond-docker-other-types-of-containers</a></div><div><br></div><div>OpenVZ is one of the oldest container technologies. I believe FreeBSD Jails is probably considered the first.</div><div><br></div><div>-Alex</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 1, 2019 at 5:33 AM Jehan PROCACCIA <<a href="mailto:jehan.procaccia@tem-tsp.eu">jehan.procaccia@tem-tsp.eu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style="font-family:arial,helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"><div style="font-family:arial,helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"><div>Thanks for those comparisons<br></div><div>I still wonder though what is the container technology used by virtuozzo/openVZ7 ? <br></div><div>from <a>https://www.slideshare.net/openvz/whats-missing-from-upstream-kernel-containers-kir-kolyshkin</a> I understand that it is patches to kernel that takes advantages of kernel namespaces, cgroups etc .. ? <br></div><div>is that right ? <br></div><div>other insteresting reading, but probably a little oriented towards lxd ... : <a>https://containerjournal.com/2017/01/09/comparing-openvz-lxd-linux-system-container-platforms/</a><br></div><div>it still beleive that choice between technologies proxmox / virtuozzo is driven by the linux distribution a sysadmin is most familiar with . <br></div><div>anyway, I 'am happy and surprised by the 1st reference above that virtuozzo is that much contributing to the kernel and is so close to a native kernel .</div><br><br><hr id="gmail-m_3529087428860836819zwchr"><div><b>De: </b>"Paulo Coghi - Coghi IT" <<a>paulocoghi@gmail.com</a>><br><b>À: </b>"OpenVZ users" <<a>users@openvz.org</a>><br><b>Envoyé: </b>Lundi 29 Avril 2019 12:26:35<br><b>Objet: </b>Re: [Users] distro virtuozzo vs proxmox<br></div><br><div><div dir="ltr"><div>My 2 cents.<br></div><div><br>*OpenVZ vs LXC*<br></div><div>OpenVZ requires a patched kernel, but it's finally updated with OVZ7<br></div><div>OpenVZ is gradually porting its technology to mainline Linux kernel<br></div><div>OpenVZ has a more battle tested OS virtualization technology<br></div><div>LXC is still more insecure<br></div><div>LXC has a more complex way to configure networks<br><br></div><div>*Virtuozzo vs Proxmox*<br></div><div>Virtuozzo better integrates OpenVZ with its features and capabilities, like live migration, distributed storage, live snapshots, etc<br></div><div>Virtuozzo is made and maintained by the same company that maintains OpenVZ itself, and buying its licenses helps the future of OpenVZ<br></div><div>Virtuozzo includes specialized tools to manage and ensure the healthy of your distributed storage cluster, subdivides it in different layers of performance and purpose, etc<br></div><div>Virtuozzo has a great and responsive support team, in my experience<br></div><div>Virtuozzo enhanced KVM a lot, that provides more server density and performance<br></div><div>Virtuozzo is one of the main KVM contributors, and contributes to other projects as well, as Linux Kernel, OpenStack, etc<br></div><div>Proxmox was famous when offered OpenVZ on its platform (not offering anymore, replacing it by LXC)<br></div><div>Proxmox is made and maintained by a company not related to OpenVZ project itself<br></div><div>Proxmox has a great and responsive support team, in my experience</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 29, 2019 at 10:48 AM Narcis Garcia <<a>informatica@actiu.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Yes, these are the right comparisons:<br>
<br>
OpenVZ vs LXC<br>
Virtuozzo distro vs Proxmox distro<br>
CentOS vs Debian vs Other general purpose distros<br>
<br>
+ Interesting to know the support to run OpenVZ 7 on CentOS.<br>
It should be documented at OpenVZ wiki!<br>
<br>
<br>
El 29/4/19 a les 4:16, Website Solution - George ha escrit:<br>
> <br>
> From my understanding, Virtuozzo 7 (or OpenVZ 7) supports user quota<br>
> inside guest container.<br>
> <br>
> However, for unprivileged LXC guest, it does not support quota inside<br>
> container natively.<br>
> <br>
> It is important if we run the guest container for multiple end-users.<br>
> <br>
> (Privileged LXC guests support user quota inside container, but they<br>
> share the same root UID between guest and host, which implies some kind<br>
> of potential security)<br>
> <br>
> <br>
> <br>
> On 29-Apr-19 3:55 AM, Jehan PROCACCIA wrote:<br>
>> regarding distros and virtuozzo vs proxmox (reason I modified the<br>
>> subject, orig: SSD trim support over a LUKS layer)<br>
>> I understand that it could be frustrating to rely on a dedidcated<br>
>> distro (virtuozzo 7), but I guess it comes with simplicity and<br>
>> consistency regarding set of packages and updates<br>
>> after all it's very similar to centos/rhel 7 as it is based on it, and<br>
>> if you wish , you could add openvz7 feature to native centos7 :<br>
>> <a rel="noreferrer">https://enjoyko.blogspot.com/2018/05/how-to-install-openvz-7-to-centos-7.html</a><br>
>><br>
>><br>
>> I guess that <a rel="noreferrer">https://wiki.openvz.org/Comparison</a> is quite up to date as<br>
>> it dates from jan/2019<br>
>> but i am still wondering what technology virtuozzo 7 uses for<br>
>> containers if not LXC ?<br>
>><br>
>> I'll be glad to know as I have regularly discussions between sysadmins<br>
>> around proxmox and virtuozzo , and finally it ends on debian vs<br>
>> centos/rhel !<br>
>><br>
>> ----- Mail original -----<br>
>> De: "Narcis Garcia" <<a>informatica@actiu.net</a>><br>
>> À: "OpenVZ users" <<a>users@openvz.org</a>><br>
>> Envoyé: Samedi 27 Avril 2019 19:19:43<br>
>> Objet: Re: [Users] SSD trim support over a LUKS layer<br>
>><br>
>> The problem of Virtuozzo 7 for me is that this is a distro.<br>
>> I prefer to use general purpose distros, for many reasons around<br>
>> packaged software, community support, future plans and others.<br>
>><br>
>><br>
>> El 27/4/19 a les 19:09, Paulo Coghi - Coghi IT ha escrit:<br>
>>> LXC is far to be an option, IMHO.<br>
>>><br>
>>> I'm happily using Virtuozzo 7 with multiple NVMe storages with zero<br>
>>> issues for more than a year.<br>
>>><br>
>>> On Sat, Apr 27, 2019 at 4:28 PM CoolCold <<a>coolthecold@gmail.com</a><br>
>>> <mailto:<a>coolthecold@gmail.com</a>>> wrote:<br>
>>><br>
>>> I believe to have fixes and backports like this in to legacy<br>
>>> version<br>
>>> of product will not happen, and you should consider upgrading.<br>
>>> Personally, I've upgraded to lxc.. it's quite primitive<br>
>>> comparing to<br>
>>> ovz 6, but it's enough for my needs.<br>
>>><br>
>>> On Sat, Apr 27, 2019, 17:49 spameden <<a>spameden@gmail.com</a><br>
>>> <mailto:<a>spameden@gmail.com</a>>> wrote:<br>
>>><br>
>>> Yes, it's an issue in kernel.<br>
>>><br>
>>> As dm-crypt/luks layer isn't passing TRIM to the underlying<br>
>>> device.<br>
>>><br>
>>> /boot is not encrypted that's why it works for you.<br>
>>><br>
>>> сб, 27 апр. 2019 г. в 11:11, Narcis Garcia<br>
>>> <<a>informatica@actiu.net</a> <mailto:<a>informatica@actiu.net</a>>>:<br>
>>><br>
>>> See in the case that /dev/sda1 (Directly mounted as Ext4 on<br>
>>> /boot) works with Trim/Discard.<br>
>>> It's the sda2_crypt (layer over sda2) that is not detected<br>
>>> to be trimmable. Devuan's stock kernel does.<br>
>>><br>
>>> CentOS issue #6548 may not be this same bug; I've tested<br>
>>> now<br>
>>> with CentOS 6.8 with a similar (but not same) result*:*<br>
>>><br>
>>> $ lsb_release -d<br>
>>> Description: CentOS release 6.8 (Final)<br>
>>><br>
>>> $ uname -a<br>
>>> Linux localhost.localdomain 2.6.32-642.el6.x86_64 #1 SMP<br>
>>> Tue<br>
>>> May 10 17:27:01 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux<br>
>>><br>
>>> $ lsblk --discard /dev/sda<br>
>>> NAME<br>
>>> DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO<br>
>>> sda<br>
>>> 0 512B 2G 0<br>
>>> ├─sda1<br>
>>> 0 512B 2G 0<br>
>>> └─sda2<br>
>>> 0 512B 2G 0<br>
>>> └─luks-f691f48b-8556-487d-ac64-50daa99ed4c9 (dm-0)<br>
>>> 0 512B 2G 0<br>
>>><br>
>>> $ cat /etc/crypttab<br>
>>> luks-f691f48b-8556-487d-ac64-50daa99ed4c9<br>
>>> UUID=f691f48b-8556-487d-ac64-50daa99ed4c9 none luks,discard<br>
>>><br>
>>> $ mount | grep -e discard<br>
>>> /dev/mapper/luks-f691f48b-8556-487d-ac64-50daa99ed4c9 on /<br>
>>> type ext4 (rw,discard)<br>
>>> /dev/sda1 on /boot type ext4 (rw,discard)<br>
>>><br>
>>> $ sudo fstrim /boot<br>
>>> # (same result as Devuan/1 and OpenVZ/6 kernel: success)<br>
>>><br>
>>> $ sudo fstrim /<br>
>>> fstrim: /: FITRIM ioctl failed: Operation not supported<br>
>>><br>
>>><br>
>>> El 26/4/19 a les 21:36, spameden ha escrit:<br>
>>>> Hi.<br>
>>>><br>
>>>> I've asked this question years ago (in<br>
>>>> <br>
>>>> 2013): <a rel="noreferrer">https://lists.openvz.org/pipermail/users/2013-August/005250.html</a><br>
>>>><br>
>>>> Let me know if it helps, but this bug should have been<br>
>>>> fixed in CentOS and RHEL at<br>
>>>> least: <a rel="noreferrer">https://bugs.centos.org/view.php?id=6548</a><br>
>>>><br>
>>>> Maybe OpenVZ maintainers didn't pick up this fix in the<br>
>>>> openvz6 legacy kernel?<br>
>>>><br>
>>>> Thanks.<br>
>>>><br>
>>>> ср, 10 апр. 2019 г. в 10:45, Narcis Garcia<br>
>>>> <<a>informatica@actiu.net</a> <mailto:<a>informatica@actiu.net</a>>>:<br>
>>>><br>
>>>> Does anybody know how can I solve this?<br>
>>>><br>
>>>> $ lsb_release -d<br>
>>>> Description: Devuan GNU/Linux 1.0 (jessie)<br>
>>>><br>
>>>> $ uname -a<br>
>>>> Linux bell1 2.6.32-openvz-042stab134.8-amd64 #1 SMP<br>
>>>> Fri Dec 7 17:18:40<br>
>>>> MSK 2018 x86_64 GNU/Linux<br>
>>>><br>
>>>> $ lsblk --discard /dev/sda<br>
>>>> NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO<br>
>>>> sda 0 512B 2G 0<br>
>>>> ├─sda1 0 512B 2G 0<br>
>>>> └─sda2 0 512B 2G 0<br>
>>>> └─sda2_crypt 0 0B 0B 0<br>
>>>><br>
>>>> $ cat /etc/crypttab<br>
>>>> sda2_crypt UUID=***** none luks,discard<br>
>>>><br>
>>>> $ mount | grep -e discard<br>
>>>> /dev/mapper/sda2_crypt on / type ext4<br>
>>>> <br>
>>>> (rw,noatime,errors=remount-ro,barrier=1,data=ordered,discard)<br>
>>>> /dev/sda1 on /boot type ext4<br>
>>>> (rw,relatime,barrier=1,data=ordered,discard)<br>
>>>><br>
>>>> $ sudo fstrim /<br>
>>>> fstrim: /: the discard operation is not supported<br>
>>>><br>
>>>> Thank you.<br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> Users mailing list<br>
>>>> <a>Users@openvz.org</a> <mailto:<a>Users@openvz.org</a>><br>
>>>> <a rel="noreferrer">https://lists.openvz.org/mailman/listinfo/users</a><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> Users mailing list<br>
>>>> <a>Users@openvz.org</a> <mailto:<a>Users@openvz.org</a>><br>
>>>> <a rel="noreferrer">https://lists.openvz.org/mailman/listinfo/users</a><br>
>>> _______________________________________________<br>
>>> Users mailing list<br>
>>> <a>Users@openvz.org</a> <mailto:<a>Users@openvz.org</a>><br>
>>> <a rel="noreferrer">https://lists.openvz.org/mailman/listinfo/users</a><br>
>>><br>
>>> _______________________________________________<br>
>>> Users mailing list<br>
>>> <a>Users@openvz.org</a> <mailto:<a>Users@openvz.org</a>><br>
>>> <a rel="noreferrer">https://lists.openvz.org/mailman/listinfo/users</a><br>
>>><br>
>>> _______________________________________________<br>
>>> Users mailing list<br>
>>> <a>Users@openvz.org</a> <mailto:<a>Users@openvz.org</a>><br>
>>> <a rel="noreferrer">https://lists.openvz.org/mailman/listinfo/users</a><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Users mailing list<br>
>>> <a>Users@openvz.org</a><br>
>>> <a rel="noreferrer">https://lists.openvz.org/mailman/listinfo/users</a><br>
>>><br>
>> _______________________________________________<br>
>> Users mailing list<br>
>> <a>Users@openvz.org</a><br>
>> <a rel="noreferrer">https://lists.openvz.org/mailman/listinfo/users</a><br>
>><br>
>> _______________________________________________<br>
>> Users mailing list<br>
>> <a>Users@openvz.org</a><br>
>> <a rel="noreferrer">https://lists.openvz.org/mailman/listinfo/users</a><br>
> <br>
> _______________________________________________<br>
> Users mailing list<br>
> <a>Users@openvz.org</a><br>
> <a rel="noreferrer">https://lists.openvz.org/mailman/listinfo/users</a><br>
_______________________________________________<br>
Users mailing list<br>
<a>Users@openvz.org</a><br>
<a rel="noreferrer">https://lists.openvz.org/mailman/listinfo/users</a><br>
</blockquote></div></div>
<br>_______________________________________________<br>Users mailing list<br><a>Users@openvz.org</a><br><a>https://lists.openvz.org/mailman/listinfo/users</a></div></div><div><br></div></div></div>_______________________________________________<br>
Users mailing list<br>
<a>Users@openvz.org</a><br>
<a rel="noreferrer">https://lists.openvz.org/mailman/listinfo/users</a><br>
</blockquote></div>