I wanted to enable EVC in my lab environment, but found that I couldn’t because my VC was a VM within that same cluster. VC refused to enable it because there was still at least one VM powered on within the cluster. Duh.
Of course, I broke out my handy-dandy do-it-all tool (yep, google) and proceeded to locate a workaround. Lo and behold, I found a useful link. Thanks go out to Bert at http://virtwo.blogspot.com.
He had instructions for how to do this within an ESX 3.5U2 environment. My environment is a complete ESX 4.1 environment consisting of two ESX 4.1 Hosts. Bert’s instructions work fairly well in my environment.
Here’s what I did for my environment:
1) Evacuate one ESX host in your cluster and place it in maintenance mode.
2) Move it out of the cluster, right under your datacenter object.
3) Exit the host out of maintenance mode.
4) Manually migrate (VMotion via drag-and-drop for example) your VirtualCenter VM (running on an ESX host in the cluster) to the ESX host that is now outside the cluster. Do this with all other VMs that were still running in the cluster.
5) Enable EVC on your cluster.
6) Migrate the VMs back to the ESX host within the cluster (again, drag and drop).
7) Place the ESX host back into the cluster.
Now, I have a happy cluster running EVC.
Here’s the link for Bert’s blog entry.
There’s also a KB Article (#1013111) on this subject as well. You can find it here.
Warning: Declaration of Social_Walker_Comment::start_lvl(&$output, $depth, $args) should be compatible with Walker_Comment::start_lvl(&$output, $depth = 0, $args = Array) in /homepages/46/d169553956/htdocs/micronauts/wp-content/plugins/social/lib/social/walker/comment.php on line 18
Warning: Declaration of Social_Walker_Comment::end_lvl(&$output, $depth, $args) should be compatible with Walker_Comment::end_lvl(&$output, $depth = 0, $args = Array) in /homepages/46/d169553956/htdocs/micronauts/wp-content/plugins/social/lib/social/walker/comment.php on line 42
the fix for this issue is1. Rename the exiting vCenter to a new name in the irevntony2. Clone the vCenter to the old vcenter name (destination should be on a host which has vDS configured). Cloning destination datastore should not be same to avoid any VMFS VM name issuesNote: You need two datastore in the ESX to do this.3. Change the cloned VM’s network settings to use the desired vDS portgroup4. Shutdown the existing vCenter5. Connect to the ESX host which has the cloned vCenter VM6. using vmkfstools -i command clone the latest disk from old vCenter to a new vCenter (use the same VMDK names for destination)7. Bring up the new vCenter and you are good to go