Re: [Users] A container won't start on upgraded openvz server

On 12/30/2019 05:17 PM, Dmitry Konstantinov wrote: > Nothing of value in dmesg. > > === > ploop58143: p1 > ploop58143: p1 > ploop58143: p1 > ploop58143: p1 > EXT4-fs (ploop58143p1): mounted filesystem with ordered data mode. > Opts: ,pfcache_csum EXT4-fs (ploop58143p1): loaded balloon from

Re: [Users] A container won't start on upgraded openvz server

Nothing of value in dmesg. === ploop58143: p1 ploop58143: p1 ploop58143: p1 ploop58143: p1 EXT4-fs (ploop58143p1): mounted filesystem with ordered data mode. Opts: ,pfcache_csum EXT4-fs (ploop58143p1): loaded balloon from 12 (0 blocks) EXT4-fs (ploop58143p1): re-mounted. Opts: ,pfcache_cs

Re: [Users] A container won't start on upgraded openvz server

On 12/30/2019 08:24 AM, Dmitry Konstantinov wrote: > Hi there, > > I've got a container based on a not too outdated gentoo (half a year > old). It starts/works OK on this: > > server1# uname -r; rpm -qa | grep vzctl > 3.10.0-957.12.2.vz7.86.2 > vzctl-7.0.201-1.vz7.x86_64 > libvzctl-7.0.515.1-1.vz7.

[Users] A container won't start on upgraded openvz server

Hi there, I've got a container based on a not too outdated gentoo (half a year old). It starts/works OK on this: server1# uname -r; rpm -qa | grep vzctl 3.10.0-957.12.2.vz7.86.2 vzctl-7.0.201-1.vz7.x86_64 libvzctl-7.0.515.1-1.vz7.x86_64 however today a new one created from the same cache won't s