Once I built my ESXi 5.5 hosts in my test lab and added them to my vCenter environment, they both had a yellow warning prompt stating: “No coredump target has been configured. Host core dumps cannot be saved”
The good news is I was able to fix this, so I thought to document the solution in case anyone else has the same issue. All the details are below…
I wanted to upgrade the memory on my vSphere 5.1 vCenter server to 16GB and I didn’t have hot-add enabled. I powered off the VM, connected directly to the host and re-configured the VM as required and then clicked OK.
At this point, I got an error saying “Access to resource settings on the host is restricted to the server that is managing it: X.X.X.X”.
The host things it is still being managed by vCenter so it won’t let me edit the VM. vCenter server is powered off so that I can edit the VM (as hot-add is not enabled the VM has to be powered off to change the memory amount).
This is how to fix this issue…..
When you rename a virtual machine in VMware, the VM’s folder and files on the datastore do not get renamed automatically. This can make troubleshooting difficult as it will be almost impossible to find a renamed VM whilst browsing a datastore.
To fix this, you normally do a Storage vMotion of the VM, which would rename the folder and all of the corresponding VM files to the new name. Unfortunately in vCenter 5.0 and 5.1 a Storage vMotion does not rename the VM files, it will only rename the folder.
There is a fix for this so that the VM files get renamed as well. Here is how to do it…
Have your tried to ping your computer or server and it fails even though you know that it is online and connected to the network? One of the reasons why this fails could be because ping is disabled in the Windows Firewall. This article discusses how to resolve this and allow ping through the Windows Firewall.
Here is a quick fix to a problem that I had the other day, which I thought my be useful to a few people.
You logging into the vSphere 5.1 Web Client with the local vSphere Single Sign-On (SSO) user of admin@System-Domain and it fails with the error message of
associated users password is expired.
Below is the solution to this error message…