Hi,
In RHEL5/6 we have been able to create bridges on our hyper-visor of a
number of vlans (eg. em1 -> em1.483 -> br483) We would be able to see
this br483 in the virt-manager drop down network choice at the end of
creating a new host.
On RHEL7 we are not using NetworkManager per the documentation[0] for
bridges (and because it is not worth it). So a RHEL7 virt-manager
(0.10.0) when connected to a libvirtd for RHEL6 (0.10.2) shows the
bridge but when connected to a libvirtd for RHEL7 (1.1.1) it does not.
So it isn't a virt-manager problem as it seems to be a difference in the
backend libvirtd. You are able to manually specify the bridge device
and it does work though.
The `iface-dumpxml br483` command in virsh on RHEL6 and RHEL7 both are
identical. I guess the question how does a libvirt client like
virt-manager determine a iface is a usable bridge?
[0] -
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Virtualization_Deployment_and_Administration_Guide/sect-Network_configuration-Bridged_networking_with_libvirt.html
Thanks,
derek
--
Derek T. Yarnell
University of Maryland
Institute for Advanced Computer Studies
