Re: Error starting domain: Requested operation is not valid: network 'default' is not active

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2019-08-18 at 10:30 +0800, Ed Greshko wrote:
> On 8/18/19 1:23 AM, Patrick O'Callaghan wrote:
> > The above only happens when SElinux is Enabled. When Disabled,
> > everything works. The same happens on both my VMs (Fedora and Windows).
> > 
> > Looking at https://wiki.libvirt.org/page/Networking I tried:
> > 
> > # virsh net-list --all
> >  Name      State      Autostart   Persistent
> > ----------------------------------------------
> >  default   inactive   yes         yes
> > 
> > # virsh net-start default
> > error: Failed to start network default
> > error: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper) unexpected exit status 11: 
> > dnsmasq: lease-init script returned exit code 1
> > 
> > I run my own dnsmasq (and QEMU/KVM runs its own dnsmasq separately) but
> > this has not been an issue recently.
> > 
> > # cat /var/lib/libvirt/dnsmasq/default.conf
> > ##WARNING:  THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO
> > BE
> > ##OVERWRITTEN AND LOST.  Changes to this configuration should be made
> > using:
> > ##    virsh net-edit default
> > ## or other application using the libvirt API.
> > ##
> > ## dnsmasq conf file created by libvirt
> > strict-order
> > pid-file=/var/run/libvirt/network/default.pid
> > except-interface=lo
> > bind-dynamic
> > interface=virbr0
> > dhcp-range=192.168.122.2,192.168.122.254,255.255.255.0
> > dhcp-no-override
> > dhcp-authoritative
> > dhcp-lease-max=253
> > dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile
> > addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts
> > 
> > Ideas on what's causing this would be welcome.
> > 
> 
> You're not getting any AVC's, correct?
> 
> In that case you should do...
> 
> semodule -DB    to remove dontaudits from policy and then test again with selinux enabled
> and see if AVC's are created.
> 
> semodule -B   after testing will turn dontaudits back on.

Did that and the problem has magically disappeared. No AVCs were
reported, though I did relabel after turning SElinux back on.

Curiously, I now see:

$ virsh net-list --all
Name   State   Autostart   Persistent
----------------------------------------


(i.e. empty) but my VMs are working.

poc
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux