Bug 950755
| Summary: | Could not start virtual network 'default': internal error | |||
|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Dulaney <jdulaney> | |
| Component: | dnsmasq | Assignee: | Tomáš Hozza <thozza> | |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 19 | CC: | aquini, berrange, bwalker, clalancette, itamar, jdenemar, jforbes, jyang, laine, libvirt-maint, suren, thozza, veillard, virt-maint | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 977555 (view as bug list) | Environment: | ||
| Last Closed: | 2013-05-04 01:46:04 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: | 977555 | |||
As far as I know, this should be fixed in dnsmasq-2.66rc5 dnsmasq-2.66-1.rc5.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/dnsmasq-2.66-1.rc5.fc19 Package dnsmasq-2.66-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dnsmasq-2.66-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5540/dnsmasq-2.66-2.fc19 then log in and leave karma (feedback). Package dnsmasq-2.66-3.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dnsmasq-2.66-3.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5540/dnsmasq-2.66-3.fc19 then log in and leave karma (feedback). dnsmasq-2.66-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. Can we have this fixed on Fedora 18? (In reply to Suren Karapetyan from comment #6) > Can we have this fixed on Fedora 18? Sure, can you please create F18 Bug? Thanks! |
Description of problem: Using virt-manager, I could not start the virtual network. Could not start virtual network 'default': 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): 1.0.4 How reproducible: Always Steps to Reproduce: 1. In virt-manager, create vm 2. When I get to the network step, it says network not active 3. Continuing, it asks if I want to start virt network 4. Clicking yes, it fails Actual results: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/uihelpers.py", line 657, in validate_network virnet.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2193, in create if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self) libvirtError: 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 Expected results: virt network to start.