2022-02-02, 01:18:43
PROBLEM SOLVED! (sort of...)
Hi Wil:
Thanks for the quick reply - I believe I have found the problem - it is related to Windows 10 "Fast startup".
Apparently when enabled it causes windows to create a "small" partial hibernation file that Windows uses on start up - it obviously is listing a VM as "running" when it actually is not running! Here is a link to an article that explains the issue. I was tipped by some info on using WOL where this Windows setting can "sometimes" cause difficulties.
How to disable Windows 10 fast startup (and why you'd want to) | Windows Central
With Fast startup disabled in windows 10, everything works properly with Vimarun - unfortunately with it disabled the Wake On Lan ability also seems to get disabled somehow! This might be because of my hardware, but it works correctly when Fast Startup is enabled in Windows. Will have to test on my other server which is using more recent hardware. I would guess that the "small" hibernation file that is getting written happens before windows gets signalled that the VM is no longer running so provides incorrect info to Vimarun on a restart. Not sure why this isn't the case on a simple "restart" command.
Regards, Dave Melnyk
Hi Wil:
Thanks for the quick reply - I believe I have found the problem - it is related to Windows 10 "Fast startup".
Apparently when enabled it causes windows to create a "small" partial hibernation file that Windows uses on start up - it obviously is listing a VM as "running" when it actually is not running! Here is a link to an article that explains the issue. I was tipped by some info on using WOL where this Windows setting can "sometimes" cause difficulties.
How to disable Windows 10 fast startup (and why you'd want to) | Windows Central
With Fast startup disabled in windows 10, everything works properly with Vimarun - unfortunately with it disabled the Wake On Lan ability also seems to get disabled somehow! This might be because of my hardware, but it works correctly when Fast Startup is enabled in Windows. Will have to test on my other server which is using more recent hardware. I would guess that the "small" hibernation file that is getting written happens before windows gets signalled that the VM is no longer running so provides incorrect info to Vimarun on a restart. Not sure why this isn't the case on a simple "restart" command.
Regards, Dave Melnyk