From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] memory: Fix up coalesced_io_del not working for KVM
Date: Mon, 19 Aug 2019 17:32:42 +0800 [thread overview]
Message-ID: <20190819093242.GC13560@xz-x1> (raw)
In-Reply-To: <20190817093237.27967-1-peterx@redhat.com>
On Sat, Aug 17, 2019 at 05:32:35PM +0800, Peter Xu wrote:
> I can easily crash QEMU as long as KVM is used with e1000 and reboot
> many times, then I hit this and QEMU aborts [1]:
>
> kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device (28)
Reproducer:
bin=x86_64-softmmu/qemu-system-x86_64
$bin -M q35,accel=kvm,kernel-irqchip=on -smp 8 -m 2G -cpu host \
-device e1000,netdev=net0 \
-netdev user,id=net0,hostfwd=tcp::5555-:22 \
-device e1000,netdev=net1 \
-netdev user,id=net1 \
-device e1000,netdev=net2 \
-netdev user,id=net2 \
-device e1000,netdev=net3 \
-netdev user,id=net3 \
-drive file=/images/default.qcow2,if=none,cache=none,id=drive0 \
-device virtio-blk-pci,drive=drive0
This should crash for no more than 2-3 reboots. The more e1000, the
faster.
Regards,
--
Peter Xu
prev parent reply other threads:[~2019-08-19 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 9:32 [Qemu-devel] [PATCH 0/2] memory: Fix up coalesced_io_del not working for KVM Peter Xu
2019-08-17 9:32 ` [Qemu-devel] [PATCH 1/2] memory: Replace has_coalesced_range with add/del flags Peter Xu
2019-08-19 14:30 ` Paolo Bonzini
2019-08-20 4:52 ` Peter Xu
2019-08-17 9:32 ` [Qemu-devel] [PATCH 2/2] memory: Split zones when do coalesced_io_del() Peter Xu
2019-08-19 14:24 ` Paolo Bonzini
2019-08-19 9:32 ` Peter Xu [this message]
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=20190819093242.GC13560@xz-x1 \
--to=peterx@redhat.com \
--cc=pbonzini@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).