Hello oVirt community, Seems lik a bug. I don't have more than one environment to test on so I can't be 100% sure and didn't want to file a report (but didn't know where else to report this). I have a fresh install self hosted ovirt cluster 4.3.1.1-1.el7. When I build any logical network adapter with a "-" in the name ex "guest-network-01" the network interface names appear on the hosts (using ip addr command) as garbled names like on8cd19bc011414. They still appear to work, but when you try to make a VNic profile based on the broken name the VMs fail to boot, the VM has to be killed via command line on each host afterwards (they try to boot and hang on all hosts in the cluster corrupting the disk of the VM) because it can't find the parent logical network interface by name. Example errors: VM Security-Onion is down with error. Exit message: (1, 'Cannot find device "guest-dmz-ne"\n', ['/sbin/tc', 'qdisc', 'add', 'dev', 'guest-dmz-network', 'ingress']). VDSM ovirt-2 command DestroyVDS failed: General Exception: ('(1, \'Cannot find device "guest-dmz-ne"\\n\', [\'/sbin/tc\', \'filter\', \'show\', \'dev\', \'guest-dmz-network\', \'parent\', \'ffff:\'])',) That took me a very long time to figure out and broke many vms in the process =(