Earlier in this article, I mentioned that errors in which a VM is unable to change states are not related to the contents of the VM’s virtual hard disk. There is at least one more problem that can cause a VM to be unable to start. If you look at the VM settings in the screenshot below, you can see that the virtual machine’s network adapter is reflecting a configuration error.Īs you can see in the next screenshot, the Event Viewer specifically states that an error has occurred because the virtual switch could not be found. The way that I caused the error shown above was to create a virtual machine and then delete the virtual switch that the VM was configured to use. In case you are wondering though, the event log that I mentioned earlier does provide the reason for the failure. Once again, the error message is less than helpful because it doesn’t provide any information that tells why the VM cannot be started. Here is what a network-related VM boot problem looks like: I’m not even necessarily talking about a VM that has been configured to perform a PXE boot. Therefore, a misconfigured virtual DVD drive can cause a VM boot failure, even if the VM is not attempting to boot from the virtual DVD.īelieve it or not, virtual network configuration errors can also cause a condition in which a VM is unable to start. If you look at the virtual machine’s settings, which you can see in the next screenshot, you will notice that this VM is configured to boot from a virtual hard disk.
You can see what this looks like in the screenshot below.
BLUESTACKS 3 STUCK AT STARTING THE ENGINE ISO
In the case of the event logs indicating that the reason why the VM cannot start is because its virtual DVD drive is pointing to an ISO file that no longer exists. In many cases, this log will tell you the exact cause of the error.
BLUESTACKS 3 STUCK AT STARTING THE ENGINE WINDOWS
Specifically, I recommend checking out the Applications and Services \ Microsoft \ Windows \ Hyper-V-VMMS \ Admin log. When faced with a VM that is refusing to start for an unknown reason, the very first thing that I recommend doing is checking the event logs.
The guest OS cannot boot until the VM reflects a state of “running.” Hence, the problem is tied to the virtual machine’s configuration, not to the guest operating system. Remember, the error message indicates that Hyper-V is unable to change the virtual machine’s state. While it is true that guest operating system corruption can cause a boot failure, error messages like the one shown above occur before Hyper-V even tries to load the guest OS. The biggest mistake that I typically see admins make as they try to resolve the problem is that of assuming that the virtual hard disk is to blame. I have encountered this and similar error messages on real-world, production systems on a few occasions. Upon doing so I received the error message shown below. This morning, for example, I tried to boot a previously healthy virtual machine that I hadn’t used in a few months. Other times, however, Hyper-V does not give you any information regarding the error’s underlying cause. If, for example, the VM is asking for more memory than what the Hyper-V host can provide, then you will receive an error message like the one shown below. When a virtual machine fails to start, the underlying cause is usually obvious. In this article, I wanted to outline a few different potential causes and solutions in case you find yourself with a Hyper-V virtual machine that won’t start. Brien’s solution saved many IT admins from days of stress, and that’s why this article is one of our 20 Best of 2020.Īlthough Hyper-V is normally very reliable, I have on occasion run into situations in which a previously functioning VM refuses to start. In this tutorial from January, Brien offers answers for a perplexing problem: What to do when a Hyper-V virtual machine won’t start. One of the problems with Hyper-V is that it is usually so reliable, so when problems arise users are at a loss.
For our readers who use Microsoft Hyper-V - and there are a lot of them - Brien Posey’s advice, knowledge, and in-depth tutorials are indispensable.
0 kommentar(er)
