After the update to 7.0.0 a few VMs that had worked fine since 6.9.2 began to randomly freeze, then unfreeze after minutes and continue to function like nothing had ever happened. This appears to happen with windows 7, 8.1, and 10 VMs. There doesn't appear to be any reason or cause, as it will happen in VMs running software or freshly started and idling.

 

At first I thought it may be just the viewing system being unresponsive, until I relaunched it a few times and that did not change anything, then I got sidetracked and it became functional/unfroze. Then when one VM froze, one that is functioning as a backup system for my security cameras, I tried accessing the webpage for the security software (Blue Iris) and I could, but it ran very slowly and lagged badly, along with the video streams becoming a slideshow with up to minutes between frames, until the VM unfroze again.

 

The only thing that appears to happen in two threads max out on the dashboard screen when it happens.

 

It does not seem to matter if the VMs are on the cache drive or on the array, or if the parity check is running or not.

Edited July 5, 20251 yr by TheGleaner

Try creating a new VM for one of them, point to the existing vdisk, and retest.

16 hours ago, JorgeB said:

Try creating a new VM for one of them, point to the existing vdisk, and retest.

More frequent, but shorter, freezes occur. 

 

It does appear to be related to disk usage, as when the VM starts using its disks, that greatly increases the frequency and chances of the freezing.

Edited April 4, 20251 yr by TheGleaner

And if you create a new VM with a new vdisk, does it have the same issue?

It looks like you are still using the 7.2 model for the machine type you should be able to change to 9.1.

 

Are you running the latet Win-virt drivers?

 

I would recommend not using the first CPU cores. i.e. 0/1 in my case. NB this is beta 2 so you may not see vcpus.

 

3 hours ago, JorgeB said:

And if you create a new VM with a new vdisk, does it have the same issue?

 

Currently TBD

 

 

3 hours ago, SimonF said:

It looks like you are still using the 7.2 model for the machine type you should be able to change to 9.1.

 

Are you running the latet Win-virt drivers?

 

I would recommend not using the first CPU cores. i.e. 0/1 in my case. NB this is beta 2 so you may not see vcpus.

 

You're going to have to elaborate on that, the first part anyways. For the second, the latest that is supported by the OS usually. The third, I found that out the hard way about a year ago, everything from dockers to VMs are excluded from using the first core/thread pair to my knowledge anyways.

On 4/4/2025 at 2:15 AM, JorgeB said:

And if you create a new VM with a new vdisk, does it have the same issue?

As of right now, it appears to be yes, but the entire server just had an issue, as seen here. I don't know if they are related.

 

 

I just realized this as well, as not having to run my win11 VM for at least 2 months, now, i've restarted my unraid 7.0.1 3x in 1 night, prior to that, it's been 24/7 for several months. 
I didn't notice this until now. 

 

unraid isn't crashing completely, I could open on incognito or another server and still browse the dashboard, main, settings, except VM. 
when I restart/reboot, I get the uncleaned shutdown error notification and parity starts. 

Edited April 28, 20251 yr by lcadmedia