Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
wycliff:~# virsh net-start default
error: Failed to start network default
error: internal error Child process (/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf) unexpected exit status 2:
dnsmasq: failed to set SO_REUSE{ADDR|PORT} on DHCP socket: Protocol not available
Version-Release number of selected component (if applicable):
libvirt-1.0.4-1.el7.x86_64
qemu-kvm-1.4.0-2.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.try to start a virtual machine
2.OK, so that failed because of missing network
3.try to start network
Actual results:
fails with the above error
Expected results:
it shouldn't fail, and in fact the default network should be running on its own
Additional info:
Tested dnsmasq-2.65-1.el7 with
libvirt-1.0.4-1.el7
qemu-kvm-1.4.0-2.el7
on RHEL7 (kernel 3.7.0-0.36.el7.x86_64)
and everything works just fine.
# virsh net-info default
Name default
UUID 104d068f-56d2-4fa3-b070-bd25aab87066
Active: yes
Persistent: yes
Autostart: yes
Bridge: virbr0
# ps aux | grep dnsmasq
nobody 1099 0.0 0.0 13188 696 ? S 20:19 0:00 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf
Do you have any more specific steps to reproduce?
Finally I see the problem with the newest dnsmasq. It seems to be already fixed in dnsmasq-2.66rc5. I'll rebase the package and let you know so you can test it.
Description of problem: wycliff:~# virsh net-start default error: Failed to start network default error: internal error Child process (/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf) unexpected exit status 2: dnsmasq: failed to set SO_REUSE{ADDR|PORT} on DHCP socket: Protocol not available Version-Release number of selected component (if applicable): libvirt-1.0.4-1.el7.x86_64 qemu-kvm-1.4.0-2.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.try to start a virtual machine 2.OK, so that failed because of missing network 3.try to start network Actual results: fails with the above error Expected results: it shouldn't fail, and in fact the default network should be running on its own Additional info: