[SOLVED] Unable to create linux VM in 25.04.2

Apps and Virtualization
1

As per the “Installing HAOS in a VM” thread (Installing HAOS (Home Assistant OS) in a VM - #75 by sos_nz) I’ll open a new thread here for specific replies / help.

I’m unable to create a VM in 25.04.2, and the system is saying “Can not retrieve response” (as per screenshot).

Background:
I’m currently running haos in an “Instance”, having migrated the previous Electric Eel VM zvol to an instance when Fangtooth was released. I moved the original zvol, rather than clone it (a mistake in hindsight, since I now have to remake an haos zvol - not difficult, but still…).

So: I’m now trying to recreate a ‘classic’ VM in 25.04.2 using the VM name ‘haos’, according to the guide posted above. I’ve downloaded the image, written it to my 50GB zvol, set up the zvol/CPU/RAM/networking all as per the guide.

But when I hit the final “Next” to actually create the VM, a drop down box appears saying “Virtual machine created” with a green tick - but nothing appears on the UI (again, as attached).

Screenshot From 2025-08-01 12-06-35
Screenshot From 2025-08-01 12-06-351475×742 17.2 KB

I’ve tried clearing the browser cache, reloaded the page AND restarted TrueNAS.

Interestingly, when I try again to recreate the vm, using the same name ‘haos’ TrueNAS says “the name “haos” is already in use”. I’ve also tried creating the vm with a range of new / different names, still no avail, but whenever I re-use the name of a vm I’ve just tried to create, the same “[name] is already in use” error is shown, so something must be saving somewhere, but nothing in the GUI.

EDIT: Could this be because I deleted my old virtual-machine dataset when I migrated to 25.04? I see others have had their phantom VM’s ‘return to life’ upon upgrading to 25.04.2, so I’m presuming there are some stale TrueNAS VM config files floating around which could cause the observed issues.

2

Try giving it a different name HAOS_2.

3

Someone else reported an issue and has the same error message on the Virtual Machine page.

4

I would not lump posts together just by error message window, especially since the upgrade just launched. I would let each thread be sorted out on it’s own.

1 Like
5

Yeah I tried that (and several other names). Still never appears on the list, and the same “can not retrieve response” message is there.

As mentioned above, even after a failed attempt to create a VM, if I try to use the same VM name again, the “name is use” message pops up, so I’m assuming something is being written to a config file somewhere.

Yeah - that was where I’d seen people’s previous VM’s be resurrected automagically, so I’m presuming there are some remnant VM config files still in people’s systems from Electric Eel and the ‘classic’ VM setup. That’s what led me to wonder if deleting my old VM dataset (since there were no longer zvols in it, and it didn’t look like it was going to be needed again) could be causing this issue, i.e. the VM system is trying to reference a dataset that is no longer present.

6

I would try using the Report a Bug feature through the TrueNAS GUI. I figure the more tickets they get, the more data they have from the debug dumps.

7

Done - Jira

1 Like
8

Here is a simple fix:

1 Like
9

Yes, SOLVED, thanks @ Stux.

2 Likes