From: Luiz Capitulino <lcapitulino@redhat.com>
To: mst@redhat.com
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] kvm_virtio_pci_irqfd_release: Assertion `ret == 0' failed
Date: Thu, 17 Jan 2013 13:28:48 -0200 [thread overview]
Message-ID: <20130117132848.74cf0e57@doriath.home> (raw)
Hi Michael,
To trigger this I just:
1. Boot the VM, command-line:
# ./qemu -drive file=disks/test.img,if=virtio,cache=none,aio=native \
-enable-kvm -m 1G -monitor stdio \
-netdev type=tap,vhost=on,id=guest0,script=qemu-ifup-switch \
-device virtio-net-pci,netdev=guest0 -cpu host
2. Once the VM is fully booted:
QEMU 1.3.50 monitor - type 'help' for more information
(qemu) q
qemu-qmp: /home/lcapitulino/work/src/qmp-unstable/hw/virtio-pci.c:535: kvm_virtio_pci_irqfd_release: Assertion `ret == 0' failed.
~/work/virt/
Seems to be related with your latest pull request (commit 8e9a8681).
Backtrace:
(gdb) bt
#0 0x00007fa3dee67285 in raise () from /lib64/libc.so.6
#1 0x00007fa3dee68b9b in abort () from /lib64/libc.so.6
#2 0x00007fa3dee5fe9e in __assert_fail_base () from /lib64/libc.so.6
#3 0x00007fa3dee5ff42 in __assert_fail () from /lib64/libc.so.6
#4 0x00007fa3e1522260 in kvm_virtio_pci_irqfd_release (proxy=0x7fa3e41a9440, queue_no=2, vector=1)
at /home/lcapitulino/work/src/qmp-unstable/hw/virtio-pci.c:535
#5 0x00007fa3e15224da in kvm_virtio_pci_vector_release (proxy=0x7fa3e41a9440, nvqs=2)
at /home/lcapitulino/work/src/qmp-unstable/hw/virtio-pci.c:605
#6 0x00007fa3e1522c87 in virtio_pci_set_guest_notifiers (d=0x7fa3e41a9440, nvqs=2, assign=false)
at /home/lcapitulino/work/src/qmp-unstable/hw/virtio-pci.c:785
#7 0x00007fa3e1613c15 in vhost_dev_stop (hdev=0x7fa3e3a89720, vdev=0x7fa3e4444810)
at /home/lcapitulino/work/src/qmp-unstable/hw/vhost.c:1027
#8 0x00007fa3e16143ca in vhost_net_stop (net=0x7fa3e3a89720, dev=0x7fa3e4444810)
at /home/lcapitulino/work/src/qmp-unstable/hw/vhost_net.c:194
#9 0x00007fa3e1617714 in virtio_net_vhost_status (n=0x7fa3e4444810, status=7 '\a')
at /home/lcapitulino/work/src/qmp-unstable/hw/virtio-net.c:137
#10 0x00007fa3e161778b in virtio_net_set_status (vdev=0x7fa3e4444810, status=7 '\a')
at /home/lcapitulino/work/src/qmp-unstable/hw/virtio-net.c:146
#11 0x00007fa3e161792b in virtio_net_set_link_status (nc=0x7fa3e41a45c0) at /home/lcapitulino/work/src/qmp-unstable/hw/virtio-net.c:181
#12 0x00007fa3e1532d9c in qemu_del_net_client (nc=0x7fa3e3a78130) at /home/lcapitulino/work/src/qmp-unstable/net/net.c:271
#13 0x00007fa3e1534681 in net_cleanup () at /home/lcapitulino/work/src/qmp-unstable/net/net.c:919
#14 0x00007fa3dee6a931 in __run_exit_handlers () from /lib64/libc.so.6
#15 0x00007fa3dee6a9b5 in exit () from /lib64/libc.so.6
#16 0x00007fa3dee526a4 in __libc_start_main () from /lib64/libc.so.6
#17 0x00007fa3e13acbc9 in _start ()
(gdb)
next reply other threads:[~2013-01-17 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 15:28 Luiz Capitulino [this message]
2013-01-17 15:50 ` [Qemu-devel] kvm_virtio_pci_irqfd_release: Assertion `ret == 0' failed Michael S. Tsirkin
2013-01-17 15:51 ` Luiz Capitulino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130117132848.74cf0e57@doriath.home \
--to=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).