Windows 10 guest keeps sleeping / suspending

[akawoz]

Guys have been trying to troubleshoot this myself but have hit a dead end. I have a vanilla Windows 10 (slow ring) install that keeps entering sleep or suspend mode. Windows is not configured to sleep or suspend. I've generated an energy-report and nothing strange seems to be noted.

 

I've tried moving to fast ring, but no luck. Tried moving between power plans but no change.

 

Strange thing is that if I try to edit any of the standard power plans, there are no timers set under sleep (attachment).

 

XML config:

https://paste.ee/p/mtzDw

 

Energy report:

https://paste.ee/p/i1ieH

 

Last thing I was going to try was to get into SeaBIOS to see if some BIOS config was overriding the OS - but can't for the life of me trigger BIOS entry (using VNC).

 

EDIT: just tried this app: https://sourceforge.net/projects/stayawake/ but still enters a "paused state"

 

EDIT: I've followed this http://lime-technology.com/wiki/index.php/UnRAID_6/VM_Guest_Support prior to posting.

[billington.mark]

Out of the box Windows10 is in "Balanced" mode, which puts it to sleep after a few mins of inactivity.

In the "real" world this isnt an issue as you can set your machine to be switched back on with USB input (like moving a mouse or hitting a keyboard key).

 

to fix:

 

goto the power options in the classic control panel, change it to performance (you might need to expand the "show additional plans" bit to select it.

click change plan settings and make sure its set to never put the PC to sleep.

 

That should stop the VM being suspended.

 

 

[bungee91]

You should do all of the post-install tuning things from this guide:

http://lime-technology.com/wiki/index.php/UnRAID_6/VM_Guest_Support

 

Also, no need to try to adjust SeaBIOS, it is not the issue.

[akawoz]

Out of the box Windows10 is in "Balanced" mode, which puts it to sleep after a few mins of inactivity.

In the "real" world this isnt an issue as you can set your machine to be switched back on with USB input (like moving a mouse or hitting a keyboard key).

 

to fix:

 

goto the power options in the classic control panel, change it to performance (you might need to expand the "show additional plans" bit to select it.

click change plan settings and make sure its set to never put the PC to sleep.

 

That should stop the VM being suspended.

 

Tried this - no change. See my original post :-)

[akawoz]

You should do all of the post-install tuning things from this guide:

http://lime-technology.com/wiki/index.php/UnRAID_6/VM_Guest_Support

 

Also, no need to try to adjust SeaBIOS, it is not the issue.

 

Grasping at straws you see - sometimes regular PC BIOS have these settings that can override Windows config.

 

And I've done all of the wiki items prior to original post.

[jonp]

I bet your vdisk is running out of space.

[akawoz]

I bet your vdisk is running out of space.

 

Yep - that was my first guess, but nope:

 

https://goo.gl/photos/AcetDXn5Gatck3Qn8

 

[jonp]

How much free space on the cache device itself?

[akawoz]

How much free space on the cache device itself?

 

37GB or 18%

[jonp]

Hmm, wonder of when this is happening it's because it's filling up from other stuff temporarily. I'd be curious what the cache drive free space reports as when you are seeing this pause behavior.

[akawoz]

Hmm, wonder of when this is happening it's because it's filling up from other stuff temporarily. I'd be curious what the cache drive free space reports as when you are seeing this pause behavior.

 

Its not actually my cache drive - I've got a 4TB WD RED that I use for cache (2TB+ free at any time) and a couple SSD's mounted with unassigned devices that hold the VM and appdata files. So don't expect any large temp data to be hitting that SSD.

 

Will do a new Win 10 VM install and see if behaviour is same.

 

Attached a full view (with SN's removed) :-)

[akawoz]

OK team, well now I'm really confused:

 

My Win10 VM has gone from suspending at least once every 30 mins to running continuously all night.

 

The ONLY change I have made in that time was the recreation of my docker.img file (size stayed the same) which does live on the same SSD's as my VM qcow2 files. Will keep monitoring but I don't understand how this could be related.