Am 16. Februar 2018 12:54:18 MEZ schrieb Ben Myatt :
>Hi,
>
>I have checked my ifconfig and you were correct, it was set to
>venet0:0. I have changed this which now gets rid of the I/O error, but
>I know get the following:
>lscpu: failed to determine number of CPUs:
Hi,
I have checked my ifconfig and you were correct, it was set to venet0:0. I have
changed this which now gets rid of the I/O error, but I know get the following:
lscpu: failed to determine number of CPUs: /sys/devices/system/cpu/possible: No
such file or directory
Within the directory
Am 15. Februar 2018 20:40:19 MEZ schrieb Ben Myatt :
>Hi,
>
>I don’t believe this is the case as the containers only have 1 IP
>address and the newer ones being on Debian 9, the ifconfig setup should
>be the latest.
>
>I will double check though.
>
>Kind Regards
>Ben Myatt
Hi,
I don’t believe this is the case as the containers only have 1 IP address and
the newer ones being on Debian 9, the ifconfig setup should be the latest.
I will double check though.
Kind Regards
Ben Myatt
> On 15 Feb 2018, at 18:18, Robert Paschedag wrote:
>
>
Am 15. Februar 2018 18:54:06 MEZ schrieb Ben Myatt :
>Hi,
>
>I am trying to register a Debian 9 client with spacewalk 2.7. The
>client is configured as a container on a CentOS 7 host, running openvz,
>virtuozzo kernel 2.6.32-042stab127.2. It has also been tested with a
Hi,
I am trying to register a Debian 9 client with spacewalk 2.7. The client is
configured as a container on a CentOS 7 host, running openvz, virtuozzo kernel
2.6.32-042stab127.2. It has also been tested with a newer kernel version of
3.10.0-693.11.6.vz7.42.5.
I can get CentOS containers