One thought was to remove the VM’s from inventory and import them back into vCenter. We hadn’t seen this sort of thing in VMware before. And finally, a third VM on yet another host showed the same symptoms a while later. Same issue, the VM was labeled “inaccessible” and was dead to the world. 30 minutes later we started to get calls that one of the spam filters (a VM on a different host) had gone down.
None of the typical vSphere operations did anything. The VM was completely un-responsive we couldn’t open a console in vSphere and it wasn’t responding to pings. We were doing our routine AM checks when we noticed a production VM had the word “inaccessible” next to it in the console. These are actually all the VMs that are inaccessible on this host right now.It was a Tuesday morning and things were beginning to ramp up in the Sys Admin office. From there, you can simply find all VMs that are inaccessible using the following command:Īs an example, this will generate output like this: And vimsh can do exactly that… It has the ability to reload a VM into a host, and exactly that does the trick!įirst, we need to access the host using ssh or the direct commandline as root. I figured I needed to somehow tell vSphere that the inaccessible VM was actually no longer inaccessible, and force it to reload the configuration. So I came up with a way simpler approach… It just takes more fixing than you might anticipate.
This approach does actually work, but it leaves you with a “new VM that is an old one”.
0 kommentar(er)
