[ovirt-users] Re: OVS and Ovirt integration questions
Maybe you can create a host hook, if you find a solution I'd be really interested as
it would solve a lot of problems for us.
Regards,
Paul S.
________________________________________
From: 0pk0de(a)riseup.net <0pk0de(a)riseup.net>
Sent: 15 November 2018 09:16
To: users(a)ovirt.org
Subject: [ovirt-users] OVS and Ovirt integration questions
Hello,
After having integrated OVS with Ovirt and enabled it as default network provider I am
facing the following issues.
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? 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...
How do I control to what vm the vnetX nic gets assigned?
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
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/users@ovirt.org/message/FLR67ZYMFON...
To view the terms under which this email is distributed, please go to:-
http://disclaimer.leedsbeckett.ac.uk/disclaimer/disclaimer.html