How did you get nested virtualization going on TrueNAS? I tried that a while ago but failed for some reason I cannot remeber now.
I didn’t have to do anything special. It just worked. I’m not sure if it matters but I use host pass-through for the CPU setting.
Interesting, maybe I was on Host Model back then… Thanks nonetheless.
Doesn’t solve the problem for people who updated from 25.04.1 and have the same issue.
is missing a record for 25.04.2. As well as the software status page, but can’t be sure for the latter.
Good catch - it’s being updated at this moment!
Updated from 25.04.1 to 25.04.2 without issues, but with some observations.
All my VM’s from 24.10 were back after the update, but as I had deleted all related zvols, they were useless and I deleted all.
All VM’s and Containers still working in Incus.
Rebuilt all my 4 VM’s in new old Vitualization: Windows11, Home Assistant, Xubuntu and Proxmox easily - and deleted these in the Container tab. Ready for Goldeye.
I do hope the containers will go ok to Goldeye, I leant to appreciate them very much and I have more than 10 of them on 2 Truenas servers.
As far as i’ve seen there’s currently no information on lxc migration. But since it’s confirmed that incus will be removed completely and lxc will also bi libvirt based, i assume you either have to also manually migrate them at some point or iX will come up with a migration plan (i doubt it)
@Whiskeydrinker, congratulations on a successful upgrade from 24.10.2.3 to 25.0.4.2. In addition to your VMs, do you also have any IX or Community apps installed, and were they okay after the upgrade as well?
One note: I upgraded from 24.10.2.3 I missed the “display”/VNC/Spice password on one of my VMs. When I booted it gave me the “NO VNCs for YOU” error. I went and changed the bad VM and booted into the already installed FT environment and still no VMs. I deleted the 25.04.2 FT boot enviornment and did a re-upgrade and it worked. Sucessful upgrade and VMs are back…
This is important… so, you have to make sure the VMs were in a good shape 1st. Then do the upgrade (please elaborate).
FYI: It looks like we have about 2,000 users that have updated to 25.04.2. We should have a better handle on all issue by next week.
Update: 4000+ users on 1st day and expect 10,000+ users today (aug 1). Its getting thoroughly beaten.
Yes, after I Booted back into EEL, Deleted the previous FT boot environment, and did a fresh upgrade of EEL to FT, FT booted just fine and VMs work. It looks like the problem is in the install code not in the run code. As long as the VMs are fixed before the upgrade it worked.
The “Virtual Machines: Cannot Retrieve Response” bug can be easily fixed by following these instructions:
2 Likes
I switched to 25.04.02 for a moment and tried to install the PR.
It does not work at least not that simple.
admin@lion[~]$ git reset --hard HEAD~1
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
So again I switched back to 24.10.2.2
Please consider using Openwrt official image: GitHub - openwrt/docker: Docker containers of the ImageBuilder and SDK
in container.
As noticed here before and described here and in my thread ^25-04-2-oh-no-my-vms-not-working^ the problem has been identified as a vnc-port issue and a temp PR suggested.
I tried the PR … I could not install it (see above). However I am far from sure that the described problem is THE or the only problem.
I switched back to 24.10.2.2 and checked the port numbers as related to my VM’s since the patch description indicates that the issue is related to ports numbers < 5900 … non of my ports are
However there is more … I did not assign a display device to all my VM’s and the port number seems to be assigned to the display device …
Never the less it all works in 24.10 … but not in 25.04 …
Where did you get that command from?
It’s not in the thread linked to by Stux.
Higher up in this thread under ‘PR’
Okay, those automatic comments by the “bugclerk” are not meant for you to run. They are related to the build-process and only relevant to the developers.
Hmmm.
That was an informative link, not an instruction. I’ll try to clarify.