Proxmox ve 6 syslog lxcfs

[juniper]

Hi,

after upgrading to proxmox 6 from 5.4 i find in syslog:

Aug  6 10:44:31 ********** lxcfs[1265]: bindings.c: 4526: cpuview_proc_stat: cpu7 from /lxc/116/ns has unexpected cpu time: 22174 in /proc/stat, 22450 in cpuacct.usage_all; unable to determine idle time
Aug  6 10:44:31 ********** lxcfs[1265]: bindings.c: 4526: cpuview_proc_stat: cpu8 from /lxc/116/ns has unexpected cpu time: 21419 in /proc/stat, 21436 in cpuacct.usage_all; unable to determine idle time
Aug  6 10:44:31 ********** lxcfs[1265]: bindings.c: 4526: cpuview_proc_stat: cpu34 from /lxc/116/ns has unexpected cpu time: 22312 in /proc/stat, 22560 in cpuacct.usage_all; unable to determine idle time
Aug  6 10:44:31 ********** lxcfs[1265]: bindings.c: 4526: cpuview_proc_stat: cpu36 from /lxc/116/ns has unexpected cpu time: 22147 in /proc/stat, 22231 in cpuacct.usage_all; unable to determine idle time
Aug  6 10:44:31 ********** lxcfs[1265]: bindings.c: 4526: cpuview_proc_stat: cpu7 from /lxc/116/ns has unexpected cpu time: 22174 in /proc/stat, 22450 in cpuacct.usage_all; unable to determine idle time
Aug  6 10:44:31 ********** lxcfs[1265]: bindings.c: 4526: cpuview_proc_stat: cpu8 from /lxc/116/ns has unexpected cpu time: 21419 in /proc/stat, 21436 in cpuacct.usage_all; unable to determine idle time
Aug  6 10:44:31 ********** lxcfs[1265]: bindings.c: 4526: cpuview_proc_stat: cpu34 from /lxc/116/ns has unexpected cpu time: 22312 in /proc/stat, 22560 in cpuacct.usage_all; unable to determine idle time
Aug  6 10:44:31 ********** lxcfs[1265]: bindings.c: 4526: cpuview_proc_stat: cpu36 from /lxc/116/ns has unexpected cpu time: 22147 in /proc/stat, 22231 in cpuacct.usage_all; unable to determine idle time

some hints?

 

[Stefan_R]

This has already been discussed here, and seems to be just a harmless debug log. Are you experiencing any actual performance issues with your container?

 

[juniper]

This has already been discussed here, and seems to be just a harmless debug log. Are you experiencing any actual performance issues with your container?

No it seems all ok....and today disappeared...