At the moment connection between VMs and the KVM host is not possible if macvtap is being used. To circumvent this a second management network is needed.
Explanation why this is needed:
macvtap works in VEPA/bridge mode - traffic from a VM is forwarded to the upstream switch, and the Linux kernel blocks the host from talking directly back to the VMs. The communication using the primary NIC is not possible.
Solution:
Create a libvirt isoloated network (no | ) element in the XML backed by a linux bridge. Attach this as a second NIC to every VM.
At the moment connection between VMs and the KVM host is not possible if macvtap is being used. To circumvent this a second management network is needed.
Explanation why this is needed:
macvtap works in VEPA/bridge mode - traffic from a VM is forwarded to the upstream switch, and the Linux kernel blocks the host from talking directly back to the VMs. The communication using the primary NIC is not possible.
Solution:
Create a libvirt isoloated network (no | ) element in the XML backed by a linux bridge. Attach this as a second NIC to every VM.