From: Cornelia Huck <cohuck@redhat.com>
To: Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>, Cindy Lu <lulu@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: [BUG] vhost-vdpa: qemu-system-s390x crashes with second virtio-net-ccw device
Date: Fri, 24 Jul 2020 15:27:18 +0200 [thread overview]
Message-ID: <20200724152718.4e1cbc9e.cohuck@redhat.com> (raw)
When I start qemu with a second virtio-net-ccw device (i.e. adding
-device virtio-net-ccw in addition to the autogenerated device), I get
a segfault. gdb points to
#0 0x000055d6ab52681d in virtio_net_get_config (vdev=<optimized out>,
config=0x55d6ad9e3f80 "RT") at /home/cohuck/git/qemu/hw/net/virtio-net.c:146
146 if (nc->peer->info->type == NET_CLIENT_DRIVER_VHOST_VDPA) {
(backtrace doesn't go further)
Starting qemu with no additional "-device virtio-net-ccw" (i.e., only
the autogenerated virtio-net-ccw device is present) works. Specifying
several "-device virtio-net-pci" works as well.
Things break with 1e0a84ea49b6 ("vhost-vdpa: introduce vhost-vdpa net
client"), 38140cc4d971 ("vhost_net: introduce set_config & get_config")
works (in-between state does not compile).
This is reproducible with tcg as well. Same problem both with
--enable-vhost-vdpa and --disable-vhost-vdpa.
Have not yet tried to figure out what might be special with
virtio-ccw... anyone have an idea?
[This should probably be considered a blocker?]
next reply other threads:[~2020-07-24 13:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 13:27 Cornelia Huck [this message]
2020-07-24 13:30 ` [BUG] vhost-vdpa: qemu-system-s390x crashes with second virtio-net-ccw device Michael S. Tsirkin
2020-07-24 14:56 ` Cornelia Huck
2020-07-24 15:17 ` Michael S. Tsirkin
2020-07-24 15:34 ` Cornelia Huck
2020-07-25 0:40 ` Jason Wang
2020-07-27 6:43 ` Cornelia Huck
2020-07-27 7:38 ` Jason Wang
2020-07-27 8:41 ` Cornelia Huck
2020-07-27 8:51 ` Jason Wang
2020-07-27 11:43 ` Michael S. Tsirkin
2020-07-27 12:44 ` Jason Wang
2020-07-27 13:16 ` Michael S. Tsirkin
2020-07-28 4:10 ` Jason Wang
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=20200724152718.4e1cbc9e.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=lulu@redhat.com \
--cc=mst@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 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).