All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-s390x <qemu-s390x@nongnu.org>,
	Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: srange crash in virtio-gpu
Date: Thu, 24 Sep 2020 11:48:25 +0100	[thread overview]
Message-ID: <20200924104825.GD2097005@redhat.com> (raw)
In-Reply-To: <7e21dd39-f251-e883-1a8e-788fc5d85ea0@de.ibm.com>

On Thu, Sep 24, 2020 at 12:35:06PM +0200, Christian Borntraeger wrote:
> Gerd,
> 
> with current master build via a slightly fixed up fedora spec file I do get a crash in virtio-gpu
> when libvirt queries the qemu. 
> I can trigger that also via command line
> 
> $ /usr/bin/qemu-system-s390x -device virtio-gpu-pci,help
> qemu-system-s390x: -device virtio-gpu-pci,help: missing object type 'virtio-gpu-device'
> Aborted (core dumped)
> $ /usr/bin/qemu-system-s390x -device virtio-gpu-ccw,help
> qemu-system-s390x: -device virtio-gpu-ccw,help: missing object type 'virtio-gpu-device'
> Aborted (core dumped)
> 
> Since I cannot reproduce the same when I build it without the spec file this must
> be something configuration specific.

The Fedora spec builds using  --enable-modules, and the error message
shows that you don't have the .so for virtio-gpu on disk.

> The call trace is:
> 
> (gdb) bt
> #0  0x000003ff9e349026 in raise () at /lib64/libc.so.6
> #1  0x000003ff9e32b162 in abort () at /lib64/libc.so.6
> #2  0x000002aa274abfca in object_initialize (data=<optimized out>, size=<optimized out>, typename=0x2aa2754904e "virtio-gpu-device") at ../qom/object.c:531

This abort is evil though

We need this to get into the "Device '<blah>' not found"  code path
to report a nice error.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2020-09-24 10:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 10:35 srange crash in virtio-gpu Christian Borntraeger
2020-09-24 10:48 ` Daniel P. Berrangé [this message]
2020-09-24 11:39   ` Christian Borntraeger

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=20200924104825.GD2097005@redhat.com \
    --to=berrange@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.