From: joserz@linux.vnet.ibm.com
To: ghammer@redhat.com, mst@redhat.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] virtio block device is not working
Date: Tue, 23 Jan 2018 01:05:28 -0200 [thread overview]
Message-ID: <20180123030528.GA5780@pacoca> (raw)
Hello people!
I'm not able to boot any guest that sets a virtio block device like:
(branch master)
[PPC64]
qemu-system-ppc64 -cpu POWER8 -nographic -vga none -m 4G -M pseries,accel=kvm,kvm-type=PR -drive file=disk.qcow2,if=virtio
QEMU Starting
Build Date = Dec 18 2017 13:08:00
FW Version = git-fa981320a1e0968d
Press "s" to enter Open Firmware.
Populating /vdevice methods
Populating /vdevice/vty@71000000
Populating /vdevice/nvram@71000001
Populating /vdevice/v-scsi@71000002
SCSI: Looking for devices
8200000000000000 CD-ROM : "QEMU QEMU CD-ROM 2.5+"
Populating /pci@800000020000000
00 0000 (D) : 1af4 1000 virtio [ net ]
Aborted
[x86]
qemu-system-x86_64 -m 4G -enable-kvm -drive file=util.qcow2,if=virtio
Running QEMU with GTK 2.x is deprecated, and will be removed
in a future release. Please switch to GTK 3.x instead
[1] 5282 abort
[Cause]
The commit 4fe6d78b2e introduces the
...
kvm_mem_ioeventfd_del(...) {
...
r = kvm_set_ioeventfd_mmio(fd, ...
if (r < 0) {
abort();
}
+ if (e->cleanup) {
+ e->cleanup(e);
+ }
}
For some reason, not yet clear to me, cleanup() calls the same
kvm_mem_ioeventfd_del again and again until kvm_set_ioeventfd_mmio
returns < 0 and abort().
I was going to send a patch to revert that 'if ()' but I think it could
cause a regression. What do you guys think?
Thanks,
Jose Ricardo Ziviani
next reply other threads:[~2018-01-23 3:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 3:05 joserz [this message]
2018-01-23 12:34 ` [Qemu-devel] virtio block device is not working joserz
2018-01-23 12:47 ` Daniel Henrique Barboza
2018-01-23 13:02 ` Daniel Henrique Barboza
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=20180123030528.GA5780@pacoca \
--to=joserz@linux.vnet.ibm.com \
--cc=ghammer@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).