Some interesting finding to share during the last migration I did. I was performed the cold migration for all the virtual machines on the production. Before we migrated over to the new SAN storage, all the current virtual machines are running with thin provisioning enable from vSphere 4. During the storage migration process, you will need to choose either same as source, thin provision or none thin provision. I had chosen same as source option and perform the storage vmotion. After the storage vmotion done, I realized that the virtual machine had no longer with thin provision enable.
Read more »
Yesterday I just did a migration of vCenter server from Physical to virtual. I re-install and configured the vCenter on the virtual machine and manually registered all the ESX host to the new vCenter. 1 of the challenges I faced was the DVswitch. I had created the same DVswitch name and port group in the new vCenter. Guess what, during the migration, the virtual machines network disconnected. I tried to dig around whats went wrong, as I found there was case senstive on the dvswitch. The case senstivie applied and happened on the Hypervisor level but from the vCenter perspective, it may not be the case as Windows does not has the issue with case sensitive. I try to create a new DVswitch port group with the correct case sentitive as I did on the hypervisor previously, vCenter detected as duplicate portgroup name.
Read more »
You may faced the similar issue by default if you currently running your vcenter server 4 on top of Windows 2008. The reason of the services start up failure are due to the dependency setting require to add in manually.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007669
I found the KB above which describe in details about the root cause and solution to over come this.
This issue may occur if the VirtualCenter Server service starts before one of the services it depends on. The VirtualCenter Server service is dependent on the following services:
- SQL Services
- ADAM Services (when using linked mode in vCenter Server 4.0)
Read more »
I’m getting an “error message: 28038″ just before the VMware VCenter Server installation end as screen shot below:
Workaround:
Read more »
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1013013
You experience these symptoms:
Note: You are not affected if one of Service Console Port(s) or Management Network IP address(s) on your ESX host falls outside of this range.
vCenter 4.0 patch 1 will help to fix this issue.
Read more »
