Bug 950755 - Could not start virtual network 'default': internal error
Summary: Could not start virtual network 'default': internal error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dnsmasq
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Hozza
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 977555
TreeView+ depends on / blocked
 
Reported: 2013-04-10 19:37 UTC by John Dulaney
Modified: 2014-06-18 09:06 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 977555 (view as bug list)
Environment:
Last Closed: 2013-05-04 01:46:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description John Dulaney 2013-04-10 19:37:23 UTC
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.

Comment 1 Jiri Denemark 2013-04-12 09:30:54 UTC
As far as I know, this should be fixed in dnsmasq-2.66rc5

Comment 2 Fedora Update System 2013-04-12 10:08:20 UTC
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

Comment 3 Fedora Update System 2013-04-18 17:24:33 UTC
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).

Comment 4 Fedora Update System 2013-04-22 17:19:49 UTC
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).

Comment 5 Fedora Update System 2013-05-04 01:46:06 UTC
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.

Comment 6 Suren Karapetyan 2013-06-24 07:13:57 UTC
Can we have this fixed on Fedora 18?

Comment 7 Tomáš Hozza 2013-06-24 07:19:04 UTC
(In reply to Suren Karapetyan from comment #6)
> Can we have this fixed on Fedora 18?

Sure, can you please create F18 Bug? Thanks!


Note You need to log in before you can comment on or make changes to this bug.