You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per the libvirt XML format documentation, when using an interface type of 'bridge' with OVS, 'hostdev', 'direct', and 'passthrough', trunked traffic can be specified on a per-interface basis to amp specific VLAN id tags' traffic. It would be nice, when detected to be using one of these interface types, to be able to select these tags through the cockpit-machines GUI instead of being required to fall back to virsh to manage that aspect of VMs.
The text was updated successfully, but these errors were encountered:
Can confirm the feature of being able to configure tagging through the cockpit-machines GUI interface would be an excellent add. I too am having to configure networking using virsh commands after setting up my VMs through the cockpit GUI.
Per the libvirt XML format documentation, when using an interface type of 'bridge' with OVS, 'hostdev', 'direct', and 'passthrough', trunked traffic can be specified on a per-interface basis to amp specific VLAN id tags' traffic. It would be nice, when detected to be using one of these interface types, to be able to select these tags through the cockpit-machines GUI instead of being required to fall back to virsh to manage that aspect of VMs.
The text was updated successfully, but these errors were encountered: