Virtualization Team

Vmware ESX/ESXi – MS Hyper-V – ESX server; tutorials, how-to, video

VMware vSphere Training

Entries for May, 2009

MS Hyper-V Virtualization Myths Busting

I have just came across a video of Microsoft trying to bust VMware top Myths, but what is funny to me it seems Microsoft had just busted them selfes in the video than anything else. The link to the video is below:

http://www.microsoft.com/video/en/us/details/f8c3314f-c82d-4f8d-8b19-6a59733670f8

I have seen Gabe reply on his blog at his Gabes virtualization Blog which seems to be a great busting to this video. Below is what Gabe is saying on his blog or please read it directly on Gabe blog at http://www.gabesvirtualworld.com/?p=445. Please give credit to Gabes & read this on his blog :) .

============== Directly from Gabes Virtualization Blog ===========

Comments (1)

ESXi cmd addnode failed for secondary node: /opt/vmware/aam/bin/ft_startup failed to complete within three minutes

In the past few weeks, I had been hit by many calls of many of my colleagues & customers being hit by the following error when trying to configure VMware ESXi HA:

“cmd addnode failed for secondary node: /opt/vmware/aam/bin/ft_startup failed to complete within three minutes”

After investigating the error for sometime & searching on the internet I found many misleading trial and error solutions for this error around Google results. The resolution which seems to work for everyone of my colleagues & customers is below.

1- Disable HA for the affected cluster

2- Delete the User Worlds Swap file called uwswap from all the nodes in the problematic cluster.

3- Enable HA for the affected cluster again.

Comments (6)

MS Hyper-V Crashes under heavy load

This video is just what the title said, MS Hyper-V Crashes under heavy load. Watch out what a mess you are planning to go into!!!!!

I expect to see too many comments on this one, don’t get me disappointed :) .

Comments (6)

Changing the VLAN ID of a ESX Service Console using Command Line

A good amount of ESX admins ask on dialy basis how to change the VMware ESX Service Console Vlan using command line. As I decided to save time by writing the steps for these kind of questions to send it to others when asked. I will document these commands in here:

First of all check which vSwitch the Service Console is on (and the name of the Service Console) with esxcfg-vswitch -l (Note: The default service Console switch is vSwitch0 & default name is “Service Console”.)

To set a vlan id on the service console use:

esxcfg-vswitch vSwitch0 -v X -p “Service Console” (Replace X with the desired VLAN number)

Comments (10)

  




Eiad Al-Aqqad Virtualization & Storage Expert on Linkedin



VMware vSphere Training