From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1656234 <1656234@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1656234] [NEW] Qemu core dumped if using virtio-net
Date: Mon, 16 Jan 2017 13:36:41 +0000 [thread overview]
Message-ID: <20170116133641.GF14681@stefanha-x1.localdomain> (raw)
In-Reply-To: <20170113084022.20152.24498.malonedeb@wampee.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
On Fri, Jan 13, 2017 at 08:40:22AM -0000, Robert Hu wrote:
> Public bug reported:
>
> System Environment
> =======
> Qemu commit/branch: e92fbc75
> Host OS: RHEL7.2 ia32e
> Host Kernel: 4.9.0
> Guest OS: RHEL7.2 ia32e
> Guest Kernel: 4.9.0
>
> Bug detailed description
> =======
> While create a kvm guest using virtio-net, the qemu will core dump with showing "Aborted (core dumped)".
> Reproduce Steps
> ==============
> create a guest:
> qemu-system-x86_64 -enable-kvm -m 4096 -smp 4 -device virtio-net-pci,netdev=nic0,mac=00:16:3e:49:be:24 -netdev tap,id=nic0,script=/etc/kvm/qemu-ifup -drive file=/ia32e_rhel7u2_kvm.qcow2,if=none,id=virtio-disk0 -device virtio-blk-pci,drive=virtio-disk0 -serial file:serial.log
>
> Current Result:
> ==============
>
> qemu-system-x86_64: /workspace/ia32e/nightly/kvm-next-20170105-ef85b6-e92fbc/kvm/qemu/hw/virtio/virtio.c:214: virtio_queue_set_notification: Assertion `vq->notification_disabled > 0' failed.
> Aborted (core dumped)
Thanks for reporting this assertion failure. A patch is queued and will
be merged soon:
https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg02277.html
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-01-16 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 8:40 [Qemu-devel] [Bug 1656234] [NEW] Qemu core dumped if using virtio-net Robert Hu
2017-01-16 13:36 ` Stefan Hajnoczi [this message]
2019-10-23 14:38 ` [Bug 1656234] " Thomas Huth
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=20170116133641.GF14681@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=1656234@bugs.launchpad.net \
--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).