* [Qemu-devel] [Bug 1813940] [NEW] kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
@ 2019-01-30 13:23 Darek Stojaczyk
2019-02-05 18:53 ` [Qemu-devel] [Bug 1813940] " elmarco
` (5 more replies)
0 siblings, 6 replies; 7+ messages in thread
From: Darek Stojaczyk @ 2019-01-30 13:23 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
Latest QEMU master fails to run with too many MMIO devices specified.
After patch 3ac7d43a6fb [1] QEMU just prints an error message and exits.
> kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
This is reproducible e.g. with the following setup:
qemu-3.1.50-dirty \
-machine pc-i440fx-2.7,accel=kvm \
-cpu host -m 4096 \
-smp 2,sockets=2,cores=1,threads=1 \
-drive file=freebsd_vm_1.qcow2,format=qcow2,if=none,id=bootdr \
-device ide-hd,drive=bootdr,bootindex=0 \
-device virtio-scsi-pci,id=vc0 \
-device virtio-scsi-pci,id=vc1 \
-device virtio-scsi-pci,id=vc2 \
-device virtio-scsi-pci,id=vc3 \
Running with just 3 Virtio-SCSI controllers seems to work fine, adding
more than that causes the error above. Note that this is not Virtio-SCSI
specific. I've also reproduced this without any Virtio devices
whatsoever.
strace shows the following ioctl chain over and over:
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
Which suggests there's some kind of MMIO region leak.
[1]
commit 3ac7d43a6fbb5d4a3d01fc9a055c218030af3727
Author: Paolo Bonzini <pbonzini@redhat.com>
AuthorDate: Wed Nov 28 17:28:45 2018 +0100
Commit: Paolo Bonzini <pbonzini@redhat.com>
CommitDate: Fri Jan 11 13:57:24 2019 +0100
memory: update coalesced_range on transaction_commit
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1813940
Title:
kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
Status in QEMU:
New
Bug description:
Latest QEMU master fails to run with too many MMIO devices specified.
After patch 3ac7d43a6fb [1] QEMU just prints an error message and exits.
> kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
This is reproducible e.g. with the following setup:
qemu-3.1.50-dirty \
-machine pc-i440fx-2.7,accel=kvm \
-cpu host -m 4096 \
-smp 2,sockets=2,cores=1,threads=1 \
-drive file=freebsd_vm_1.qcow2,format=qcow2,if=none,id=bootdr \
-device ide-hd,drive=bootdr,bootindex=0 \
-device virtio-scsi-pci,id=vc0 \
-device virtio-scsi-pci,id=vc1 \
-device virtio-scsi-pci,id=vc2 \
-device virtio-scsi-pci,id=vc3 \
Running with just 3 Virtio-SCSI controllers seems to work fine, adding
more than that causes the error above. Note that this is not Virtio-
SCSI specific. I've also reproduced this without any Virtio devices
whatsoever.
strace shows the following ioctl chain over and over:
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
Which suggests there's some kind of MMIO region leak.
[1]
commit 3ac7d43a6fbb5d4a3d01fc9a055c218030af3727
Author: Paolo Bonzini <pbonzini@redhat.com>
AuthorDate: Wed Nov 28 17:28:45 2018 +0100
Commit: Paolo Bonzini <pbonzini@redhat.com>
CommitDate: Fri Jan 11 13:57:24 2019 +0100
memory: update coalesced_range on transaction_commit
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1813940/+subscriptions
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Qemu-devel] [Bug 1813940] Re: kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
2019-01-30 13:23 [Qemu-devel] [Bug 1813940] [NEW] kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device Darek Stojaczyk
@ 2019-02-05 18:53 ` elmarco
2019-02-05 20:25 ` Paolo Bonzini
` (4 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: elmarco @ 2019-02-05 18:53 UTC (permalink / raw)
To: qemu-devel
The bug is also reproducible with virtio-9p
-fsdev local,id=r,path=/,security_model=none -device virtio-9p-pci,fsdev=r,mount_tag=r
I bisected it to the same commit.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1813940
Title:
kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
Status in QEMU:
New
Bug description:
Latest QEMU master fails to run with too many MMIO devices specified.
After patch 3ac7d43a6fb [1] QEMU just prints an error message and exits.
> kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
This is reproducible e.g. with the following setup:
qemu-3.1.50-dirty \
-machine pc-i440fx-2.7,accel=kvm \
-cpu host -m 4096 \
-smp 2,sockets=2,cores=1,threads=1 \
-drive file=freebsd_vm_1.qcow2,format=qcow2,if=none,id=bootdr \
-device ide-hd,drive=bootdr,bootindex=0 \
-device virtio-scsi-pci,id=vc0 \
-device virtio-scsi-pci,id=vc1 \
-device virtio-scsi-pci,id=vc2 \
-device virtio-scsi-pci,id=vc3 \
Running with just 3 Virtio-SCSI controllers seems to work fine, adding
more than that causes the error above. Note that this is not Virtio-
SCSI specific. I've also reproduced this without any Virtio devices
whatsoever.
strace shows the following ioctl chain over and over:
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
Which suggests there's some kind of MMIO region leak.
[1]
commit 3ac7d43a6fbb5d4a3d01fc9a055c218030af3727
Author: Paolo Bonzini <pbonzini@redhat.com>
AuthorDate: Wed Nov 28 17:28:45 2018 +0100
Commit: Paolo Bonzini <pbonzini@redhat.com>
CommitDate: Fri Jan 11 13:57:24 2019 +0100
memory: update coalesced_range on transaction_commit
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1813940/+subscriptions
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Qemu-devel] [Bug 1813940] Re: kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
2019-01-30 13:23 [Qemu-devel] [Bug 1813940] [NEW] kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device Darek Stojaczyk
2019-02-05 18:53 ` [Qemu-devel] [Bug 1813940] " elmarco
@ 2019-02-05 20:25 ` Paolo Bonzini
2019-02-06 14:29 ` Philippe Mathieu-Daudé
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Paolo Bonzini @ 2019-02-05 20:25 UTC (permalink / raw)
To: qemu-devel
Hmm that's not surprising because coalesced ranges were completely
broken before that commit. I'll take a look.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1813940
Title:
kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
Status in QEMU:
New
Bug description:
Latest QEMU master fails to run with too many MMIO devices specified.
After patch 3ac7d43a6fb [1] QEMU just prints an error message and exits.
> kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
This is reproducible e.g. with the following setup:
qemu-3.1.50-dirty \
-machine pc-i440fx-2.7,accel=kvm \
-cpu host -m 4096 \
-smp 2,sockets=2,cores=1,threads=1 \
-drive file=freebsd_vm_1.qcow2,format=qcow2,if=none,id=bootdr \
-device ide-hd,drive=bootdr,bootindex=0 \
-device virtio-scsi-pci,id=vc0 \
-device virtio-scsi-pci,id=vc1 \
-device virtio-scsi-pci,id=vc2 \
-device virtio-scsi-pci,id=vc3 \
Running with just 3 Virtio-SCSI controllers seems to work fine, adding
more than that causes the error above. Note that this is not Virtio-
SCSI specific. I've also reproduced this without any Virtio devices
whatsoever.
strace shows the following ioctl chain over and over:
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
Which suggests there's some kind of MMIO region leak.
[1]
commit 3ac7d43a6fbb5d4a3d01fc9a055c218030af3727
Author: Paolo Bonzini <pbonzini@redhat.com>
AuthorDate: Wed Nov 28 17:28:45 2018 +0100
Commit: Paolo Bonzini <pbonzini@redhat.com>
CommitDate: Fri Jan 11 13:57:24 2019 +0100
memory: update coalesced_range on transaction_commit
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1813940/+subscriptions
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Qemu-devel] [Bug 1813940] Re: kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
2019-01-30 13:23 [Qemu-devel] [Bug 1813940] [NEW] kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device Darek Stojaczyk
2019-02-05 18:53 ` [Qemu-devel] [Bug 1813940] " elmarco
2019-02-05 20:25 ` Paolo Bonzini
@ 2019-02-06 14:29 ` Philippe Mathieu-Daudé
2019-02-13 9:31 ` Darek Stojaczyk
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Philippe Mathieu-Daudé @ 2019-02-06 14:29 UTC (permalink / raw)
To: qemu-devel
Does this patch from Jagannathan Raman fixes it?
https://lists.gnu.org/archive/html/qemu-devel/2019-02/msg01397.html
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1813940
Title:
kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
Status in QEMU:
Confirmed
Bug description:
Latest QEMU master fails to run with too many MMIO devices specified.
After patch 3ac7d43a6fb [1] QEMU just prints an error message and exits.
> kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
This is reproducible e.g. with the following setup:
qemu-3.1.50-dirty \
-machine pc-i440fx-2.7,accel=kvm \
-cpu host -m 4096 \
-smp 2,sockets=2,cores=1,threads=1 \
-drive file=freebsd_vm_1.qcow2,format=qcow2,if=none,id=bootdr \
-device ide-hd,drive=bootdr,bootindex=0 \
-device virtio-scsi-pci,id=vc0 \
-device virtio-scsi-pci,id=vc1 \
-device virtio-scsi-pci,id=vc2 \
-device virtio-scsi-pci,id=vc3 \
Running with just 3 Virtio-SCSI controllers seems to work fine, adding
more than that causes the error above. Note that this is not Virtio-
SCSI specific. I've also reproduced this without any Virtio devices
whatsoever.
strace shows the following ioctl chain over and over:
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
Which suggests there's some kind of MMIO region leak.
[1]
commit 3ac7d43a6fbb5d4a3d01fc9a055c218030af3727
Author: Paolo Bonzini <pbonzini@redhat.com>
AuthorDate: Wed Nov 28 17:28:45 2018 +0100
Commit: Paolo Bonzini <pbonzini@redhat.com>
CommitDate: Fri Jan 11 13:57:24 2019 +0100
memory: update coalesced_range on transaction_commit
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1813940/+subscriptions
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Qemu-devel] [Bug 1813940] Re: kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
2019-01-30 13:23 [Qemu-devel] [Bug 1813940] [NEW] kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device Darek Stojaczyk
` (2 preceding siblings ...)
2019-02-06 14:29 ` Philippe Mathieu-Daudé
@ 2019-02-13 9:31 ` Darek Stojaczyk
2019-02-13 11:54 ` Dr. David Alan Gilbert
2021-02-03 13:54 ` Thomas Huth
5 siblings, 0 replies; 7+ messages in thread
From: Darek Stojaczyk @ 2019-02-13 9:31 UTC (permalink / raw)
To: qemu-devel
> Does this patch from Jagannathan Raman fixes it?
> https://lists.gnu.org/archive/html/qemu-devel/2019-02/msg01397.html
It fixes my case. Thanks
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1813940
Title:
kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
Status in QEMU:
Confirmed
Bug description:
Latest QEMU master fails to run with too many MMIO devices specified.
After patch 3ac7d43a6fb [1] QEMU just prints an error message and exits.
> kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
This is reproducible e.g. with the following setup:
qemu-3.1.50-dirty \
-machine pc-i440fx-2.7,accel=kvm \
-cpu host -m 4096 \
-smp 2,sockets=2,cores=1,threads=1 \
-drive file=freebsd_vm_1.qcow2,format=qcow2,if=none,id=bootdr \
-device ide-hd,drive=bootdr,bootindex=0 \
-device virtio-scsi-pci,id=vc0 \
-device virtio-scsi-pci,id=vc1 \
-device virtio-scsi-pci,id=vc2 \
-device virtio-scsi-pci,id=vc3 \
Running with just 3 Virtio-SCSI controllers seems to work fine, adding
more than that causes the error above. Note that this is not Virtio-
SCSI specific. I've also reproduced this without any Virtio devices
whatsoever.
strace shows the following ioctl chain over and over:
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
Which suggests there's some kind of MMIO region leak.
[1]
commit 3ac7d43a6fbb5d4a3d01fc9a055c218030af3727
Author: Paolo Bonzini <pbonzini@redhat.com>
AuthorDate: Wed Nov 28 17:28:45 2018 +0100
Commit: Paolo Bonzini <pbonzini@redhat.com>
CommitDate: Fri Jan 11 13:57:24 2019 +0100
memory: update coalesced_range on transaction_commit
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1813940/+subscriptions
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Qemu-devel] [Bug 1813940] Re: kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
2019-01-30 13:23 [Qemu-devel] [Bug 1813940] [NEW] kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device Darek Stojaczyk
` (3 preceding siblings ...)
2019-02-13 9:31 ` Darek Stojaczyk
@ 2019-02-13 11:54 ` Dr. David Alan Gilbert
2021-02-03 13:54 ` Thomas Huth
5 siblings, 0 replies; 7+ messages in thread
From: Dr. David Alan Gilbert @ 2019-02-13 11:54 UTC (permalink / raw)
To: qemu-devel
That also fixes the case I'd hit
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1813940
Title:
kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
Status in QEMU:
Confirmed
Bug description:
Latest QEMU master fails to run with too many MMIO devices specified.
After patch 3ac7d43a6fb [1] QEMU just prints an error message and exits.
> kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
This is reproducible e.g. with the following setup:
qemu-3.1.50-dirty \
-machine pc-i440fx-2.7,accel=kvm \
-cpu host -m 4096 \
-smp 2,sockets=2,cores=1,threads=1 \
-drive file=freebsd_vm_1.qcow2,format=qcow2,if=none,id=bootdr \
-device ide-hd,drive=bootdr,bootindex=0 \
-device virtio-scsi-pci,id=vc0 \
-device virtio-scsi-pci,id=vc1 \
-device virtio-scsi-pci,id=vc2 \
-device virtio-scsi-pci,id=vc3 \
Running with just 3 Virtio-SCSI controllers seems to work fine, adding
more than that causes the error above. Note that this is not Virtio-
SCSI specific. I've also reproduced this without any Virtio devices
whatsoever.
strace shows the following ioctl chain over and over:
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
Which suggests there's some kind of MMIO region leak.
[1]
commit 3ac7d43a6fbb5d4a3d01fc9a055c218030af3727
Author: Paolo Bonzini <pbonzini@redhat.com>
AuthorDate: Wed Nov 28 17:28:45 2018 +0100
Commit: Paolo Bonzini <pbonzini@redhat.com>
CommitDate: Fri Jan 11 13:57:24 2019 +0100
memory: update coalesced_range on transaction_commit
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1813940/+subscriptions
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug 1813940] Re: kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
2019-01-30 13:23 [Qemu-devel] [Bug 1813940] [NEW] kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device Darek Stojaczyk
` (4 preceding siblings ...)
2019-02-13 11:54 ` Dr. David Alan Gilbert
@ 2021-02-03 13:54 ` Thomas Huth
5 siblings, 0 replies; 7+ messages in thread
From: Thomas Huth @ 2021-02-03 13:54 UTC (permalink / raw)
To: qemu-devel
That patch has been included here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=4f8260248c68e4599a5
Thus closing this ticket now.
** Changed in: qemu
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1813940
Title:
kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
Status in QEMU:
Fix Released
Bug description:
Latest QEMU master fails to run with too many MMIO devices specified.
After patch 3ac7d43a6fb [1] QEMU just prints an error message and exits.
> kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
This is reproducible e.g. with the following setup:
qemu-3.1.50-dirty \
-machine pc-i440fx-2.7,accel=kvm \
-cpu host -m 4096 \
-smp 2,sockets=2,cores=1,threads=1 \
-drive file=freebsd_vm_1.qcow2,format=qcow2,if=none,id=bootdr \
-device ide-hd,drive=bootdr,bootindex=0 \
-device virtio-scsi-pci,id=vc0 \
-device virtio-scsi-pci,id=vc1 \
-device virtio-scsi-pci,id=vc2 \
-device virtio-scsi-pci,id=vc3 \
Running with just 3 Virtio-SCSI controllers seems to work fine, adding
more than that causes the error above. Note that this is not Virtio-
SCSI specific. I've also reproduced this without any Virtio devices
whatsoever.
strace shows the following ioctl chain over and over:
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_UNREGISTER_COALESCED_MMIO, 0x7f60a4985410) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = 0
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
145787 ioctl(11, KVM_REGISTER_COALESCED_MMIO, 0x7f60a49853b0) = -1 ENOSPC (No space left on device)
Which suggests there's some kind of MMIO region leak.
[1]
commit 3ac7d43a6fbb5d4a3d01fc9a055c218030af3727
Author: Paolo Bonzini <pbonzini@redhat.com>
AuthorDate: Wed Nov 28 17:28:45 2018 +0100
Commit: Paolo Bonzini <pbonzini@redhat.com>
CommitDate: Fri Jan 11 13:57:24 2019 +0100
memory: update coalesced_range on transaction_commit
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1813940/+subscriptions
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2021-02-03 14:06 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-30 13:23 [Qemu-devel] [Bug 1813940] [NEW] kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device Darek Stojaczyk
2019-02-05 18:53 ` [Qemu-devel] [Bug 1813940] " elmarco
2019-02-05 20:25 ` Paolo Bonzini
2019-02-06 14:29 ` Philippe Mathieu-Daudé
2019-02-13 9:31 ` Darek Stojaczyk
2019-02-13 11:54 ` Dr. David Alan Gilbert
2021-02-03 13:54 ` Thomas Huth
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.