Expand on your belief that using the motherboard NIC for a VM “would cause trouble”??
It is not so much the onboard issue, it is that I use the onboard NIC for truenas and completely pass the quad nic card through for the VM so they are completely separate.
If whilst doing an update or system change in truenas causes the onboard NIC to reset this will cause connectivity issues for anything running on it.
I think it should work fine now that libvirt is back.
I had to migrate ny pfSense to Incus when I upgraded to 25.04.0, and later the old VM came back…
Excellent work on the release. I’ve just updated my environment from 24.10 and it was totally painless. All my existing VM and App workloads are up and running and the new environment so far is as smooth as silk.
1 Like
Update on my question : I just updated (remotely through the connection provided by the pfSense VM) straight to 25.10.0 with no issue.
1 Like
P.S. All went well, the VM works (even the pfSense), but one of my TrueNAS experienced an unexplained self reboot about 26 hours following the update.