Y yena Renowned Member Nov 18, 2011 378 5 83 Mar 15, 2018 #1 The gnulinux-4.13.4-1-pve-advanced-3018d25a67c6ca88 and gnulinux-4.13.13-6-pve-advanced-3018d25a67c6ca88 Have serius bug that on LXC env cause kworker 100% usage. Only way is to boot with the old gnulinux-4.10.15-1. Tested on 7 different server.
The gnulinux-4.13.4-1-pve-advanced-3018d25a67c6ca88 and gnulinux-4.13.13-6-pve-advanced-3018d25a67c6ca88 Have serius bug that on LXC env cause kworker 100% usage. Only way is to boot with the old gnulinux-4.10.15-1. Tested on 7 different server.
tom Proxmox Staff Member Staff member Aug 29, 2006 15,896 1,148 273 Mar 15, 2018 #2 Can you do additional tests with the new 4.15 kernel? https://forum.proxmox.com/threads/4-15-based-test-kernel-for-pve-5-x-available.42097/
Can you do additional tests with the new 4.15 kernel? https://forum.proxmox.com/threads/4-15-based-test-kernel-for-pve-5-x-available.42097/
V Vasu Sreekumar Active Member Mar 3, 2018 123 36 28 55 St Louis MO USA Mar 15, 2018 #3 I had same issue running kernel 4.13 with 25 live nodes, Kworker using 100% CPU. Now I moved all 25 live nodes to 4.15 kernel, no issues so far.
I had same issue running kernel 4.13 with 25 live nodes, Kworker using 100% CPU. Now I moved all 25 live nodes to 4.15 kernel, no issues so far.