https://bugzilla.novell.com/show_bug.cgi?id=829033 https://bugzilla.novell.com/show_bug.cgi?id=829033#c5 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|richard@nod.at | Resolution| |INVALID --- Comment #5 from Marius Tomaschewski <mt@suse.com> 2013-07-17 21:24:11 UTC --- (In reply to comment #3)
libvirt creates veth devies and sets them up/down.
Right.
If udevd also starts configuring them we end up in a situation where libvirt thinks that an interface is up, but is in reality down and vice versa.
No, udev does not create them -- it just handles the event when interface appears in the system (created by libvirt in this case) or is removed from the system/kernel (triggered by libvirt, cleanup call on sysconfig side). There is no ifcfg-file for the veth interfaces, so nothing is done and nothing happens. When there is one, it is there a) by intention or b) libvirt is trying to use a system configured/reserved interface name, that is a misconfiguration. (In reply to comment #4)
BTW: There is *zero* reason why udevd should handle virtual network devices...
e.g. routed vm configuration on the host side, we've used with xen. The user may want to create a ifcfg-file with STARTMODE=hotplug and ifroute-file to apply routes. As there is no issue, resolving as INVALID. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.