ESXi4.1 in Vcenter 5 vmotion problem

Hello

I'm in the process of migrating my virtual infrastructure Vmware 5.

I installed a new vCenter (build 455964) and I migrated all the hosts to vCenter 4.1 for my new vCenter.

I have IBM HS22 14 blades. In 2010, we bought the first 9 blades and the last this year.

They are all equipped with 2 processors six cores x 5650.

My problem is that I am not able to vmotion of virtual machines between the new blades and the older, those same processors are the same.

The error is: host CPU is not compatible with the requirements of the virtual machine to CPUID level 0 x 1 'ecx' register Inconsistency detected for these characteristics: * PCLMULQDQ and * AES-NI.

I can't activate the VCA mode as I can't turn off the virtual machines.

I tried to update the firmware/bios on the blades, but the result was the same.

Has anyone of you has met with such a problem? Is this a bug of vCenter?

Thank you

Razvan

This isn't a bug with vcenter 4.1.

There is a feature of IBM Blade Server called AES (Advanced Encryption Standard). What stop perform vmotion.

You must disable new AES blade IBM HS22 and add this host to group and see vmotion works like a charm. We had the same problem and we have resolved to disbaling AES on ibm HS22 blade.

See the under IBM KB for the question:

http://www-947.IBM.com/support/entry/portal/docDisplay?lndocid=MIGR-5086963

Price point of useful and correct answer by clicking on the sub tab

Tags: VMware

Similar Questions

  • Quick vMotioning problem between two servers HP BL460c Gen 9 when EVC enabled

    I have two HP BL460c Gen 9 blades configured exactly the same thing with 2 x Intel XEON E5-2660 v3 processors in each of them. Both running the same version ROM (I36 06/05/2015) and running the same version of ESXi (5.0.0 build 2509828). They are managed by a Server Build 2656067 vCenter 5.0.0.

    When I configure these two servers in a cluster with EVC disabled I am able to vMotion between them. However, if I activate the Intel EVC modes so I am unable to vMotion between these two identical servers.  Here is an example of the message that I get when I updated Westmere VCA mode

    Host CPU is not compatible with the requirements of the virtual machine to CPUID level 0 x 1 'ecx' register

    Bits of the host: 0000:0010:1001:1000:0010:0010:0000:0011

    Required: x 110: x01x:11 x 1: 1xx0:xx11:xx1x:xxxx:xx11

    Inconsistency detected for these features:

    * General incompatibilities

    If I disable CVS, then I can vMotion VMs between them.

    I wanted to add these hosts to an existing cluster configured with EVC Westmere mode so that I was able to vMotion between old and new guests, but was unable to vMotion VMs off the new hosts, even if I tried to vMotion to another new host.

    Configure a new cluster with only these two new hosts to so I could experiment. I can only vMotion between them if CVS is disabled. I cannot further increase the VCA mode on this new cluster, for example of Westmere to Sandy Bridge then I have virtual machines under tension within the cluster. For example: I put the VCA mode at Westmere, feeding on a virtual computer, when I go to change the CVS to Sandy Bridge mode I get the following message, I should be able to increase the VCA mode but may not lower it

    The cluster cannot be configured with the selected Enhanced vMotion

    Compatibility mode; The CPU features disabled by this mode may be currently in use

    by slot voltage or suspension of the virtual machines in the cluster.

    I get this message even if I try to set the VCA mode at the same level, that it is already.

    Anyone got any ideas on how to solve this problem?

    Hello

    Seems, your CPU supports 5.0 ESXi and vCenter 5.0, you must upgrade your vSphere vSphere 6.x for the VCA.

    See the links below and also compatibility VCA matrix attached:

    VMware KB: Enhanced vMotion compatibility (EVC) support processor

    Intel CPU VCA Matrix (Enhanced VMware vMotion compatibility) | Virten.NET

  • naming vCenter 5.1 problem

    Hi all

    We had this problem VMware KB: vMotion fails to 15% with the error: the object or target sending is not found

    Cause

    It is a problem that is known about VMware vCenter Server 5.1 and VMware vCloud Director 5.1. This problem occurs when the .vmx file name contains a colon (:)).

    Note: If there are two points in a VM VAPP model name in a vCloud Director environment, it spreads to all virtual machines deployed.

    I just wanted to know, anyone heard of any other appellation limitations to what might cause problems? Just, I thought I would check, as I didn't want to cause any other naming problem while trying to solve this one.

    See you soon!

    http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2046088&sliceId=1&docTypeID=DT_KB_1_1&dialogID=929808625&StateID=1%200%20929826152 contains a list of the characters that should not be used.

  • VCenter and VMotion

    Hello and thanks in advance.

    I work with VSphere 4 Essentials and just finished installing VCenter Server. The problem I have is that I can't add all guests to the 'cluster '. The error message, it's that I need to upgrade the license for VMotion. What should I do to disable VMotion, so I can add hosts to the cluster.

    Thanks again,

    Check all the VMkernel port on the host groups and ensure that VMotion is not enabled.

  • Console remote vCenter access (NAT problem)?

    Hello world

    I have problems accessing my VMRC via vCenter WebClient.

    My network config is as described in the title:

    my office LAN (say 192.168.1.50)-> firewall-> my server room (say 10.1.1.0/24).

    the ESX and vCenter are in the server room.

    To access the server room,'s done it through NAT (IE to access my true IP vCenter 10.1.1.10 I access from my desktop to 200.1.1.10).

    When I access the remote console hollow vSphere Client (so connecting directly to ESX without using vCenter) works (the console log shows that I connect to the NAT address).

    When I want to access a remote console trough the web interface, the console to it log shows tries to reach the REAL of ESX instead of the NAT one address.

    I hope that I was enough to get a clear answer

    Is - this repairable or y at - it a parameter that escapes me in vCenter to make this setup work (I did research all morning without finding a clue).

    Thanks in advance and forgive my approximate English.

    I finally find myself...

    I assumed that, as a result of posting here makes me think differently!

    Solution: Add the host whose DNS name in vCenter instead of IP addresses, then the VM consoles work properly.

  • Add ESXi4 host to vCenter 5.5 has failed, host do not support VSANS

    Hi all. I have to build a laboratory to test running with vCenter 5.5 and a server Dell PE 1950 ESXi 4.  I try to add the ESXi 4 host to vCenter 5.5 (towards a test cluster), however, the process of adding a host failed with the error message "host"x.x.x.x"does not support VSANS".  If anyone of you experience this problem, and is there a way around this problem?  I understand VSAN is a new feature on ESXi 5.1 and later, but I don't expect you to stop me adding ESXi 4 on the cluster... Thank you.

    My bad.  I thought about it.  I activated the VSANS on the cluster; Once I disabled the option to VSAN on the cluster, I am able to add the host ESXi 4...

  • VCenter Unattended Installation - problems INSTALLDIR

    I have been using the published PDF which gives powerful assistance vCenter unattended installs the server: http://www.vmware.com/files/pdf/techpaper/vcenter_server_cmdline_install.pdf

    I have this job for the most part, but a part does not work, and I think I have nailed to the INSTALLDIR switch for the individual MSI files.

    For example, this command does not work (it does appear the msi help window):

    $arguments = ' / QR ADMINPASSWORD = "+ $SSOpasswd + 'DEPLOYMODE = FIRSTDOMAIN SSO_SITE =' + $SSOsite +" INSTALLDIR = "+ $InstallDIR / l * v D:\VCS-INSTALL-LOGS\ssoinstall.log'"

    Start-Process - FilePath "D:\Installs\vCS\VMware-SSO-Service.msi" - ArgumentList $arguments

    However, simply removing the switch INSTALLDIR allows for installation to occur, for example

    ' $arguments = ' / QR ADMINPASSWORD = "+ $SSOpasswd + 'DEPLOYMODE = FIRSTDOMAIN SSO_SITE =' + $SSOsite +" / l * v D:\VCS-INSTALL-LOGS\ssoinstall.log.

    Start-Process - FilePath "D:\Installs\vCS\VMware-SSO-Service.msi" - ArgumentList $arguments

    The PDF to think that this option is available.  In addition, I tested the switch in place without spaces and without quotation marks, so it doesn't seem to be a character double-quotes/exhaust problem. I am also using quotes and characters for passwords exhaust etc so do that...

    I've confirmed that this is a problem (for me at least) to:

    SSO

    Web client

    The inventory service

    vCenter Server

    Dump of the ESXi Collector

    Syslog Collector

    Any ideas?

    I try this using vCenter Server 5.5 Update 2 installation on server 2012 R2 using PowerShell (4).

    Thank you

    Tom

    For the moment that it is:

    $InstallDIR = "D:\Program Files\VMware\Infrastructure".

    Note:

    1. I also tried with an escape with double quote character in the variable argument (according to the PDF in my original post):

    $exe = "$VCmedia\Single Sign-On\VMware-SSO - Server.msi".

    $myargs = ' / QR ADMINPASSWORD = "+ $SSOpasswd + 'DEPLOYMODE = FIRSTDOMAIN SSO_SITE =' + $SSOsite + ' INSTALLDIR =------"' + $InstallDIR + ""-""

    2. I also tried with the escape character (') - same result PowerShell:

    $exe = "$VCmedia\Single Sign-On\VMware-SSO - Server.msi".

    ' $myargs = ' / QR ADMINPASSWORD = "+ $SSOpasswd + 'DEPLOYMODE = FIRSTDOMAIN SSO_SITE =' + $SSOsite +" INSTALLDIR = ""' + $InstallDIR + "" '

    3. I also tried with a path that has no spaces - this works:

    $exe = "$VCmedia\Single Sign-On\VMware-SSO - Server.msi".

    $myargs = ' / QR ADMINPASSWORD = "+ $SSOpasswd + 'DEPLOYMODE = FIRSTDOMAIN SSO_SITE =' + $SSOsite +" INSTALLDIR = D:\VMware'

    So, who does not point to a problem with spaces/quotes - but I don't know what I'm doing wrong...

    I've added a line if it looks like this now:

    $exe = "$VCmedia\Single Sign-On\VMware-SSO - Server.msi".

    ' $myargs = ' / QR ADMINPASSWORD = "+ $SSOpasswd + 'DEPLOYMODE = FIRSTDOMAIN SSO_SITE =' + $SSOsite +" INSTALLDIR = ""' + $InstallDIR + "" '

    $myargs = $myargs + "" / l * v D:\VCS-INSTALL-LOGS\ssoinstall.log ""

    Write-Host "command: Start-Process $exe $myargs - wait."

    Start-process $exe $myargs - wait

    The output from the Write-Host shows this:

    Command: Start-Process D:\INSTALLS\vCS\\Single signe-On\VMware-SSO-Server.msi/qr ADMINPASSWORD = Hello! 2 DEPLOYMODE = FIRSTDOMAIN SSO_SITE = VCS - SSO INSTALLDIR = "" D:\Program Files\VMware\Infrastructure "" / l * v D:\VCS-INSTALL-LOGS\ssoinstall.log-attendre "

    The escape character is still there - suggesting that I do not understand how to use it!  I just removed the script and it works, so the controls are now:

    $exe = "$VCmedia\Single Sign-On\VMware-SSO - Server.msi".

    $myargs = ' / QR ADMINPASSWORD = "+ $SSOpasswd + 'DEPLOYMODE = FIRSTDOMAIN SSO_SITE =' + $SSOsite +" INSTALLDIR = "" ' + $InstallDIR + ' "'"

    $myargs = $myargs + "" / l * v D:\VCS-INSTALL-LOGS\ssoinstall.log ""

    Write-Host "command: Start-Process $exe $myargs - wait."

    Start-process $exe $myargs - wait

    Write-Host now says:

    Command: Panel Start-Process D:\INSTALLS\vCS\\Single-On\VMware-SSO-Server.msi/qr ADMINPASSWORD = Hello! 2 DEPLOYMODE = FIRSTDOMAIN SSO_SITE = VCS - SSO INSTALLDIR = "D:\Program Files\VMware\Infrastructure" / l * v D:\VCS-INSTALL-LOGS\ssoinstall.log-attendre

    Personally, I'm surprised that it works, but it's cool, I'm still learning - I'll try and look a little more information about quotes, spaces and the behavior of the variables when it is passed to a cmdlet.

  • VMware vCenter Orchestrator Configuration problem

    Hi guys,.

    My company has just installed VMware vCenter Orchestrator and we try to create a new host to vCenter server with version 5.0.1.

    Can someone point me to documentation that shows me how to configure the web page in the print screen attached?  Or can someone please tell me what is needed in the empty fields, etc.?  When we try to enter info, we get alerts of service of red light of the vCenter Server tab and the tab startup options.  Both give us a red circle indicating a problem.

    Thank you!

    A free IP address? Oh... No, this plugin configuration is not actually CREATE a vCenter for you, it allows you to configure the vCO to speak to an EXISTING vCenter server you must already have a server vCenter configuration somewhere and you must use the FULL domain name or address IP of this server in this configuration.

  • SQL vCenter Orchestrator config problem

    I recently downloaded and installed vSphere 5. I installed vCenter and added my esxi servers successfully. I'm trying to configure Orchestrator. When I connect and try to set up the database, I can not connect. I'm not sure what to put. I entered the ip address of the local computer, which is where I installed the vCenter server. When I installed vCenter he installed SQL 2008. I guess it creates the database for Orchestrator, is this correct. If this is not the case, what should I do to get this working. I downloaded SQL 2008 express manager but cannot even see that the database. How to solve this problem?

    Hello

    The vCenter Server Setup does not create a database for Orchestrator.

    Here's what you need to do to set up the database of the vCO.

    First configure SQL Server Express to the remote connection. Here are the steps:

    http://pubs.VMware.com/vSphere-50/topic/com.VMware.vSphere.vco_install_config.doc_42/GUID-0F8AE76E-6BB0-4679-B597-973E4ECB8177.html

    Then manually create the database of vCO. For SQL Server Express, you can use the osql tool (just search osql on the computer on which you installed SQL Server Express). The osql.exe file can be found here:

    C:\Program Files (x 86) \Microsoft SQL Server\90\Tools\Binn\

    or here:

    C:\Program Files\Microsoft SQL Server\100\Tools\Binn\

    The steps for creating a database with OSQL are:

    1. start the osql tool in a command prompt.

    (a) go to the installation directory.

    (b) type osql.exe EI

    (EI means approved connection).

    2. create the database of vCO, vco, for example.

    (a) on the first line type: CREATE DATABASE vco

    (b) on the second line type: GO

    Finally, you can configure vCO to work with SQL Server Express using the interface Configuration of the vCO. The steps to do this are provided as examples in the subject to: http://pubs.vmware.com/vsphere-50/topic/com.vmware.vsphere.vco_install_config.doc_42/GUID841EB9F0-2CBC-44E3-9AC2-4EBAE36F6942.html

    I hope this helps.

  • VMware Vcenter Orcestrator Configuration problem - LDAP connection

    Hi all

    I got the task to implement Ccenter and I'm having a small problem.

    I configured everything except the configuration of the LDAP connection in the web configuration of vcenter.

    I am receining the following error:

    Type

    Title

    Description

    Error

    LDAP connection successful but no users found. Check LDAP paths.

    LDAP connection successful but no users found. Check LDAP paths.

    Error

    Group admin not found

    I have no real expereince LDAP so I'm totally lost on this error message.

    Can anyone offer any help on this problem?

    Thank you - Ron

    For the configuration of Orcestrator see this good guide:

    a user's guide to configure vCO

    And see also this case:

    LDAP Orchestrator 4.0 configuration

    André

  • vCenter / Orchestrator configuration problem

    Hello

    While the implementation of vCenter Server and Orchestrator configuration, I had trouble to finish. I am not able to find any user who is a member of the Group of Directors vCO to fill the Plug-ins section which is necessary to Boot Options. The other Orcestrator server cannot run to add a user in the Administration Group (assuming that this is the place that it should be done) wihout fill first the Startup Options section in the Web Configuration.

    The back Orchestrator Installation and Configuration Guide not clearly how do a user member of the management group until the administrator has started, however, it says "enter the credentials of a user who is a member of the group administrator Orchestrator." I tried the default user (vmware), the user I set up in the pub for vCenter Server service running and the local administrator, but he keeps giving the error «Bad credentials for the installation of the plugin.» "Unable connect user: vCenter, unknown user.

    Any help is appreciated how go about this situation.

    Hi Martell,

    I'm sorry to hear that you are having problems with the configuration.

    Let me see if I could erase this until relations are here.

    1. the user name that you used to connect to the Configurator is not related to any configuration in the configurator.

    2. the user of the plugin in the plugin name must be in the ad group that you specified in the LDAP tab under group admin vCO.  Here is my config of the sample for the vCO admin group: "CN = vco - admin, CN = Users, DC = pm - vco, DC = local.

    I guess that if you add the service account used by running vCenter Server to the group admin vCO listed above you will be ok.

    Let us know if it works.

    SIA

  • Installing vcenter 6.0 problem

    I when I install vcenter

    the error is

    unsupported 16-bit application

    the program or feature

    "\?? \G:\VCenter-Server\vmware-vCenter-Server.exe cantnot start or run due to the incompatibily with 64 bit versions of windows. Contact the reseller of software to ask if there is a version compatible with windows 64-bit.

    I have

    OS: windows server 2008 r2

    These error messages occur often with images installation damaged, so first check the checksum of the download.

    André

  • Ability to add esxi4.1U2 to vCenter - esxi 4.1composed

    Hello

    It is possible to add a ESXi 4.1 update 2 host to vCenter 4.1 cluster composed of hosts ESXi 4.1 ?

    Thanks in advance.

    Yes, you can. This works. See the matrix of interoperability of VMware products.

    http://PartnerWeb.VMware.com/comp_guide2/SIM/interop_matrix.php

  • editing essentials vCenter logon Active Directory problem

    Hello

    I have problems with my setup 5.1 VSphere (edition essentials, max 3 guests). I installed the appliance virtual vcenter without any problem, but I can't add AD users to the configuration of permissions.

    The vcenter device appears in AD very well and "query domainjoin-cli" tells me that the device is joined to a domain.

    I added some screenshots to illustrate my problem.

    http://i47.tinypic.com/2mgjprl.png

    I have no option to select the AD users

    vcenter_AD1.png

    vcenter_AD2.png

    My management screen appears to be limited compared to the screenshots I found on the internet. When I click on "configure authentication", nothing happens. I re - run the Configuration Wizard, nothing helps.

    I have no problem join hosts separate esxi announcement and logging into them using AD accounts.

    Hello

    Welcome to the community.

    A few questions:

    -What user are helps you connect to the device via the client vSphere vCenter?

    -Did you try to use the Web Client vSphere? What makes it look like there?

    -How is your SSO configured?

  • Cannot Storage Vmotion between EMC Celerra NFS and NFS VNX

    Recently we have improved our infrastructure VMware 3.5 to 5.0. Managed to migrate all virtual machines to the Esxi5.0 without any problems. More recently, we bought new storage EMC VNX 5300, set up and configured the NFS storage for the early. All the warehouses of new data related to blades and all storage pools, old and new can be found under vCenter.

    Problem we have is that we can not Storage vMotion virtual machines of the old Celerra NFS for new NFS VNX stores. It comes back with the error "cannot access file VM VNX {datastore} filename '. We got a similar message appears when you try to create a new virtual machine or import an OVF on VNX new data warehouses.

    We have the license of the company, with Dell M600 blades with EMC storage as mentioned above.

    Pointers would be appreciated

    Kem

    Thanks for your contributions, but I solved it. A bit of a 'schoolboy error', but although I had added to the VMKernel IP in the host root and read-write in the NFS export properties, I also need to add the IP address of the hosts/blades. Storage vMotion successfully in new stores VNX. THX Kem

Maybe you are looking for