Hi Levin, I realized later it won't work that easily with Cloudstack yet.
-Jithin From: Levin Ng <levindec...@gmail.com> Date: Friday, 22 September 2023 at 4:35 PM To: users@cloudstack.apache.org <users@cloudstack.apache.org>, users@cloudstack.apache.org <users@cloudstack.apache.org> Subject: Re: Network Offering for L2 Interface Hi Jithin, Can you elaborate more of your approach, having all vlan under base kvm, but ACS still just assign one VLAN on guest VM, whatever VLAN it tag inside VM, it is q-in-q configuration. Regards, Levin On 22 Sep 2023 at 07:38 +0100, Jithin Raju <jithin.r...@shapeblue.com>, wrote: > Hi Levin, > > You could try this on the base KVM : > > bridge vlan add vid 2-4094 dev eth1 > > -Jithin > > From: Levin Ng <levindec...@gmail.com> > Date: Friday, 22 September 2023 at 4:27 AM > To: users@cloudstack.apache.org <users@cloudstack.apache.org> > Subject: Network Offering for L2 Interface > Hi, > > I’m looking for a better solution for assign a root bridge interface without > assigning VLAN for VM, allow me to test nested virtulization environment such > as ACS in ACS, where requires VLAN tagging in side the nested KVM. I’d been > worked out two way to achieve it, > > • SR-IOV with pass-through PCI > • q-in-q network setup > > but it require quite much admin work before hand, appreciated if everyone > have ideas to done it in more elegant way. > > > Regards, > Levin > > >
