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…
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…
I have decided to build a new test lab at home based on VMware architecture so that I can test and learn new technologies which I don’t always get a chance to play with at work. I have decided to go with a two physical host approach and use my existing Synology DS1813+ NAS for the storage. Because I want to simulate a physical network as much as possible, I am using a Cisco SG300-10 layer 3 switch to perform all of the management of all of the VLANs and the routing between them and my home network.
I am currently in the process of purchasing all of the hardware and building the lab. Below are all of the details of what my final test lab will look and the reasonings behind why I have made the decisions I have….
Since vSphere 4.1 you have the option of setting the number of cores per CPU in a virtual machine. This allows you to present logical processors to a VM into specific socket and core configurations. This feature is commonly know as corespersocket.
So the question arises…. is it better two assign multiple sockets or multiple cores per socket?
Below we look into the best practices and when to use which option…
If you are installing VMware ESXi on a server \ computer, sometimes you might run into a problem where ESXi cannot detect a Network Adapter (NIC) and therefore will not allow you to continue the installation. The reason for this is because the native ESXi installer does not contain the drivers for the NIC you have installed. This is the situation I found myself in recently when building an ESXi host in my home test lab.
To resolve this problem, we need to inject the drivers into the VMware ESXi installer image and therefore create a custom VMware ESXi image. Although this sounds hard, it is actually pretty easy. Below are the steps required to achieve this…
VMware Hot-Add is an awesome feature – adding CPUs and RAM to a virtual machine without having to power off, however have you ever wondered why it isn’t enabled by default? Recently I was reviewing our VM templates at work and was wondering if we should turn on CPU Hot-Add and Memory Hot-Add on our templates, therefore making it available for all new VMs. I did some research, and this is what I found….