command IOTOP = ksoftirqd/0 99%

stomach · Dec 3, 2017

The iotop command shows that the ksoftirqd process is 99%.

Even with all VMS switched off

stomach · Dec 4, 2017

kobuki · Dec 4, 2017

Can you post outputs?

Code:

pveversion -v
grep '.*' /sys/firmware/acpi/interrupts/*

stomach · Dec 4, 2017

Code:

root@pve:~# pveversion -v
proxmox-ve: 5.1-28 (running kernel: 4.13.8-2-pve)
pve-manager: 5.1-36 (running version: 5.1-36/131401db)
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.13.8-2-pve: 4.13.8-28
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9

Code:

root@pve:~# grep '.*' /sys/firmware/acpi/interrupts/*
/sys/firmware/acpi/interrupts/error:       0
/sys/firmware/acpi/interrupts/ff_gbl_lock:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/ff_pmtimer:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/ff_pwr_btn:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/ff_rt_clk:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/ff_slp_btn:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe00:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe01:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe02:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe03:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe04:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe05:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe06:       4  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe07:       0         enabled      unmasked
/sys/firmware/acpi/interrupts/gpe08:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe09:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe0A:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe0B:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe0C:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe0D:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe0E:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe0F:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe10:       1  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe11:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe12:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe13:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe14:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe15:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe16:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe17:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe18:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe19:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1A:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1B:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe1C:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1D:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1E:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1F:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe20:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe21:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe22:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe23:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe24:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe25:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe26:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe27:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe28:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe29:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2A:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2B:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2C:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2D:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2E:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2F:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe30:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe31:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe32:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe33:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe34:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe35:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe36:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe37:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe38:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe39:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe3A:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe3B:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe3C:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe3D:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe3E:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe3F:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe_all:       5
/sys/firmware/acpi/interrupts/sci:       5
/sys/firmware/acpi/interrupts/sci_not:       0
root@pve:~#

kobuki · Dec 4, 2017

My idea was an old kernel or a misbehaving acpi interrupt. Neither of them seems to be relevant, sorry. I suggest flashing the newest bios or downgrading the kernel to see if it helps.

stomach · Dec 5, 2017

I installed version 4 and it worked. thank you !

kobuki · Dec 5, 2017

You mean PVE 4.4? I dont't believe it's supported for too long if at all... Anyway it looks like a kernel bug surfacing in your setup.

Kei · Dec 7, 2017

I confirm this problem with PVE 5.1-36. I have a couple of VM's shared via iSCSI and I/O delay is around 10 percent with CPU usage at 40 percent... I confirm having couple of instances of ksoftirqd processes at 99% and with PVE 4.x i/O delay was almost zero. Plz help

stomach · Dec 10, 2017

With version 4, there are no problems (it is working perfectly).

My hardware is a bit old (Already exists for 3 years).

Kei · Dec 11, 2017

I would be grateful if someone can find a solution because I would like to keep using version 5.x

Kei · Dec 11, 2017

Please help... this is very burdensome

tom · Dec 11, 2017

try with the latest kernel and check again.

(pve-kernel-4.13.8-3-pve: 4.13.8-30)

mada · Dec 11, 2017

tom said:
try with the latest kernel and check again.

(pve-kernel-4.13.8-3-pve: 4.13.8-30)

I still have this pain in my work even it sometime come with
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
28627 root 20 0 0 0 0 R 99.7 0.0 3652:46 [kworker/u16:0]

This kworker +
ksoftirqd
eat my i/o and CPU each upgrade the kernel just become worse than before. this issue shows up about from pve: 4.10 or so i keep upgrading but no way i need to reboot the node each few days to avoid this issue.

root@xxx# pveversion --v
proxmox-ve: 5.1-30 (running kernel: 4.13.8-3-pve)
pve-manager: 5.1-38 (running version: 5.1-38/1e9bc777)
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.13.8-2-pve: 4.13.8-28
pve-kernel-4.13.8-3-pve: 4.13.8-30
libpve-http-server-perl: 2.0-7
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-22
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-3
pve-container: 2.0-17
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: not correctly installed
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1

Kei · Dec 12, 2017

I've not tryed upgrading yet but I can confirm that in this "old" machine the problem is NOT present:

pveversion --v
proxmox-ve: 4.4-79 (running kernel: 4.4.35-2-pve)
pve-manager: 4.4-12 (running version: 4.4-12/e71b7a74)
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.35-2-pve: 4.4.35-79
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-108
pve-firmware: 1.1-10
libpve-common-perl: 4.0-91
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-73
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-3
pve-qemu-kvm: 2.7.1-1
pve-container: 1.0-93
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-1
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve14~bpo80

Kei · Dec 16, 2017

Problem still there with Linux 4.13.13-1-pve #1 SMP PVE 4.13.13-31.
This is what happens cloning a VM over iSCSI (while in PVE 4.x it just takes 15% at most).
I will go back to PVE 4.x until someone will push a fix for this mess...

mada · Dec 16, 2017

Kei said:
Problem still there with Linux 4.13.13-1-pve #1 SMP PVE 4.13.13-31.
This is what happens cloning a VM over iSCSI (while in PVE 4.x it just takes 15% at most).
I will go back to PVE 4.x until someone will push a fix for this mess...

Do you have LXC and KVM on that node? or KVM only?

Kei · Dec 16, 2017

KVM only.

Andrey Dudin · Dec 16, 2017

I have the same issue.

pveversion -v

Code:

# pveversion -v
proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-35 (running version: 5.1-35/722cc488)
pve-kernel-4.13.4-1-pve: 4.13.4-25
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90

grep '.*' /sys/firmware/acpi/interrupts/*

Code:

# grep '.*' /sys/firmware/acpi/interrupts/*
/sys/firmware/acpi/interrupts/error:       0
/sys/firmware/acpi/interrupts/ff_gbl_lock:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/ff_pmtimer:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/ff_pwr_btn:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/ff_rt_clk:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/ff_slp_btn:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe00:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe01:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe02:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe03:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe04:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe05:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe06:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe07:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe08:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe09:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe0A:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe0B:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe0C:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe0D:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe0E:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe0F:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe10:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe11:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe12:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe13:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe14:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe15:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe16:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe17:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe18:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe19:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1A:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1B:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1C:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1D:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1E:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe1F:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe20:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe21:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe22:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe23:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe24:       5  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe25:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe26:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe27:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe28:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe29:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2A:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2B:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2C:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2D:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2E:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe2F:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe30:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe31:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe32:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe33:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe34:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe35:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe36:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe37:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe38:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe39:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe3A:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe3B:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe3C:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe3D:       0         invalid      unmasked
/sys/firmware/acpi/interrupts/gpe3E:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe3F:       0     STS invalid      unmasked
/sys/firmware/acpi/interrupts/gpe_all:       5
/sys/firmware/acpi/interrupts/sci:       5
/sys/firmware/acpi/interrupts/sci_not:       1

iotop

Code:

TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND                                                                                                      23 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/2]
   17 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/1]
    8 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/0]
   77 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/11]
   71 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/10]
   65 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/9]
   59 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/8]
   53 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/7]
  222 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/35]
  216 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/34]
   47 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/6]
   41 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/5]
   35 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/4]
  210 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/33]
  204 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/32]
   29 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/3]
  198 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/31]
  192 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/30]
  186 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/29]
  162 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/25]
  156 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/24]
  180 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/28]
  174 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/27]
  168 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/26]
  120 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/18]
  108 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/16]
  102 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/15]
   96 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [ksoftirqd/14]
 3357 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 % [kworker/u96:2]

I have same(hardware) node with older versions and this problem is NOT present.
pveversion -v

Code:

# pveversion -v
proxmox-ve: 5.0-19 (running kernel: 4.10.17-2-pve)
pve-manager: 5.0-30 (running version: 5.0-30/5ab26bc)
pve-kernel-4.10.17-2-pve: 4.10.17-19
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-14
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-3
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

Kei · Dec 16, 2017

Hopefully proxmox team will address this problem. This is extremely frustrating

mada · Dec 16, 2017

Kei said:
KVM only.

I had the same issue as well

also sometimes issue with kworker eat my CPU and I/O as well

command IOTOP = ksoftirqd/0 99%

Member

Member

Renowned Member

Member

Renowned Member

Member

Renowned Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Attachments

Proxmox Staff Member

Member

Well-Known Member

Well-Known Member

Attachments

Member

Well-Known Member

New Member

Well-Known Member

Member

We value your privacy