[SOLVED] VLAN Tagging Makes VM Unresponsive

[fluppy]

Hey all,

So I'm trying out Proxmox to see if we can migrate to it from our vSphere setup.

I've created an LACP bond and created a bridge based on this bond. I've made the bridge VM aware.

If i create a VM and tag it with let's say 20, it works as expected. If I tag it with 10, it doesn't. The NoVNC console itself becomes unresponsive and I can't interact with the VM at all. If I tag it with 20 again, then it's fine.

Specifically, I'm just trying to install Alma 9 on this VM, as the installer is an easy way to test network connectivity

What could be causing this?

As you can see below, I have 1 interface (eno1) that I'm using for management, and a bond (bond0) that has 2 10 gig interfaces in it which I want the VMs to use for their traffic.


Have I configured this wrong? I'm trying to get the Proxmox web gui to be accessible on 10.10.10.12 (vlan10), which it currently is but I need to be able to create VMs on different vlans (10, 20, 30) and have VM traffic go through the LACP bond instead of onboard 1 gig port

 

[fluppy]

In case someone sees this, my firewall wasn't providing DNS for that VLAN which was causing this issue.

 

[Spoonman2002]

Nice that you solved the problem yourself AND provided the solution!