weizhouapache commented on issue #11491: URL: https://github.com/apache/cloudstack/issues/11491#issuecomment-4124577778
> I tested this and basically just changing the tags allowed on the vnet interface makes it work if connected to an L2 network that runs untagged (and as such directly connected to the physical network bridge). > > I don't know if such a quick fix is desirable or if a solution similar to openstack is more wanted (bundle networks under a parent network and custom tag each of these). Something similar to openstack can have benefits as it better supports VXLAN as well. > > As for the benefits, having a trunk reduces the virtual interrupts which increases efficiency. On VNF VMs with dozens of NICs passing moderate traffic, it can save some CPU cycles, especially on edge zones. @draggeta Thanks for the testing. Good to hear The VM configuration looks straightforward, as you mentioned. The potential challenges may include: - How VLANs are managed (the OpenStack approach works, but may not be ideal in this context) - Handling VLAN tags in the KVM plugin, which could impact VM operations such as start and migration - Ensuring the current network configuration continues to function as expected (NICs attached to Linux bridges with VLAN tags, e.g., breth1-XXX) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
