<div dir="auto"><div><div class="gmail_extra"><div class="gmail_quote">On Dec 3, 2016 11:18 PM, "Chris Cowley" <<a href="mailto:chris@chriscowley.me.uk">chris@chriscowley.me.uk</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Evening all<br>
<br>
I am struggling to get VMs on a tagged VLAN with oVirt to communicate<br>
with a physical machine that is 'untagged' on that VLAN.<br>
<br>
This VLAN is tagged on the port for my ovirt host, and any VMs attached<br>
to that network work perfectly within oVirt (single host). On that host<br>
I have added an IP on that VLAN too.<br>
<br>
On a couple of host other physical machines, it is connected on to that<br>
VLAN untagged and another is on it tagged. They communicate fine, and<br>
also with the oVirt host on that VLAN. No traffic goes to or from the<br>
VMs however.<br>
<br>
<br>
<a href="https://www.draw.io/i/EiXgaUi" rel="noreferrer" target="_blank">https://www.draw.io/i/EiXgaUi</a><br>
<br>
As my switch is doing tagging/untagging should I be importing the<br>
network? If that is the case, err, how?<br></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">When you define a VM network in ovirt, it either globally has a vlan tag, or has not. This cannot be con trolled per host.</div><div dir="auto"><br></div><div dir="auto">However, you could set a before-network-setup vdsm hook. When Engine asks the host to create a tagged network, the hook would modify the request to an untagged network.</div><div dir="auto"><br></div><div dir="auto">Then, traffic from vms running on that host would be tagged only by the switch (I assume that now it ends up q-in-q).</div><div dir="auto"><br></div><div dir="auto">If you end up writing this hook, please share it with us. You can look into vdsm-hook-fcoe for a (completely different) network hook.</div><div dir="auto"><br></div><div dir="auto"><br></div></div>