https://bugzilla.kernel.org/show_bug.cgi?id=197861 bubez (michele.mase@xxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michele.mase@xxxxxxxxx --- Comment #37 from bubez (michele.mase@xxxxxxxxx) --- Host: ubuntu 17.10, vanilla kernel 4.14.12, nested virtualization and vhost_net workaround aplied options kvm_intel nested=1 options vhost_net experimental_zcopytx=0 Problem: can always be reproduced on redhat/centos7.x, after about 8 hour of guest uptime, guest machine hangs How to reproduce: boot a centos/redhat7.x guest vm (a minimal installation should be ok), and wait about 8hours, the period may vary. You can give a tail command on syslog to see some detailed message (for example tail -f /var/log/messages) Guest kernel: 3.10.0-693.11.6.el7.x86_64 Syslog output: /var/log/messages Jan 10 12:56:03 kvm178 dbus[756]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Jan 10 12:56:03 kvm178 dhclient[911]: bound to 192.168.122.178 -- renewal in 1257 seconds. Jan 10 12:56:28 kvm178 dbus[756]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out Jan 10 12:56:28 kvm178 dbus-daemon: dbus[756]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out Jan 10 12:58:40 kvm178 kernel: INFO: task systemd:1 blocked for more than 120 seconds. Jan 10 12:58:40 kvm178 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 10 12:58:40 kvm178 kernel: systemd D ffff88004d1d8000 0 1 0 0x00000000 Jan 10 12:58:40 kvm178 kernel: Call Trace: Jan 10 12:58:40 kvm178 kernel: [<ffffffff816ab6d9>] schedule+0x29/0x70 Jan 10 12:58:40 kvm178 kernel: [<ffffffff810625bf>] kvm_async_pf_task_wait+0x1df/0x230 Jan 10 12:58:40 kvm178 kernel: [<ffffffff810b34b0>] ? wake_up_atomic_t+0x30/0x30 Jan 10 12:58:40 kvm178 kernel: [<ffffffff816afc00>] ? error_swapgs+0x61/0x18d Jan 10 12:58:40 kvm178 kernel: [<ffffffff816afcef>] ? error_swapgs+0x150/0x18d Jan 10 12:58:40 kvm178 kernel: [<ffffffff816b32d6>] do_async_page_fault+0x96/0xd0 Jan 10 12:58:40 kvm178 kernel: [<ffffffff816af928>] async_page_fault+0x28/0x30 Jan 10 13:00:40 kvm178 kernel: INFO: task systemd:1 blocked for more than 120 seconds. Jan 10 13:00:40 kvm178 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 10 13:00:40 kvm178 kernel: systemd D ffff88004d1d8000 0 1 0 0x00000000 Jan 10 13:00:40 kvm178 kernel: Call Trace: Jan 10 13:00:40 kvm178 kernel: [<ffffffff816ab6d9>] schedule+0x29/0x70 Jan 10 13:00:40 kvm178 kernel: [<ffffffff810625bf>] kvm_async_pf_task_wait+0x1df/0x230 Jan 10 13:00:40 kvm178 kernel: [<ffffffff810b34b0>] ? wake_up_atomic_t+0x30/0x30 Jan 10 13:00:40 kvm178 kernel: [<ffffffff816afc00>] ? error_swapgs+0x61/0x18d Jan 10 13:00:40 kvm178 kernel: [<ffffffff816afcef>] ? error_swapgs+0x150/0x18d Jan 10 13:00:40 kvm178 kernel: [<ffffffff816b32d6>] do_async_page_fault+0x96/0xd0 Jan 10 13:00:40 kvm178 kernel: [<ffffffff816af928>] async_page_fault+0x28/0x30 Jan 10 13:01:26 kvm178 systemd-logind: Failed to start session scope session-23.scope: Connection timed out Jan 10 13:02:40 kvm178 kernel: INFO: task systemd:1 blocked for more than 120 seconds. Jan 10 13:02:40 kvm178 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 10 13:02:40 kvm178 kernel: systemd D ffff88004d1d8000 0 1 0 0x00000000 Jan 10 13:02:40 kvm178 kernel: Call Trace: Jan 10 13:02:40 kvm178 kernel: [<ffffffff816ab6d9>] schedule+0x29/0x70 Jan 10 13:02:40 kvm178 kernel: [<ffffffff810625bf>] kvm_async_pf_task_wait+0x1df/0x230 Jan 10 13:02:40 kvm178 kernel: [<ffffffff810b34b0>] ? wake_up_atomic_t+0x30/0x30 Jan 10 13:02:40 kvm178 kernel: [<ffffffff816afc00>] ? error_swapgs+0x61/0x18d Jan 10 13:02:40 kvm178 kernel: [<ffffffff816afcef>] ? error_swapgs+0x150/0x18d Jan 10 13:02:40 kvm178 kernel: [<ffffffff816b32d6>] do_async_page_fault+0x96/0xd0 Jan 10 13:02:40 kvm178 kernel: [<ffffffff816af928>] async_page_fault+0x28/0x30 Jan 10 13:04:40 kvm178 kernel: INFO: task systemd:1 blocked for more than 120 seconds. Jan 10 13:04:40 kvm178 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 10 13:04:40 kvm178 kernel: systemd D ffff88004d1d8000 0 1 0 0x00000000 Jan 10 13:04:40 kvm178 kernel: Call Trace: Jan 10 13:04:40 kvm178 kernel: [<ffffffff816ab6d9>] schedule+0x29/0x70 Jan 10 13:04:40 kvm178 kernel: [<ffffffff810625bf>] kvm_async_pf_task_wait+0x1df/0x230 Jan 10 13:04:40 kvm178 kernel: [<ffffffff810b34b0>] ? wake_up_atomic_t+0x30/0x30 Jan 10 13:04:40 kvm178 kernel: [<ffffffff816afc00>] ? error_swapgs+0x61/0x18d Jan 10 13:04:40 kvm178 kernel: [<ffffffff816afcef>] ? error_swapgs+0x150/0x18d Jan 10 13:04:40 kvm178 kernel: [<ffffffff816b32d6>] do_async_page_fault+0x96/0xd0 Jan 10 13:04:40 kvm178 kernel: [<ffffffff816af928>] async_page_fault+0x28/0x30 Jan 10 13:06:40 kvm178 kernel: INFO: task systemd:1 blocked for more than 120 seconds. Jan 10 13:06:40 kvm178 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 10 13:06:40 kvm178 kernel: systemd D ffff88004d1d8000 0 1 0 0x00000000 Jan 10 13:06:40 kvm178 kernel: Call Trace: Jan 10 13:06:40 kvm178 kernel: [<ffffffff816ab6d9>] schedule+0x29/0x70 Jan 10 13:06:40 kvm178 kernel: [<ffffffff810625bf>] kvm_async_pf_task_wait+0x1df/0x230 Jan 10 13:06:40 kvm178 kernel: [<ffffffff810b34b0>] ? wake_up_atomic_t+0x30/0x30 Jan 10 13:06:40 kvm178 kernel: [<ffffffff816afc00>] ? error_swapgs+0x61/0x18d Jan 10 13:06:40 kvm178 kernel: [<ffffffff816afcef>] ? error_swapgs+0x150/0x18d Jan 10 13:06:40 kvm178 kernel: [<ffffffff816b32d6>] do_async_page_fault+0x96/0xd0 Jan 10 13:06:40 kvm178 kernel: [<ffffffff816af928>] async_page_fault+0x28/0x30 Jan 10 13:08:40 kvm178 kernel: INFO: task systemd:1 blocked for more than 120 seconds. Jan 10 13:08:40 kvm178 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 10 13:08:40 kvm178 kernel: systemd D ffff88004d1d8000 0 1 0 0x00000000 Jan 10 13:08:40 kvm178 kernel: Call Trace: Jan 10 13:08:40 kvm178 kernel: [<ffffffff816ab6d9>] schedule+0x29/0x70 Jan 10 13:08:40 kvm178 kernel: [<ffffffff810625bf>] kvm_async_pf_task_wait+0x1df/0x230 Jan 10 13:08:40 kvm178 kernel: [<ffffffff810b34b0>] ? wake_up_atomic_t+0x30/0x30 Jan 10 13:08:40 kvm178 kernel: [<ffffffff816afc00>] ? error_swapgs+0x61/0x18d Jan 10 13:08:40 kvm178 kernel: [<ffffffff816afcef>] ? error_swapgs+0x150/0x18d Jan 10 13:08:40 kvm178 kernel: [<ffffffff816b32d6>] do_async_page_fault+0x96/0xd0 Jan 10 13:08:40 kvm178 kernel: [<ffffffff816af928>] async_page_fault+0x28/0x30 Jan 10 13:10:40 kvm178 kernel: INFO: task systemd:1 blocked for more than 120 seconds. Jan 10 13:10:40 kvm178 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 10 13:10:40 kvm178 kernel: systemd D ffff88004d1d8000 0 1 0 0x00000000 Jan 10 13:10:40 kvm178 kernel: Call Trace: Jan 10 13:10:40 kvm178 kernel: [<ffffffff816ab6d9>] schedule+0x29/0x70 Jan 10 13:10:40 kvm178 kernel: [<ffffffff810625bf>] kvm_async_pf_task_wait+0x1df/0x230 Jan 10 13:10:40 kvm178 kernel: [<ffffffff810b34b0>] ? wake_up_atomic_t+0x30/0x30 Jan 10 13:10:40 kvm178 kernel: [<ffffffff816afc00>] ? error_swapgs+0x61/0x18d Jan 10 13:10:40 kvm178 kernel: [<ffffffff816afcef>] ? error_swapgs+0x150/0x18d Jan 10 13:10:40 kvm178 kernel: [<ffffffff816b32d6>] do_async_page_fault+0x96/0xd0 Jan 10 13:10:40 kvm178 kernel: [<ffffffff816af928>] async_page_fault+0x28/0x30 Jan 10 13:12:40 kvm178 kernel: INFO: task systemd:1 blocked for more than 120 seconds. Jan 10 13:12:40 kvm178 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 10 13:12:40 kvm178 kernel: systemd D ffff88004d1d8000 0 1 0 0x00000000 Jan 10 13:12:40 kvm178 kernel: Call Trace: Jan 10 13:12:40 kvm178 kernel: [<ffffffff816ab6d9>] schedule+0x29/0x70 Jan 10 13:12:40 kvm178 kernel: [<ffffffff810625bf>] kvm_async_pf_task_wait+0x1df/0x230 Jan 10 13:12:40 kvm178 kernel: [<ffffffff810b34b0>] ? wake_up_atomic_t+0x30/0x30 Jan 10 13:12:40 kvm178 kernel: [<ffffffff816afc00>] ? error_swapgs+0x61/0x18d Jan 10 13:12:40 kvm178 kernel: [<ffffffff816afcef>] ? error_swapgs+0x150/0x18d Jan 10 13:12:40 kvm178 kernel: [<ffffffff816b32d6>] do_async_page_fault+0x96/0xd0 Jan 10 13:12:40 kvm178 kernel: [<ffffffff816af928>] async_page_fault+0x28/0x30 Jan 10 13:14:40 kvm178 kernel: INFO: task systemd:1 blocked for more than 120 seconds. Jan 10 13:14:40 kvm178 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 10 13:14:40 kvm178 kernel: systemd D ffff88004d1d8000 0 1 0 0x00000000 Jan 10 13:14:40 kvm178 kernel: Call Trace: Jan 10 13:14:40 kvm178 kernel: [<ffffffff816ab6d9>] schedule+0x29/0x70 Jan 10 13:14:40 kvm178 kernel: [<ffffffff810625bf>] kvm_async_pf_task_wait+0x1df/0x230 Jan 10 13:14:40 kvm178 kernel: [<ffffffff810b34b0>] ? wake_up_atomic_t+0x30/0x30 Jan 10 13:14:40 kvm178 kernel: [<ffffffff816afc00>] ? error_swapgs+0x61/0x18d Jan 10 13:14:40 kvm178 kernel: [<ffffffff816afcef>] ? error_swapgs+0x150/0x18d Jan 10 13:14:40 kvm178 kernel: [<ffffffff816b32d6>] do_async_page_fault+0x96/0xd0 Jan 10 13:14:40 kvm178 kernel: [<ffffffff816af928>] async_page_fault+0x28/0x30 Jan 10 13:16:40 kvm178 kernel: INFO: task systemd:1 blocked for more than 120 seconds. Jan 10 13:16:40 kvm178 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 10 13:16:40 kvm178 kernel: systemd D ffff88004d1d8000 0 1 0 0x00000000 Jan 10 13:16:40 kvm178 kernel: Call Trace: Jan 10 13:16:40 kvm178 kernel: [<ffffffff816ab6d9>] schedule+0x29/0x70 Jan 10 13:16:40 kvm178 kernel: [<ffffffff810625bf>] kvm_async_pf_task_wait+0x1df/0x230 Jan 10 13:16:40 kvm178 kernel: [<ffffffff810b34b0>] ? wake_up_atomic_t+0x30/0x30 Jan 10 13:16:40 kvm178 kernel: [<ffffffff816afc00>] ? error_swapgs+0x61/0x18d Jan 10 13:16:40 kvm178 kernel: [<ffffffff816afcef>] ? error_swapgs+0x150/0x18d Jan 10 13:16:40 kvm178 kernel: [<ffffffff816b32d6>] do_async_page_fault+0x96/0xd0 Jan 10 13:16:40 kvm178 kernel: [<ffffffff816af928>] async_page_fault+0x28/0x30 .... guest died, guest cpu 100%, hard reset on guest needed. Guests with redhat/centos6.x (kernel 2.6.32-696.18.7.el6.x86_64) and windows10 doesn't have problems. Hope this could help. -- You are receiving this mail because: You are watching the assignee of the bug.
