[ovirt-users] Re: Networking - How to pass all vlan (trunk) to a guest VM?
Unfortunately you are trying to implement an unsupported setup as discussed already here: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/O23ICVSO5SHTK5PX6ZFB7XB3ROWJOHAL/ * BTW, I have missed your responses. Please try to keep the ones who participated in the thread on the email to/cc sections, it will improve the chances the thread is tracked by them. Thanks, Edy. On Sun, Nov 4, 2018 at 9:47 PM Jonathan Greg wrote: > Hi, > > To give a try, I added a new vlan in my infrastructure but I didn't > defined it in oVirt. I configured a sub-interface ens3.444 on my guest VM > and the VM is able to talk to the external world. > > However, as soon as I define I create a logical network (vlan444) in oVirt > and attach it to the host. the VM communication stop. It looks like that we > cannot trunk a vlan to a guest if this vlan is defined in oVirt. > > Is it the expected behavior? > Is there a workaround? > Will this feature be available in the next release(s)? > > > Thanks > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/VCR5S4VCRCWKOSWC74SIK67I3JUUJQJB/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/VLMFDCEPSKRI56LOS4FMTDNNEMZ67E7Q/
[ovirt-users] Re: Networking - How to pass all vlan (trunk) to a guest VM?
Hi, To give a try, I added a new vlan in my infrastructure but I didn't defined it in oVirt. I configured a sub-interface ens3.444 on my guest VM and the VM is able to talk to the external world. However, as soon as I define I create a logical network (vlan444) in oVirt and attach it to the host. the VM communication stop. It looks like that we cannot trunk a vlan to a guest if this vlan is defined in oVirt. Is it the expected behavior? Is there a workaround? Will this feature be available in the next release(s)? Thanks ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/VCR5S4VCRCWKOSWC74SIK67I3JUUJQJB/
[ovirt-users] Re: Networking - How to pass all vlan (trunk) to a guest VM?
Hi Edy, Here is the output requested. Note that I attached the logical network named "trunk" below to a VM. From that VM, I do have enable the 8021q module and configure sub-interface. But I don't see any traffic coming in. [root@c200m2-1 ~]# ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp11s0: mtu 9000 qdisc mq master bond0 state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 3: enp12s0: mtu 9000 qdisc mq master bond0 state DOWN group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 4: ens1f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 30:f7:0d:08:7e:44 brd ff:ff:ff:ff:ff:ff 5: ens1f1: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 30:f7:0d:08:7e:45 brd ff:ff:ff:ff:ff:ff 263: vnet0: mtu 9000 qdisc mq master vlan2192 state UNKNOWN group default qlen 1000 link/ether fe:1a:4a:16:01:0f brd ff:ff:ff:ff:ff:ff inet6 fe80::fc1a:4aff:fe16:10f/64 scope link valid_lft forever preferred_lft forever 264: vnet1: mtu 9000 qdisc mq master vlan2192 state UNKNOWN group default qlen 1000 link/ether fe:1a:4a:16:01:10 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc1a:4aff:fe16:110/64 scope link valid_lft forever preferred_lft forever 265: vnet2: mtu 9000 qdisc mq master vlan2192 state UNKNOWN group default qlen 1000 link/ether fe:1a:4a:16:01:11 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc1a:4aff:fe16:111/64 scope link valid_lft forever preferred_lft forever 266: vnet3: mtu 9000 qdisc mq master vlan2192 state UNKNOWN group default qlen 1000 link/ether fe:1a:4a:16:01:12 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc1a:4aff:fe16:112/64 scope link valid_lft forever preferred_lft forever 268: vnet4: mtu 9000 qdisc mq master trunk state UNKNOWN group default qlen 1000 link/ether fe:1a:4a:16:01:08 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc1a:4aff:fe16:108/64 scope link valid_lft forever preferred_lft forever 21: bond0: mtu 9000 qdisc noqueue master trunk state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 55: ovirtmgmt: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff inet 10.194.16.146/24 brd 10.194.16.255 scope global ovirtmgmt valid_lft forever preferred_lft forever 64: ;vdsmdummy;: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 6a:18:4b:3a:f6:ac brd ff:ff:ff:ff:ff:ff 65: bond0.12@bond0: mtu 9000 qdisc noqueue master vlan12 state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 66: vlan12: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 67: bond0.13@bond0: mtu 9000 qdisc noqueue master vlan13 state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 68: vlan13: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 69: bond0.10@bond0: mtu 9000 qdisc noqueue master vlan10 state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 70: vlan10: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 71: bond0.11@bond0: mtu 9000 qdisc noqueue master vlan11 state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 72: vlan11: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 73: bond0.14@bond0: mtu 9000 qdisc noqueue master vlan14 state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 74: vlan14: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 75: bond0.15@bond0: mtu 9000 qdisc noqueue master vlan15 state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 76: vlan15: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 77: bond0.3@bond0: mtu 9000 qdisc noqueue master vlan3 state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 78: vlan3: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 79: bond0.201@bond0: mtu 9000 qdisc noqueue master vlan201 state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 80: vlan201: mtu 9000 qdisc noqueue state UP group default qlen 1000 link/ether d4:8c:b5:bd:30:ef brd ff:ff:ff:ff:ff:ff 81: bond0.202@bond0: mtu 9000 qdisc noqueue master vlan202 state UP group defa
[ovirt-users] Re: Networking - How to pass all vlan (trunk) to a guest VM?
Yes, not setting any VLAN on a network implies all packets will pass on to that network from the nic it is configured on. Please share your host `ip addr` , `brctl show` and the name of the network you configured. Do you see relevant packets on the host nic? Thanks, Edy. On Thu, Nov 1, 2018 at 5:29 PM Petr Horacek wrote: > Hello, > > you are right, with "Enable VLAN tagging" VMs should be connected to the > network via a trunk. > > It should work, right Edward? > > Regards, > Petr > > 2018-10-31 20:14 GMT+01:00 Jonathan Greg : > >> Hi, >> >> I didn't find the documentation about it... How I can pass all the vlan >> (trunk) to a guest VM (without SR-IOV)? >> >> My switch is configured to trunk all vlans. >> I do have configured a logical network with the "Enable VLAN tagging" box >> uncheck and assign it to a VM. My understanding with this setting is that >> tagged and untagged packet should be forwarded to the VM guest. >> Unfortunately it doesn't work at all, if I run a tcpdump on the VM nic >> attached to this logical network, I don't see anything... I would really >> like to run a virtual router or firewall on my setup without having to >> shutdown my VM and having attach a new vnic each time I want to add a new >> vlan. >> >> Any idea? >> >> Jonathan >> ___ >> Users mailing list -- users@ovirt.org >> To unsubscribe send an email to users-le...@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/JXJG2H553WIGAZ5RI5KX3NXHDDKTCPCH/ >> > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/TKGHLCU243I4YECAESWF53GRJ6YTR3CF/
[ovirt-users] Re: Networking - How to pass all vlan (trunk) to a guest VM?
Hello, you are right, with "Enable VLAN tagging" VMs should be connected to the network via a trunk. It should work, right Edward? Regards, Petr 2018-10-31 20:14 GMT+01:00 Jonathan Greg : > Hi, > > I didn't find the documentation about it... How I can pass all the vlan > (trunk) to a guest VM (without SR-IOV)? > > My switch is configured to trunk all vlans. > I do have configured a logical network with the "Enable VLAN tagging" box > uncheck and assign it to a VM. My understanding with this setting is that > tagged and untagged packet should be forwarded to the VM guest. > Unfortunately it doesn't work at all, if I run a tcpdump on the VM nic > attached to this logical network, I don't see anything... I would really > like to run a virtual router or firewall on my setup without having to > shutdown my VM and having attach a new vnic each time I want to add a new > vlan. > > Any idea? > > Jonathan > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/JXJG2H553WIGAZ5RI5KX3NXHDDKTCPCH/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/CTMLJ3VBKQLXISA3C6PWXQWMHJSJYB2L/
