Created attachment 1585671 [details] terminal log of the usage of isolated ports on plain libvirt The communication between VMs connected to the same logical network (east-west-traffic) should be blocked on port-level. The ports of the VMs can only communicate with an "uplink" port, which will be fixed to the physical network. This means that the default gateway and the DHCP server has to be connected via the physical network to the hosts. The limitations of bug 1651499 and bug 1651467 will be resolved, and no additional configuration like in bug 1009608, except a checkbox to enable this feature, should be requred. User interaction and design: On creating the network, the user can enable this feature for the new network. Documentation Considerations: The new property of logical networks has to be added to the doc. Requirements: The kernel feature port isolation https://github.com/torvalds/linux/commit/7d850abd5f4edb1b1ca4b4141a4453305736f564 is available on the hosts. Out of Scope: - Updating of the new property of the logical network - Configuring port isolation per vNIC or vNIC profile - The allowed "uplink", which will be able to communicate with all VMs, is the physical network
To stretch the isolation for VMs across multiple hosts, the ports of the physical switch connected to the related hosts NICs must have Private VLAN / port isolation enabled and hairpin disabled.
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly
I would like to see this implemented as soon as an appropriate libvirt is available to RHV.
This is a long requested feature, even if we have to wait to have an appropriate libvirt version available.
michal: verified in build 4.4.3.6-0.13
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.