-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QEMU crash when execute device_add and device_del alternately #733
Comments
Is there an out-of-bounds memory access? |
@saranzhou you'd better raise an issue at https://github.com/oracle/qemu, we don't maintain QEMU in this repository. Aside from that, have you tested the latest version of vfio-user client sent by John Johnsons at qemu-devel? CC @jraman567 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When execute device_add and device_del alternately, qemu crashes:
[root@localhost coredump]# virsh qemu-monitor-command testvm --hmp 'device_add vfio-user-pci,socket=/var/run/cntrl,id=testdisk0'
[root@localhost coredump]# virsh qemu-monitor-command testvm --hmp 'device_del testdisk0'
[root@localhost coredump]# virsh qemu-monitor-command testvm --hmp 'device_add vfio-user-pci,socket=/var/run/cntrl,id=testdisk0'
[root@localhost coredump]# virsh qemu-monitor-command testvm --hmp 'device_del testdisk0'
[root@localhost coredump]# virsh qemu-monitor-command testvm --hmp 'device_add vfio-user-pci,socket=/var/run/cntrl,id=testdisk0'
error: Unable to read from monitor: Connection reset by peer
And the coredump stack as follows:
thread_all_bt.log
I have repetitioned for several times, and QEMU always crashes in flatview_destroy process.
oracle qemu branch: vfio-user-dbfix
spdk branch: V22.01
Has anyone ever encountered a similar issue? thanks a lot🙂
The text was updated successfully, but these errors were encountered: