Can't access VM settings or VM page on Unraid

[madmanx]

Would anyone be able to point me in the right direction, my Unraid VM settings is unresponsive, so if I start my array and click on the VM tab it just displays a page without any VMs and if I try and go to the VM settings again a blank page. i think its related to an issue I had with the passed through NIC and somehow may have corrupted. What can I do to restore. I have backups of all the VM's so that isn't a particular issue. Just dont know where to start.

 

I've attached my Diagnostics

titan-diagnostics-20220312-0950.zip

[Squid]

Try it in safe mode.  Also try manually spinning up all the drives in the array before going to the VM tab

[NeariX]

 Same issue here. I have 3 VMs running (Debian, Macinabox and Windows Server 2019) and when i go to the VMs tab it loads the Web page, but the VMs list is empty and loads forever. If I try to leave the page, no other page loads as well, making the Webinterface inresponsive.
However, I can still control the VMs from the Dashboard if it decides to load someday.

I found a "fix": abort website loading, open the login url of unraid and sign in again. WebGUI works (as long as you avoid the VMs tab)

Unraid 6.10.0-rc4

towernas-diagnostics-20220503-0917.zip 

[mikeyosm]

This has started happening to me too. Today I tried to start a 3rd VM, the VM would not start and then the VM page and VM settings page become unresponsive. The only way to resolve is to restart the UNRAID host. Just to add, when this happens, all opther VMs, dockers etc are running fine and no other issues. Just the UNRAID UI VM and VM settings page wont load. Logs show nothing out of the ordinary.

 

I'm running 6.10 latest RC.

[kl0wn]

Add me to the list

[itimpi]

On 6/24/2022 at 11:29 AM, mikeyosm said:

I'm running 6.10 latest RC.

Probably not relevant but 6.10.3 had gone stable so you should not be running a RC.   It is now the 6.11 release that is in RC state - I think RC4 currently.

[LumpyCustard]

Add me to the list of people experiencing this issue.

 

I recently assisted a friend with purchasing a new server and got him onto Unraid. While remotely configuring his brand new server and completely stock installation of Unraid (no plugins, no major configuration changes outside of setting a password), I noted that his VM tab would become unresponsive and load for minutes on end.

 

Dashboard, Main, Shares, Users, Settings, Plugins, Docker, Apps, Stats, Tools -- all load instantly, but VM tab loads for ages and ages.

 

The VM's are running fine, they can be remoted into using SSH and RDP, but the VM tab itself just doesn't load.

 

I've begun to experience this on my own installation of Unraid as well which has been deployed for over a year.

 

If i wait 5+ minutes the VM page contents appears (with no VM's visible) and i'm left with the Unraid loading symbol in the centre of the screen.

 

After a few more minutes the VM's appear, but if i try to connect via VNC i get a "Connecting..." screen which i've never seen before.

 

The only way to "fix" the issue is by rebooting the Unraid host. And again, to be clear, my friend is running a stock installation of Unraid with NOTHING installed on it, not a single docker image or plugin. All i did was create a blank Windows 10 VM with no GPU passthrough or any other advanced settings.

 

 

Video:

 

Edited September 4, 2022 by LumpyCustard

[Kilrah]

Have you made sure any adblocker/script blocker is disabled for the Unraid pages and cleared cookies?

[LumpyCustard]

As you can see in the gif my adblocker is disabled. 
 

Clearing cookies does not resolve. 

 

I note that one of my CPU's cores is permanently pinned once this issue starts:

 

 

After killing the below highlighted process with the SIGKILL command, the VM tab begins to work properly again.

 

 

And after killing it my CPU is no longer pinned.

 

Edited September 5, 2022 by LumpyCustard

[ashebanow]

Same thing just happened to me: Unraid 6.12.4, plenty of space in cache and in pool. Only thing I did that was at all relevant was deleting a VM I no longer used.

 

EDIT: it came back after a reboot. But weird.

Edited November 22, 2023 by ashebanow