public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
* [Bug 60505] New: Heavy network traffic triggers vhost_net lockup
@ 2013-07-04 16:55 bugzilla-daemon
  2013-07-05 15:05 ` [Bug 60505] " bugzilla-daemon
                   ` (6 more replies)
  0 siblings, 7 replies; 8+ messages in thread
From: bugzilla-daemon @ 2013-07-04 16:55 UTC (permalink / raw)
  To: kvm

https://bugzilla.kernel.org/show_bug.cgi?id=60505

            Bug ID: 60505
           Summary: Heavy network traffic triggers vhost_net lockup
           Product: Virtualization
           Version: unspecified
    Kernel Version: 3.9.8
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: bvanassche@acm.org
        Regression: No

When running heavy network traffic between host and guests after some time the
qemu-kvm processes lock up and become unkillable. Apparently these processes
hang in an ioctl. From the output of echo w > /proc/sysrq-trigger:

SysRq : Show Blocked State
 task                        PC stack   pid father
qemu-kvm        D ffff88011fa128c0     0 30506      1 0x00000004
ffff88005dc11d38 0000000000000086 ffff880097c20720 ffff88005dc11fd8
ffff88005dc11fd8 ffff88005dc11fd8 ffffffff81810440 ffff880097c20720
ffff88005dc11d48 ffff88005ddb0058 ffff88005ddb8528 ffff88005ddb0000
Call Trace:
[<ffffffff813fa679>] schedule+0x29/0x70
[<ffffffffa07a39a5>] vhost_work_flush+0xa5/0x120 [vhost_net]
[<ffffffffa07a3b19>] vhost_poll_flush+0x19/0x20 [vhost_net]
[<ffffffffa07a6077>] vhost_net_flush_vq+0x37/0x50 [vhost_net]
[<ffffffffa07a71d2>] vhost_net_ioctl+0x502/0x660 [vhost_net]
[<ffffffff8114bed0>] do_vfs_ioctl+0x90/0x520
[<ffffffff8114c3b0>] sys_ioctl+0x50/0x90
[<ffffffff81403a42>] system_call_fastpath+0x16/0x1b
qemu-kvm        D ffff88011fad28c0     0 30575      1 0x00000004
ffff880097e05d38 0000000000000082 ffff8800a3c50000 ffff880097e05fd8
ffff880097e05fd8 ffff880097e05fd8 ffff88011acd5ca0 ffff8800a3c50000
ffff880097e05d48 ffff8800d41c0058 ffff8800d41c8528 ffff8800d41c0000
Call Trace:
[<ffffffff813fa679>] schedule+0x29/0x70
[<ffffffffa07a39a5>] vhost_work_flush+0xa5/0x120 [vhost_net]
[<ffffffffa07a3b19>] vhost_poll_flush+0x19/0x20 [vhost_net]
[<ffffffffa07a6077>] vhost_net_flush_vq+0x37/0x50 [vhost_net]
[<ffffffffa07a71d2>] vhost_net_ioctl+0x502/0x660 [vhost_net]
[<ffffffff8114bed0>] do_vfs_ioctl+0x90/0x520
[<ffffffff8114c3b0>] sys_ioctl+0x50/0x90
[<ffffffff81403a42>] system_call_fastpath+0x16/0x1b

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2013-08-13 18:58 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-04 16:55 [Bug 60505] New: Heavy network traffic triggers vhost_net lockup bugzilla-daemon
2013-07-05 15:05 ` [Bug 60505] " bugzilla-daemon
2013-07-07  8:39 ` bugzilla-daemon
2013-07-07 11:27 ` bugzilla-daemon
2013-07-08  9:20 ` bugzilla-daemon
2013-07-08 10:09 ` bugzilla-daemon
2013-07-08 10:11 ` bugzilla-daemon
2013-08-13 18:58 ` bugzilla-daemon

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox