Today I got an error when selecting the “VMware EVC” option in the Cluster Settings at my vCenter 4.0 host with multiple HP Blades with same CPU. Error message:
Method not found: ‘Vmomi.HostSystemArray EVCState.get_BadSoftwareHostsBlockingEVC()’
Solution:
This issue occurs when a system installed with vSphere 4.1 and you use vSphere 4.0 Client on that system to access vCenter Server 4.0.
To workaround this issue, install a vSphere 4.0 Client on a system on which you have not installed vSphere4.1 Client earlier and then update the EVC cluster using the vSphere 4.0 Client.
I’m running NagiosXI in my testlab, to monitor my ESX hosts/VM’s I need to install the Nagios VMware Plugin. What did I do to realize the VMware host monitoring:
You need to install the SDK software.. download the VMware vSphere™ SDK for Perl download version: vSphere SDK for Perl – 32-bit Linux Installer because Nagios is running on a Linux 32-bit VM.
- Upload (with WinSCP) the extracted folder to the Nagios VM /tmp/ ; - Dir to the folder: vmware-vsphere-cli-distrib ; - Install the SDK: ./vmware-install.pl
Sometimes it is necessary to rollback an installation of VMware ESXi, reverting to a previous installation. Last weekend I did this for testing in my home lab. It’s pretty easy…
^ My upgraded VMware ESXi 4.1.0 Build 260247 server
^ Reboot the host and press SHIFT + H to revert the rollback. Message:
Current hypervisor will premanently be replaced with build: 4.0.0.-164009. Are you sure?
Last year we already posted about creating a bootable USB stick. In the last post we used WinImage to create the bootable USB stick to boot ESXi. Some time ago I found a tool which makes it much easier to create a bootable ESXi USB Stick. I am going to use UNetbootin to create bootable USB stick. You can download it here.
1. First connect the USB stick and start UNetbootin
Why am I unable to migrate virtual machines with VMotion across Intel processors?
In ESX 3.5 Update 2 and later, VMware recommends using Enhanced VMotion Compatibility (EVC) to eliminate many VMotion CPU compatibility problems. For more information on EVC, see KB 1003212.
To ensure system stability during migration with VMotion, VirtualCenter and vCenter Server require the source and target CPUs to be compatible. For more information on CPU compatibility requirements, see Basic System Administration for your version of VirtualCenter or vCenter Server, available from http://www.vmware.com/support/pubs/.
If the source and target CPUs are incompatible for VMotion, you can:
Perform a cold migration (rather than a VMotion migration), thereby removing VMotion CPU requirements as an issue.
Remove VMotion compatibility constraints by modifying the default bit-mask used by VirtualCenter or vCenter Server. Note that some modifications discussed in this knowledge base article are neither supported nor recommended by VMware for production environments. In general, masking any CPU features intended for applications (such as SSE3) is not supported for VMotion. Use of EVC is recommended for migrating virtual machines across CPU generations.
