Enabling VMs completely breaks Unraid, need help asap fixing this as i need a working windows VM.

So I just finally moved over everything after testing unraid for a month with no issues. however i switched from an amd gpu to a nvidia gpu. when i set the gpu in the VM from virtual to the nvidia gpu it completely broke the VMs section. I had VM set to autostart. I have to go into safe mode and disable vms using the native gui, as my array autostarts upon launch. The second i try to go to dashboard, the VM tab, the docker tab or the vm settings in settings, it will not load those section and the remote access stops working, only direct access still functions, but wont load those sections. I am forced to hard reset the system, as even shutting down the array gets broken. Dockers seem to still function in the background, even if i cant access the section. I have removed the vm backups and the isos from their respective locations, both folders are empty but it still breaks the second i enable VMs in the settings. Is there a path forward here? because I would rather not keep hard resetting with the array running while i try to figure this out on my own.

Thank you in advance for any help.

Edit config/domains.cfg on flash drive to disable VMs.

 

Then boot up and

 

Attach diagnostics to your NEXT post in this thread.

pooplexserver-diagnostics-20231227-1845.zip

 

I was able to disable the VMs through the settings by loading up in safe mode, I'm not sure how to edit the config, not sure how to access the /boot/ in krusader and I'm not aware of a way to edit files from the array directory.

I got a bit impatient and started looking in the vm settings in settings and deleted something, im bad with name recollection, it had something to do with isos and virt, that seems to have resolved the issue after a restart. I am successfully inside of my VM again and Unraid is running properly. sorry for the trouble, thanks for attempting to help.

I had the same issue, did you figure out what the issue was?

3 hours ago, Anonymus said:

I had the same issue, did you figure out what the issue was?

I did not find a solution unfortunately. all the things I would have used the gpu for can be done in docker, so i just opted for that route. however dockurr/ made a docker windows, that you are apperantly capable of passing the gpu through with some tinkering, i just havent had the time to test it. its still early days and hes still adding some basic functionality like drive passthrough, but that may be the way forward as other dockers using the gpu seem to be fine.

This seems to also be an issue for all vms, linux did it to me too.

Edited January 20, 20242 yr by Vulkandr