http://bugzilla.opensuse.org/show_bug.cgi?id=909348 Charles Arnold changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfehlig@suse.com --- Comment #1 from Charles Arnold --- I think this is a valid error. The interface name can't exceed 15 characters. This is a system limit as defined in net/if.h. Virt-manager is just reporting what came back from libvirt when it used the iptables call to set up a firewall rule for the interface. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=909348 --- Comment #3 from Charles Arnold --- (In reply to Attila Schler from comment #2)

(In reply to Charles Arnold from comment #1)

...

I think this is a valid error. The interface name can't exceed 15 characters. This is a system limit as defined in net/if.h. Virt-manager is just reporting what came back from libvirt when it used the iptables call to set up a firewall rule for the interface.

But from where comes that long interface name? Why sees the Virtual Machine Manager that interface name?

# ifconfig net_wlp16s0_00_1f_3b_59_61_3d net_wlp16s0_00_: error fetching interface information: Device not found

# ifconfig wlp16s0 wlp16s0 Link encap:Ethernet HWaddr 00:1F:3B:59:61:3D inet addr:192.168.12.7 Bcast:192.168.12.255 Mask:255.255.255.0 inet6 addr: fe80::21f:3bff:fe59:613d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:721012 errors:0 dropped:0 overruns:0 frame:0 TX packets:493504 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:989818675 (943.9 Mb) TX bytes:51008826 (48.6 Mb)

That is odd. Something has appended the MAC addr to the interface name. Could you also attach the file ~/.cache/virt-manager/virt-manager.log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=909348 Ulf Dettmer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ulf.dettmer@stk.nrw.de --- Comment #6 from Ulf Dettmer --- I got the same problem after updating my installation from 12.3 to 13.2 (using the 'zypper dup' way). Those strange IF names are referred to as "Alternative method of enumerating interfaces" in the libvirt documentation: http://libvirt.org/guide/html/Application_Development_Guide-Network_Interfac... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=909348 Cédric Bosdonnat changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |attila.schler@atskler.net Flags| |needinfo?(attila.schler@ats | |kler.net) --- Comment #8 from Cédric Bosdonnat --- (In reply to Jim Fehlig from comment #7)

(In reply to Charles Arnold from comment #5)

...

These long names are acquired from libvirt. For example, 'virsh nodedev-list | grep net' will show the long names like 'net_wlp16s0_00_1f_3b_59_61_3d' that appear in the popdown list.

net_wlp16s0_00_1f_3b_59_61_3 is the nodedev name. Information about this nodedev can be obtained with nodedev-dumpxml, e.g.

These IDs are libvirt internal ones, not something the kernel and network tools knows about.

...

Virt-manager gathers them all up and puts them in the list allowing them to be selected.

Perhaps virt-manager should display the interface name associated with the nodedev.

Indeed that would make much more sense for the user experience, but I guess we'll need to show something else for the other device types.

...

Jim, Any thoughts on this? How are these long name interfaces supposed to be used?

IMO, virt-manager should not be using the nodedev name, but the actual interface associated with the nodedev.

Cedric has done some work in libvirt's network code lately, so I'd like to hear his opinion.

I agree, the nodev is something only libvirt knows about. For other things, the device name should be fetched from the device XML. @Attila: Could you please run virt-manager with --debug flag so that we could see what XML fragment is used to create the network device? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=909348 Cédric Bosdonnat changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(cbosdonnat@suse.c | |om), | |needinfo?(attila.schler@ats | |kler.net) | --- Comment #10 from Cédric Bosdonnat --- (In reply to Attila Schler from comment #9)

...

@Attila: Could you please run virt-manager with --debug flag so that we could see what XML fragment is used to create the network device?

Don't worry, I didn't see that you already provided a log: The problem is here:

[Wed, 10 Dec 2014 23:51:44 virt-manager 11058] DEBUG (network:256) Creating virtual network 'for_bugzilla' with xml: <network> <name>for_bugzilla</name> <uuid>ac477956-4b42-4cda-915c-fc13c22fa5d4</uuid> <forward mode="nat" dev="net_wlp16s0_00_1f_3b_59_61_3d"/> <domain name="for_bugzilla"/> <ip address="192.168.133.1" netmask="255.255.255.0"> <dhcp> <range start="192.168.133.128" end="192.168.133.254"/> </dhcp> </ip> </network>

The dev value uses the libvirt internal id, rather than the device name. This looks like virt-manager not properly using the libvirt API. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=909348 Charles Arnold changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #12 from Charles Arnold --- Fix available in the Virtualization/virt-manager repo. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=909348 --- Comment #14 from Attila Schler --- This new problem existed before the fix! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=909348 --- Comment #16 from Attila Schler --- (In reply to Charles Arnold from comment #15)

(In reply to Attila Schler from comment #14)

...

This new problem existed before the fix!

Check this page to see if it is applicable to your situation,

http://wiki.libvirt.org/page/Libvirtd_and_dnsmasq

I've noticed a few upstream bugs with dnsmasq / libvirt. What version of libvirt do you now have installed?

I think there are permission kind of problems. If I stop the apparmor sevice (# service apparmor stop) I don't get the before-mentioned “dnsmasq: cannot run lease-init script” problem. But I get the following: Error starting network 'default': internal error: Failed to apply firewall rules /usr/sbin/iptables -w --table filter --insert INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT: iptables v1.4.21: can't initialize iptables table `filter': Permission denied Perhaps iptables or your kernel needs to be upgraded. Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/network.py", line 104, in start self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2853, in create if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self) libvirtError: internal error: Failed to apply firewall rules /usr/sbin/iptables -w --table filter --insert INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT: iptables v1.4.21: can't initialize iptables table `filter': Permission denied Perhaps iptables or your kernel needs to be upgraded.

What version of libvirt do you now have installed? The libvirt (libvirt = 1.2.11-463.3) package not installed by default. The libvirt-daemon 1.2.11-463.3 and libvirt-client 1.2.11-463.3 installed.

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=909348 --- Comment #18 from Cédric Bosdonnat --- @Attila, BTW, the problem you mentioned is already reported as bug 911001, and should be fixed with up-to-date factory apparmor packages. The fix for 13.2 will be submitted soon. -- You are receiving this mail because: You are on the CC list for the bug.