On Thu, Nov 15, 2018 at 10:17 AM <[email protected]> wrote:

> Hello,
>
> After having integrated OVS with Ovirt and enabled it as default network
> provider I am facing the following issues.
>

We are using OVN as network provider.


>
> I can see with "ovs-vsctl show" that the virtual switch / bridge called
> "br-int" is created. I can see interfaces being added / removed to it as I
> start / stop VMs.
>
> [root@******* ~]# ovs-vsctl show
> 78e883f9-f074-4292-afce-bb829ded856b
>     Bridge br-int
>         fail_mode: secure
>         Port "vnet6"
>             Interface "vnet6"
>         Port br-int
>             Interface br-int
>                 type: internal
>         Port "vnet4"
>             Interface "vnet4"
>     ovs_version: "2.9.0"
>
> Now I for example want to create a new interface as shown:
>
> ip tuntap add mode tap sniff0
> ovs-vsctl add-port br-int sniff0 -- --id=@p get port sniff0 -- --id=@m
> create mirror name=m0 select-all=true output-port=@p -- set bridge br-int
> mirrors=@m
> fae36943-2ca7-4914-9679-0b881cd062d8
>
> Its created, but how do I assign this sniffing interface to a ovirt VM?


If I understand your intentions correctly from now on you just need to add
OVN network connected to physical 'sniff0'. This can be done via UI in
Networks -> New network -> Check "Create on physical network" -> Select
correct provider -> Change to "Custom" and type the 'sniff0' in the
textbox. From now on you can use vNIC profile of this network and assign it
to desired VM.



> also, how can I create sniffing ports listening only on a subset of
> interfaces if they get dynamically created / removed? vnet6 points to host
> A now, but after shutting it down starting a few other VMs it will point to
> host B...


Adding @Dominik <[email protected]>


> How do I control to what vm the vnetX nic gets assigned?
> _______________________________________________
> Users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/[email protected]/message/FLR67ZYMFONHH3D3AWDIBT6RUYBPTBF4/
>

Hopefully this helps.

Regards,
Ales Musil
-- 

ALES MUSIL
Associate Software Engineer - rhv network

Red Hat EMEA <https://www.redhat.com/>


[email protected]   IM: amusil
<https://red.ht/sig>
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/MQRL62MDKSUENAFAYEE2ZSJLJ6BRIWS5/

Reply via email to