RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1607796 - Extra error reported when failed to start guest
Summary: Extra error reported when failed to start guest
Keywords:
Status: CLOSED DUPLICATE of bug 1607831
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Han Han
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-24 09:44 UTC by yafu
Modified: 2018-07-26 23:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-26 23:29:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description yafu 2018-07-24 09:44:08 UTC 
Description of problem:
Extra error reported when failed to start guest

Version-Release number of selected component (if applicable):
libvirt-4.5.0-4.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Edit guest xml with a big iothreads(no nwfilter setting in guest):
#virsh edit iommu1
<iothreads>10000</iothreads>

2.Start the guest:
#virsh start iommu1
error: Failed to start domain iommu1
error: internal error: qemu unexpectedly closed the monitor: qemu-kvm: util/qemu-thread-posix.c:131: qemu_cond_destroy: Assertion `cond->initialized' failed.

3.Check the syslog:
#cat /var/log/messages
Jul 24 05:40:07 dell-per730-44 libvirtd: 72835: error : qemuMonitorIORead:609 : Unable to read from monitor: Connection reset by peer
Jul 24 05:40:07 dell-per730-44 libvirtd: 72835: error : qemuProcessReportLogError:1899 : internal error: qemu unexpectedly closed the monitor: qemu-kvm: util/qemu-thread-posix.c:131: qemu_cond_destroy: Assertion `cond->initialized' failed.
Jul 24 05:40:07 dell-per730-44 kernel: virbr0: port 2(vnet0) entered disabled state
Jul 24 05:40:07 dell-per730-44 libvirtd: 72837: error : ****virNWFilterBindingLookupByPortDev:589 : portdev in virNWFilterBindingLookupByPortDev must not be NULL*****


Actual results:
Extra erro reported:
Jul 24 05:40:07 dell-per730-44 libvirtd: 72837: error : ****virNWFilterBindingLookupByPortDev:589 : portdev in virNWFilterBindingLookupByPortDev must not be NULL*****


Expected results:
Should not report extra error.

Additional info:
Comment 2 Han Han 2018-07-26 14:15:37 UTC 
Well, it is a qemu assertion failure caused by to many threads. Should libvirt limit the max number of iothreads?
Comment 3 yafu 2018-07-26 14:54:11 UTC 
(In reply to Han Han from comment #2)
> Well, it is a qemu assertion failure caused by to many threads. Should
> libvirt limit the max number of iothreads?

The error about iothreads is expected. The error about nwfilter is unreasonable, since i have no nlfilter setting in my guest.
Comment 4 Fangge Jin 2018-07-26 23:29:26 UTC 
It looks same as Bug 1607831 - Error message about nwfilter promoted when fail to start vm.
If you think they are different, feel free to reopen it. Thanks.

*** This bug has been marked as a duplicate of bug 1607831 ***
Note You need to log in before you can comment on or make changes to this bug.