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 12 (0 > blocks) EXT4-fs (ploop58143p1): re-mounted. > Opts: ,pfcache_csum,balloon_ino=12 EXT4-fs (ploop58143p1): re-mounted. > Opts: discard > CT: 22: started > CT: 22: stopped > === > > that's all. > strace's output is probably too big for the list.
Sorry, then looks like my simple guess is wrong. Please create a bug and post there vzctl strace and probably it makes sense with vzctl debug logs (/etc/vz/vz.conf LOG_LEVEL=10). Next step - to understand which component is guilty - if you suspect kernel, let's install older kernels and check where the behavior changed. -- Best regards, Konstantin Khorenko, Virtuozzo Linux Kernel Team >>> Any ideas how to fix this? >> >> Any complains in dmesg? >> In particular i suspect something like: >> >> + WARN_ONCE(1, "The process %s from VE0 tried to execute >> untrusted file " >> + "%s from VEX\n", >> + current->comm, name->name); >> >> >> -- >> Best regards, >> >> Konstantin Khorenko, >> Virtuozzo Linux Kernel Team >> >> _______________________________________________ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users > > _______________________________________________ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > . > _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
