Bug 1271060
| Summary: | virtio_pci_set_host_notifier_internal: unable to init event notifier: -24 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | mazhang <mazhang> |
| Component: | qemu-kvm-rhev | Assignee: | Thomas Huth <thuth> |
| Status: | CLOSED ERRATA | QA Contact: | Xu Han <xuhan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.2 | CC: | hannsj_uhl, knoel, michen, mrezanin, mst, qzhang, thuth, virt-maint, zhengtli |
| Target Milestone: | rc | ||
| Target Release: | 7.4 | ||
| Hardware: | ppc64le | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-2.8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 23:29:42 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1359843 | ||
|
Description
mazhang
2015-10-13 05:36:57 UTC
The "-24" means EMFILE - "Too many open files". Does it work if you increase the maximum possible number of open file descriptors? (not sure, but I think you can do that with "ulimit -n") (In reply to Thomas Huth from comment #2) > The "-24" means EMFILE - "Too many open files". Does it work if you increase > the maximum possible number of open file descriptors? (not sure, but I think > you can do that with "ulimit -n") Setting needinfo(reporter) (In reply to Thomas Huth from comment #2) > The "-24" means EMFILE - "Too many open files". Does it work if you increase > the maximum possible number of open file descriptors? (not sure, but I think > you can do that with "ulimit -n") Test on 3.10.0-327.5.1.el7.ppc64le and qemu-kvm-rhev-2.3.0-31.el7_2.5.ppc64le. Those messages gone after increase the maximum possible number of open file descriptors. Ok, so how should we proceed here? Would it be acceptable to simply improve the error message with a hint that the number of possible open file descriptors should be increased with "ulimit -n"? (In reply to Thomas Huth from comment #5) > Ok, so how should we proceed here? Would it be acceptable to simply improve > the error message with a hint that the number of possible open file > descriptors should be increased with "ulimit -n"? Summary: virtio_pci_set_host_notifier_internal: unable to init event notifier: -24 means "Too many open files", and it will works if increase the maximum possible number of open file descriptors. Base on 902632#c10 and 1124311#c29, close this bug is ok. If any problem please let me know. Thanks, Mazhang. Okay, we've concluced the "this doesn't work" aspect actually "works as designed". What's left ist the "this error message could use improvement" aspect: we should print strerror(number) instead of number. I've now suggested a patch for this upstream: http://news.gmane.org/find-root.php?message_id=1467065523-13881-1-git-send-email-thuth@redhat.com (note that upstream, the code has been moved around there a little bit, in downstream the code is in hw/virtio/virtio-pci.c instead) *** Bug 1370356 has been marked as a duplicate of this bug. *** Patch has been merged in upstream now, so the improved error message should be included in QEMU 2.8: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=a8bba0ada41b228e4dd5113a02f20bbc0f5d6f0a Verified this bug with qemu-kvm-rhev-2.8.0-5.el7.ppc64le. Steps: Same as comment 0. Results: Error messages became more readable. 2017-02-28T01:58:27.307667Z qemu-kvm: virtio_bus_set_host_notifier: unable to init event notifier: Too many open files (-24) 2017-02-28T01:58:27.328345Z qemu-kvm: virtio_bus_start_ioeventfd: failed. Fallback to userspace (slower). And these would gone after increased the maximum possible number of open file descriptors. So, the bug has been fixed. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 |