Hey, trying to figure this out and getting deeper.
New install Pmox and able to upgrade everything before deploying VMs. Initial VMs actually connected fine but suddenly do not. Only had one other and all subsequent deployments without pci passthrough are failing on the vmbrs.
Proxmox Host is fine on vmbr0 and has static IP I can reach. However, it is not noted in the Opnsense Firewall leases in any way.
All VMs I make on vmbr1 (same NIC as Pmox host on vmbr0) and even a test vmbr2 on the MB ports all come in as down.
When starting up the VM it spins and eventually passes at job systemd-networkd-wait-online.service/start running portion and that systemctl inside shows it's failing
I have run a few commands and note that:
- the netplan .yaml uses a cloud-init name even though I did not set up cloud init for this vm
- ip a shows a down link and changing .yaml to dhcp and even a temp static does not seem to work in assigning an IP address
- ethtool shows that the ens18 that was assigned to the VM for vmbr1 has a link but reports no data and is for all intents and purposes not reading the NIC for the vmbr
- Pmox ethtool on the same NIC port shows all data reading fine but also same output for the vmbr with nothing really there but the link
Basically, why would the VMs (ubuntu 22.04), keep acting this way. I imagine I can just hard write the lease into the router, but I'm surprised the MAC isn't coming in at all there in the list of leases. Thank you!
New install Pmox and able to upgrade everything before deploying VMs. Initial VMs actually connected fine but suddenly do not. Only had one other and all subsequent deployments without pci passthrough are failing on the vmbrs.
Proxmox Host is fine on vmbr0 and has static IP I can reach. However, it is not noted in the Opnsense Firewall leases in any way.
All VMs I make on vmbr1 (same NIC as Pmox host on vmbr0) and even a test vmbr2 on the MB ports all come in as down.
When starting up the VM it spins and eventually passes at job systemd-networkd-wait-online.service/start running portion and that systemctl inside shows it's failing
I have run a few commands and note that:
- the netplan .yaml uses a cloud-init name even though I did not set up cloud init for this vm
- ip a shows a down link and changing .yaml to dhcp and even a temp static does not seem to work in assigning an IP address
- ethtool shows that the ens18 that was assigned to the VM for vmbr1 has a link but reports no data and is for all intents and purposes not reading the NIC for the vmbr
- Pmox ethtool on the same NIC port shows all data reading fine but also same output for the vmbr with nothing really there but the link
Basically, why would the VMs (ubuntu 22.04), keep acting this way. I imagine I can just hard write the lease into the router, but I'm surprised the MAC isn't coming in at all there in the list of leases. Thank you!
Last edited: