S
Shaqamaca
Hi.
I am having this problem that after I startup up desktop machine my virtual machines are in a bad state if restoring a "saved state".
This appears in the virtual machine as "disk I/O error" and nothing can be written to the disk.
I get these events.
08:32:02 The Snapshots configuration 11156FDE-93C9-40DD-81EE-7E9C86B02FF3 at 'G:\WinDev1****80C at 'G:\WinDev1811Eval.HyperV' is now accessible.
08:31:41 The Virtual Machines configuration 111E6205-215D-459A-A419-A2E6AB90680C at 'G:\WinDev1811Eval.HyperV' is no longer accessible: The device is not ready. (0x80070015).
Rebooting the virtual machine fixes everything so I believe this has to do with some race condition.
For now I try to actually power down my virtual machines so that I cold boot them when I need them and that is a workaround.
But I can't have machines starting automatically when my host boots up due to the above errors.
Strangely enough. I am using Docker and the guest mobylinuxvm does not seem to have this problem.
Should I delay HyperV somehow until host has finished whatever is causing this or is there a known fix ?
Continue reading...
I am having this problem that after I startup up desktop machine my virtual machines are in a bad state if restoring a "saved state".
This appears in the virtual machine as "disk I/O error" and nothing can be written to the disk.
I get these events.
08:32:02 The Snapshots configuration 11156FDE-93C9-40DD-81EE-7E9C86B02FF3 at 'G:\WinDev1****80C at 'G:\WinDev1811Eval.HyperV' is now accessible.
08:31:41 The Virtual Machines configuration 111E6205-215D-459A-A419-A2E6AB90680C at 'G:\WinDev1811Eval.HyperV' is no longer accessible: The device is not ready. (0x80070015).
Rebooting the virtual machine fixes everything so I believe this has to do with some race condition.
For now I try to actually power down my virtual machines so that I cold boot them when I need them and that is a workaround.
But I can't have machines starting automatically when my host boots up due to the above errors.
Strangely enough. I am using Docker and the guest mobylinuxvm does not seem to have this problem.
Should I delay HyperV somehow until host has finished whatever is causing this or is there a known fix ?
Continue reading...