[ovirt-users] Trunk port for a guest nic?

Peter Michael Calum pemca at tdc.dk
Sun Jul 31 19:19:00 UTC 2016


Hi,

In my setup all VM’s runs on separate Vlans.

On hypervisors I have :

nic0 / nic1 : bond0 – ovirtmgmt + storage (nic0 / nic1 is access ports in vlanxxx) 10G network
nic2 / nic3 : bond1 – Trunk ports with vlan1,2,3,4..n  - 1G network

In logical networks in manager I define all vlan1,2,3,4..n with vlan tag

In VM I connect nics to Vlan(s) from the logical networks.

Br,
Peter


Fra: users-bounces at ovirt.org [mailto:users-bounces at ovirt.org] På vegne af Edward Haas
Sendt: 31. juli 2016 20:42
Til: Dan Lavu <dan at redhat.com>
Cc: users <users at ovirt.org>
Emne: Re: [ovirt-users] Trunk port for a guest nic?



On Thu, Jul 28, 2016 at 3:23 PM, Dan Lavu <dan at redhat.com<mailto:dan at redhat.com>> wrote:
Sorry Edy, I totally missed this email.
So, if my hypervisor I have 4 NICs,
0 ovirtmgmt (untagged vlan71)
1/2 bonded, trunk vlan 70,72-80
4 unplugged
So i just create a trunk network, no tags and connect it to the bonded interface? Then attach it to my guest?

Yes.
When you do not define a vlan on the ovirt network, it means that everything passes to it, tagged and non tagged.
When you connect the guest to that network, it will just pass all packets as is (you will need to define the vlans in your guest to strip the tagging).
I would start with one VLAN on the host, just to see that it works and then proceed with the others. You may need to define macspoofing to allow multiple
mac addresses to exit the same VM.

Cheers,
Dan

On Fri, Jul 15, 2016 at 3:30 PM, Edward Haas <ehaas at redhat.com<mailto:ehaas at redhat.com>> wrote:


On Wed, Jul 13, 2016 at 11:40 PM, Dan Lavu <dan at redhat.com<mailto:dan at redhat.com>> wrote:
Hello,

I remember reading some posts about this in the past, but I don't know if anything came of it. Is this now possible? If so, does anybody have any documentation on how to do this in 4.0?
Thanks,
Dan


Hello Dan,
If you mean allowing a VM to communicate on multiple vlan/s, then attaching a VM to a non-vlan network should do the job.
You just need to define a trunk in the VM.

Thanks,
Edy.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160731/e76358ea/attachment-0001.html>


More information about the Users mailing list