Bug 1261400

Description of problem:

First,

If you want to use KVM/qemu to make some VM on your computer you MUST have NetworkManager out of the way.

Why ?

Because : In my case I had eth0 managed by Network Manager and VM with their own macvtap interface.

First boot of the host, everything is okay, start the VM, no problem.
Reboot a VM, no more network for it.
networkctl shows the macvtapX interface is here, but nothing on ifconfig.

The only solution is to reboot the host ! No good at all.

Second,

-In the Virtual Machine Manager, open the Edit menu, open Connection Details
-Go to the Network Interfaces tab

As said in first point what you see here DOES NOT reflect your network if you're using NetworkManager. It is completely plain wrong.

If your network setting is based on the sysintV files, this part of the GUI will EDIT THOSE FILES if you make changes here. We can conclude that those preferences are just like the Network Preferences settings.

THIS IS UNCLEAR AND CONFUSING, is there a reason to toy with the host network interfaces here ? Aren't the system preferences in Gnome or whatever GUI here for that ?

Plus, it lies : my eth0 interface is set to use DHCP but in this GUI I can see it in Static Mode...

How reproducible:

always

Steps to Reproduce:
1.have NetworkManager managing your Network
2.set VM in macvtap network and play with it
3.disable NetworkManager and set your network with sysinitV files
4.play with your VM again

Actual results:

with NetworkManager the network its setting are a mess

Expected results:

NetworkManager or not the network behaviour is consistent and the displayed informations are too

My recommendation:

-remove the Network Interfaces tab in Virtual Machine Manager GUI, or
-put a warning message in the Network Interfaces tab in Virtual Machine Manager GUI to tell to swith to sysinitV and do not use NetworkManager