On Fri, 2015-03-13 at 09:29 +0100, Bastian Blank wrote: 
> How is vibr1 defined in /etc/network/interfaces?
Not at all, actually I still have many interfaces defined there (even
though non of them is used since NM is broken), but only the normal
eth/wlan stuff.

Normally, libvirtd should dynamically set these ifaces up.


> > 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.
> So this is actually a missing error cleanup somewhere.
Well not sure,.. right after booting, none of these unconfigured vibrX
devices exist, only when I start them via libvirtd,... but then they
already fail to come up (unless I've manually loaded tun before) 


> No, it is not a problem with the kernel.  The ability to autoload
> modules was restricted as it was the source of nasty surprises.
So auto-loading tun was actually removed somewhere between 3.16 and .19?

So then we should probably reassign this to libvirtd (or dnsmasq)?


Cheers,
Chris.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to