public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
* [Bug 220793] New: If Qemu VM using VHOST/VIRTIO quits kernel crashes
@ 2025-11-19  8:22 bugzilla-daemon
  0 siblings, 0 replies; only message in thread
From: bugzilla-daemon @ 2025-11-19  8:22 UTC (permalink / raw)
  To: kvm

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

            Bug ID: 220793
           Summary: If Qemu VM using VHOST/VIRTIO quits kernel crashes
           Product: Virtualization
           Version: unspecified
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P3
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: aliqrudi@gmail.com
        Regression: No

Created attachment 308953
  --> https://bugzilla.kernel.org/attachment.cgi?id=308953&action=edit
Kernel call trace

The problem happens if a Qemu VM using vhost/virtio receives packets at
a very high rate.  After Qemu's quit command or when the VM is rebooted,
the kernel panics.  The problem is easy to reproduce; we tried different
kernel versions, including 6.1.158 and the mainline, with the same result.
We also reproduced the problem with both Mellanox ConnectX-6 and Intel
XL710 NICs.  The VM is run in Debian 12 using Qemu-7.2.19, on a machine
with AMD Ryzen 9 processor and 192GB of memory.

I have to note that while Qemu's quit command triggers the problem,
if Qemu is killed with SIGTERM, nothing happens.  Kernel's call trace
is included at the end of this email.

-- 
You may reply to this email to add a comment.

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2025-11-19  8:22 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-11-19  8:22 [Bug 220793] New: If Qemu VM using VHOST/VIRTIO quits kernel crashes bugzilla-daemon

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