From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Doug Goldstein <cardoe@cardoe.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] assert hit on master with q35 machine type
Date: Tue, 10 Jan 2017 16:01:54 +0000 [thread overview]
Message-ID: <20170110160154.GD17540@stefanha-x1.localdomain> (raw)
In-Reply-To: <20170109130852.GE2541@work-vm>
[-- Attachment #1: Type: text/plain, Size: 1814 bytes --]
On Mon, Jan 09, 2017 at 01:08:53PM +0000, Dr. David Alan Gilbert wrote:
> copying in Stefan since it's his commit.
>
> * Doug Goldstein (cardoe@cardoe.com) wrote:
> > I'm currently hitting an assert on master. I've bisected the change down
> > to aff8fd18f1786fc5af259a9bc0077727222f51ca but obviously that's a false
> > positive because that adds the assert for the condition. So obviously
> > the issue was introduced prior to this. As another data point the issue
> > only occurs with q35 machines and will only happen with pc-q35-2.7 and
> > pc-q35-2.8 (and obviously the aliased q35). If I use pc-q35-2.6 it does
> > not hit.
> >
> > The message is: qemu-system-x86_64:
> > /home/doug/work/qemu/hw/virtio/virtio.c:214:
> > virtio_queue_set_notification: Assertion `vq->notification_disabled > 0'
> > failed.
> >
> > But that clearly just shows its the assert that was added in that
> > commit. To create the machine I use the following command line:
> >
> > ./work/qemu/x86_64-softmmu/qemu-system-x86_64 -enable-kvm -M pc-q35-2.8
> > -device intel-iommu -cpu host -m 2048 -smp 2 -drive
> > if=pflash,format=raw,file=/tmp/tmp.Sno2BP3saP -global
> > isa-debugcon.iobase=0x402 -debugcon file:/tmp/tmp.KCrwM98Mus -monitor
> > stdio -chardev socket,host=127.0.0.1,port=4455,id=S0,server,nowait
> > -device isa-serial,chardev=S0 -device piix3-usb-uhci -device usb-tablet
> > -netdev id=net0,type=tap -device virtio-net-pci,netdev=net0 -boot
> > order=n -device qxl-vga -gdb tcp::1234
> >
> > It happens almost right away. Let me know how I can help track this down
> > further.
I can't reproduce the assertion failure.
Are you able to provide a backtrace (e.g. launch QEMU under gdb and then
use the 'bt' command after the assertion failure is raised)?
Thanks,
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-01-10 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 1:45 [Qemu-devel] assert hit on master with q35 machine type Doug Goldstein
2017-01-09 13:08 ` Dr. David Alan Gilbert
2017-01-10 16:01 ` Stefan Hajnoczi [this message]
2017-01-11 1:22 ` Doug Goldstein
2017-01-11 17:26 ` Stefan Hajnoczi
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=20170110160154.GD17540@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=cardoe@cardoe.com \
--cc=dgilbert@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).