On 19:36 Thu 11 Feb , Axton wrote:
> Thanks. This is good info. When Virtuozzo goes ga, will i need to
> purchase licenses?
We cannot provide exact dates of vz7 final version.
Buy vz7 license or not depends on you :)
See comparison of the stable version of OpenVZ, opensource version of Vz7
and c
On Wed, 10 Feb 2016 21:05:23 +0100
Volker Janzen wrote:
> if my server for OpenVZ legacy has HDD and SSD, what can I do to
> benefit from SSD speed?
Recently I have tested following solutions for openvz legacy server:
* flashcache 3.1.2 (writeback mode)
* btier 1.3.11
* dm-cache (bundled in
On Fri, 12 Feb 2016 15:01:14 +0300
Andrey Tataranovich wrote:
> On Wed, 10 Feb 2016 21:05:23 +0100
> Volker Janzen wrote:
>
> > if my server for OpenVZ legacy has HDD and SSD, what can I do to
> > benefit from SSD speed?
>
> Recently I have tested following solutions for openvz legacy server:
Template creation fails if /var/tmp is xfs, which is the default file
system on RHEL7. The documentation for installation does not highlight
this requirement for /var/tmp; it does for /vz though. Reference:
https://openvz.org/Quick_installation
Here is the full output. Resolved by formatting /v
On 02/12/2016 08:00 AM, Axton wrote:
Template creation fails if /var/tmp is xfs, which is the default file
system on RHEL7. The documentation for installation does not
highlight this requirement for /var/tmp; it does for /vz though.
Reference:
https://openvz.org/Quick_installation
Please
I came across that same situation while installing some months ago. I just
created a directory on an ext4-formatted partition and symlinked /var/tmp
to that.
On Fri, Feb 12, 2016 at 4:25 PM, Kir Kolyshkin wrote:
>
>
> On 02/12/2016 08:00 AM, Axton wrote:
>
> Template creation fails if /var/tmp i
Yep, no big deal to work around, but the docs should state this as a
requirement. /var/tmp was a separate file system on my machine, so I just
unmounted, reformatted as ext4, updated the fstab entry, then remounted.
On Fri, Feb 12, 2016 at 7:09 PM, jjs - mainphrame
wrote:
> I came across that s
My host's network uses teaming, bridge, and vlan interfaces.
There are 4 physical interfaces: enp0s20f0-enp0s20f3
The 4 physical interfaces are grouped using lacp via teaming.
[root@cluster-02 ~]# teamdctl team0 config dump actual
{
"device": "team0",
"link_watch": {
"name": "etht
