I’ve been using TrueNAS for… well, before it was called TrueNAS, but held on my home server on TrueNAS CORE 13.3 for quite some time. I have used up to 24.10 (Electric Eel) with bridge configurations for clients multiple times (often clean installs), with no issue, however in my case, I upgraded from 13.3 to 25.10 last night in a double migration, as I was under the opinion that the system now could bring virtual machines forward, a feature 23/24 failed to do cleanly, and of course, the VMs did present correctly in the WebGUI.
However, I cannot seem to find a clear answer why I am seeing the behavior. The reserved IP for my system came forward correctly and was reassigned to the bridge, the ens6 NIC is now inheriting the the IP correctly, and both the TrueNAS core and APPs are being forwarded to the internet via my mesh router; the same thing cannot be said about VMs, whether they are pre-existing from the old OS or newly created. The adapter following “ip a” command shows that it is DISCONNECTED from any network despite the boot process not halting looking for connection.
All of my VMs are based on Ubuntu Server 24.x and provided correct operation in the dumb bridge 13.3 used. Any ideas?
For reference, my system is based on a LGA 2011-3 workstation main board (Machinist brand), Intel XEON E5-2683 v4, 128GB DDR4 ECC-R, LSI 9200-8i, an Intel Intel 82599EN NIC, and 4 Western Digital Enterprise 8TB SAS drives.
I do have items captured from the display but am not having any luck adding them here.