libvirt-4.1.0 doesn't work with bridged networking, returns "Network device allocation not available" on 'virsh start' But libvirt with this use flag pulls other packages as dnsmasq, ebtables, which are not needed for simple bridge network. If someone doesn't need NAT/firewall/etc controlled by libvirt, these packages are not required. Perhaps they should be in a separate use flag now?
4.1.0 also breaks openvswitch (bridged) setups 2018-03-19 21:32:03.593+0000: 6183: error : virNetDevOpenvswitchRemovePort:239 : internal error: Unable to delete port (null) from OVS 2018-03-19 21:32:03.593+0000: 6183: error : virDomainNetReleaseActualDevice:29027 : this function is not supported by the connection driver: Network device release not available 2018-03-19 21:32:03.593+0000: 6183: error : qemuAutostartDomain:276 : internal error: Failed to autostart VM 'xxxxxxxxxx': this function is not supported by the connection driver: Network device allocation not available 2018-03-19 21:32:03.602+0000: 6183: error : virDomainNetAllocateActualDevice:29000 : this function is not supported by the connection driver: Network device allocation not available 2018-03-19 21:32:03.605+0000: 6183: error : virCommandWait:2601 : internal error: Child process (/usr/bin/ovs-vsctl --timeout=5 -- --if-exists del-port) unexpected exit status 1: ovs-vsctl: 'del-port' command requires at least 1 arguments
Upstream has changed the networking setup significantly in 4.1.0 - sorry I missed that. I have pushed libvirt-4.1.0-r1 to the main repository, that unconditionally enables networking support. USE=virt-network is retained for now (simply pulling in dependencies, and might be removed at some point in time). (mastermirror is currently down - use the git mirrors to retrieve it.)
Thanks, 4.1.0-r1 resolved my openvswitch bridging issue. One question though: I have no need for either ebtables or dnsmasq and even though current USE flags look like this [ebuild R ~] app-emulation/libvirt-4.1.0-r1:0/4.1.0::gentoo USE="caps libvirtd macvtap nls qemu udev vepa -apparmor -audit -dbus -firewalld -fuse -glusterfs -iscsi -libssh -lvm -lxc -nfs -numa (-openvz) -parted -pcap -phyp -policykit -rbd -sasl (-selinux) -uml -virt-network -virtualbox -wireshark-plugins -xen -zeroconf -zfs" 0 KiB I get quite a few errors when starting libvirtd: 2018-03-20 21:07:19.337+0000: 3433: info : libvirt version: 4.1.0 2018-03-20 21:07:19.337+0000: 3433: error : dnsmasqCapsRefreshInternal:741 : Cannot check dnsmasq binary dnsmasq: No such file or directory 2018-03-20 21:07:19.338+0000: 3433: error : udevGetDMIData:1698 : internal error: Failed to get udev device for syspath '/sys/devices/virtual/dmi/id' or '/sys/class/dmi/id' 2018-03-20 21:07:19.338+0000: 3433: error : virFirewallValidateBackend:193 : direct firewall backend requested, but /sbin/ebtables is not available: No such file or directory 2018-03-20 21:07:19.338+0000: 3433: error : virFirewallApply:918 : internal error: Failed to initialize a valid firewall backend 2018-03-20 21:07:19.347+0000: 3433: error : virExec:523 : Cannot find 'pm-is-supported' in path: No such file or directory 2018-03-20 21:07:19.347+0000: 3433: warning : virQEMUCapsInit:1222 : Failed to get host power management capabilities Any chance USE flags could be adjusted to support a pure bridging setup (where the bridge is not controlled by libvirt) without pulling in unneeded dependencies?
I think the default config file for network should be removed (if USE=-virt-network). Anyway, this network will not work without required packages but libvirt will show errors in the log. For example, add to ebuild (install) something like this rm -rf "${D}"/etc/libvirt/qemu/networks/ rmdir "${D}"/var/lib/libvirt/dnsmasq/ rmdir "${D}"/var/lib/libvirt/network/ or change makefiles
Not sure if this is enough to get rid of those errors. At the moment I have just disabled default network autostart. I removed all the folders you listed, but I still get the same dnsmasq and ebtables errors.
I can confirm -r1 works again.
>but I still get the same dnsmasq and ebtables errors. I was getting ebtables error in the log with libvirt 4.0. And if you disable use flag, you don't want to have an interface (virbr0) controlled by libvirt.
*** Bug 650660 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=68fdb138b9730d532c38cdf6fcef2a36f37a92cb commit 68fdb138b9730d532c38cdf6fcef2a36f37a92cb Author: Matthias Maier <tamiko@gentoo.org> AuthorDate: 2018-03-23 14:00:39 +0000 Commit: Matthias Maier <tamiko@gentoo.org> CommitDate: 2018-03-23 14:05:58 +0000 app-emulation/libvirt: 4.1.0-r2: Apply upstream patch for bridge support Apply an upstream patch to reenable bridge support even if USE=-virt-network and automatic network support is compiled out of libvirt Thanks to Agostino Sarubbo for upstream report and mentioning the upstream patch. Patch: https://www.redhat.com/archives/libvir-list/2018-March/msg01461.html Bug: https://bugs.gentoo.org/650660 Bug: https://bugs.gentoo.org/650872 Package-Manager: Portage-2.3.24, Repoman-2.3.6 .../files/libvirt-4.1.0-unbreak_my_bridge.patch | 78 ++++++++++++++++++++++ ...irt-4.1.0-r1.ebuild => libvirt-4.1.0-r2.ebuild} | 10 +-- 2 files changed, 80 insertions(+), 8 deletions(-)}
4.1.0-r3 fixed the issue for me. I suggest to stabilize.
