I had upgraded to libvirt-0.8.7. Then I noticed that my "default" virtual network did not auto-start, and could not be started manually. I recompiled libvirt with debug and started debugging and saw: -- 11:37:23.557: 86397: debug : virCommandRunAsync:1148 : About to run /sbin/ip addr add 192.168.122.1/24 broadcast 192.168.122.255 dev virbr0 11:37:23.557: 86397: debug : virExecWithHook:716 : /sbin/ip addr add 192.168.122.1/24 broadcast 192.168.122.255 dev virbr0 11:37:23.557: 86397: debug : virCommandRunAsync:1164 : Command result 0, with PID 86543 11:37:23.559: 86397: debug : virCommandWait:1226 : internal error Child process exited with status 1. 11:37:23.559: 86397: debug : virCommandRun:1049 : Result stdout: '' stderr: 'libvir: error : cannot execute binary /sbin/ip: No such file or directory ' 11:37:23.559: 86397: debug : networkAddAddrToBridge:1523 : internal error cannot set IP address on bridge 'virbr0' -- When downgrading to the previous version (0.8.6-r1). I did not experience this problem and the network started as usual. When I installed iproute2, libvirt-0.8.7 started the virtual network. So it appears to be a new dependency.
New optional one as it should work fine without iproute2 if you use bridges and not routed networks.
Added a message to the ebuild.
Message is added and virt-network USE flag now pulls these bits in.