I have been experiencing a minor annoyance with the Virtual Network.

It is supposed to be active on boot but it shows inactive although vibr0 exists.

bash-4.2# virsh net-list --all
Name State Autostart Persistent
----------------------------------------------------------
default inactive yes yes

ifconfig virbr0 down
brctl delbr virbr0

bash-4.2# virsh net-start default
error: Failed to start network default
error: internal error: Network is already in use by interface virbr0

Then I have to reboot and that only works half the time requiring the

ifconfig virbr0 down
brctl delbr virbr0
reboot

to fix it which usually works.

Any thoughts on how to correct this

I don't know about anyone else, but I restart my virtual network with libvirt. I avoid stopping any virtual nics by network manager too.

That seems to work or at least it worked when I tried it just now

I just wish it would not get messed up at all

Hopefully this will all be better with 14.2

That is how it gets started when the system comes up anyway.

I'm not entirely sure you did this or not. It seems like you skipped doing so.

See the README for libvirt on http://slackbuilds.org/cgit master branch, here: https://slackbuilds.org/cgit/slackbu...a4cfc321cfbea0

The read me on every slackbuild will explain how to use it. In your case you need to add to /etc/rc.d/rc.local and /etc/rc.d/rc.local_shutdown an if statement that starts and stops libvirt on boot/shutdown.

Of course, if you choose not to start it or stop it at boot/shutdown, then you can just run /etc/rc.d/rc.libvirt {start,stop} as root when you decide you need to use your virtual machines.

I always read the README files.

Opps I did do the stuff from the README but I had put in stuff to start libvirtd and assign a PID that was not necessary

I took that out and all is well