Package: src:linux Version: 3.19.1-1~exp1 Severity: normal
Hi. Not sure whether this bug is actually within the kernel or whether the real problem is rather in libvirtd or network-manager (which is always a valid suspect of screwing up network things). Since I've upgraded from 3.16 from sid to 3.19 from experimental libvirtd gives me an error when starting virtual networks (vibr1 and so on, which are set up as bridge devices via dnsmasq. The message is that the device already exists. What happens is apparently the following: The tun modules is not (no longer?) auto-loaded by the kernel and a vibrX device is set up but not fully working. libvirt/NM are then not able to detect this already existing device anymore and cannot even stop it. When one manually removes it, e.g. via ip link delete virbr1), then modprobe tun and then start it again from libvirt things work fine again. So either there's some regression in the kernel that the module is no longer auto-loaded... or one of the using packages (libvirtd, dnsmasq, etc.) should do so but doesn't. Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org