Tag: Fixes

5th February 2015 · Luca Sturlese

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…

Read More “Fix – No coredump target has been configured”

3rd February 2015 · Luca Sturlese

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…..

Read More “Fix – Access to resource settings on the host is restricted”

15th November 2014 · Luca Sturlese

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…

Read More “Storage vMotion does not rename virtual machine files”