Error of VMotion with CPU lag between hosts

Having a problem with vmotion and incompatibility of function CPU that I hope someone can help me with. We have 4 guests who are servers HP DL360 using Intel Xeon E5345 CPU we recently added another host in the cluster that uses an Intel Xeon E5420 CPU here is the error message when you try to vmotion, a virtual machine to the new host.  New host-based SSE4 and others are SSE3

Impossible to migrate host CPU is incompatible with

requirements of the virtual machine to CPUID level register 0 x 1 ' ecx.

bits of the host: 0000:0100:0000:1000:0010:0010:0001:0001

necessary x 0000:0000:0000:000: xxx0:0x1x:xxx1:x 001

inconsistency detected for these features:

* SSE4.1 see KB artickle 1993 for a possible solution

I looked at the article and I don't know what is the best way to get around this. All virtual machines are set to expose the nx flag to the operating system.  Is it recommended to do CPU bit masking or Enhanced vMotion on the cluster? Enhanced VMotion is disabled on the cluster and cannot be enabled because there is an original 4 guest that any material error is incompatible. I started the new server with the CPUID tool and its Support SSE's SSE4 NX/ED is enabled and supports 64-bit. What could be some possible reasons why other hosts are displayed as incompatible materials? Both processors are listed as being supported for vMotion strengthened on the compatibility table, I spoke with the support and they recommended the creation of a new cluster and enabling enhanced vMotion or turn off the VM and activating on current cluster but all hosts should be considered to be compatible.  We are on ESX 3.5 Update 3

What would be the best way to work around this problem without a major outage?

Thanks for any help.

In my experience so far, no.     I had to stop/restart the VM to bring them to the new cluster.

-KjB

VMware vExpert

Tags: VMware

Similar Questions

  • Peut funtion Vmotion and Storage Vmotion with Intel and AMD hosts within the same cluster

    Hi, I can do storage Vmotion OR Vmotion between Intel and AMD hosts within the same group?

    Thank you

    No, it is not possible to vmotion or storage vmotion between CPUs from different manufacturers - I heard rumors that two manufacturers are working on technology that will help in the future-

    If you find this or any other answer useful please consider awarding points marking the answer correct or useful

  • vMotion (without shared storage) between two hosts with different vSwitches standard s VM

    I can VM vMotion (without shared storage) between two hosts with different vSwitches standard? The vSwitches on these two hosts have different names and number of NIC, but have the same name of portgroup.


    Thank you.

    Yes, you can in a Storage VMotion to one Esxi to another with no shared storage...

    It is important the portgroup bears the same name... This is the reference for the VM...

  • VDI Vmotion between hosts with appvolumes

    All we need to consider here?

    My server admin was the work of the host and put in maintenance mode.  Ended up with a lot of errors on the VMs for the vmotion with Appstacks and writable volumes attached.

    http://KB.VMware.com/kb/2116782


    I'm happy I regularly check the KB VMware Digest because it is not listed in the known issues in all the release notes section.

  • vMotion between hosts on different subnets

    Before you start, I'm a network engineer, not a server guru, please bare with me

    Is it possible to vMotion a virtual machine to a host on an IP network to another host, on a different IP network?

    Example:

    Data Center 1 - 10.1.1.1/24 with VM in the 10.1.2.0/24 ESX Server

    Same city, different site, binding fiber 10 GB between facilities 2ms latency

    Data Center 2 - 10.2.1.1/24 in the 10.2.2.0/24 with VM ESX Server

    Scenario:

    vMotion a computer virtual network 10.1.2.0/24 to the 10.2.2.0/24 network where virtual machine, on arrival on the ESX 2 data center server, now uses a IP address of 10.2.2.0/24.

    Any guidance towards a white paper or a guide would be greatly appreciated.

    Thank you all for your time.

    -Chris

    Network engineer

    Press Ganey Associates

    vMotion is possible between hosts on different subnets, but unless your discussions presented to the virtual machines are on the same subnet, you will eventually drop the virtual machine on a VLAN different and IP addressing will fail.

    There are ways around this, you could script the change of IP address / present several IP addresses of the virtual machine / or reservations DHCP to use, but you will need to ensure DNS etc. records are updated.

    If you have some kind of load balancer, you could in theory balance workloads on 2 IPs hosted on the same VM, to solve the network ip address issues, although in the end, you'll want a VLAN tended to port VM coverage groups.

    Good luck

  • Error during communication with the remote host when you create the new virtual machine

    I'm under 7 ESX servers on IBM Blade H22 there is a mistake to invite while I create a new virtual machine

    on the vcenter Server

    At the end of 30-35 minutes, it gives an error

    "Error during communication with the remote host"

    The existing machines are working well... I tried to create virtual machines to other ESX servers as well

    but the same question. I also tried to make the clone of existing machines, but without success

    Can anyone help?

    You rescan the LUNS once?

    You've restarted the management agent?

    You've restarted the vpxa?

    If this isn't the case, please perform the step above and check out them.

  • Is it possible to host ESX 3.5 VMotion with ESX 4 online?

    VMware newbie

    Is it possible to host ESX 3.5 VMotion with ESX 4 online?

    It is possible.

    And it is necessary to do a guest upgrade without interruption of service.

    André

  • You can VMotion between host ESXi 4 and ESXi 4 Update 1?

    I have a node 2 VMotion, HA cluster. Identical machines running ESXi 4. I want to use the patch to update 1 update. If I VMotion then update all my virtual machines on a host, the other on its own will I be able to VMotion virtual machines on the host being updated from the host not yet updated? Then update the second host.

    Thank you.

    There is no problem doing exactly what you describe - it is supported.

    If you find this or any other answer useful please consider awarding points marking the answer correct or useful

  • vMotion fails at 9% - Source host cannot connect to the destination host

    Hello

    I wonder if someone could shine any light on why vmotion fails to occur between an ESXi host who has just been restarted, in order to test HA. I have the following configuration:

    3 x ESXi5 DL360 G7s with two 4-way NIC

    VSphere Vcenter 5

    1 x cluster configured for DRS HA

    2 x Procurve 2910 - 24G

    The switches are not connected to each other.

    Both switches are configured as such:

    1894901.png

    All ports are not marked. NO PLEASE, no routing

    Each host vMotion vSwitch is connected to two switches by 1 x 1 GB nic

    I configured a vswitch on each host of vMotion. There are two ports vmkernel with two IPS on the same subnet. There are two vmnic attached to the vSwitch. On each port, a Vmic is configured to be active while the other is unused. I enabled frames on the vSwitch and 2910 switches. A VLAN has been configured on the two predisposees 2910 for vmotion with frames and defined traffic on "no label". I can successfully vmkping all the ip s vmotion on all ESXi hosts. However, when I test HA by stopping an ESXi host, when I restart the ESXi host I am unable to vmotion in that ESXi host. When I test vmkping I find that the host rebooted can only vmkping itself and no other host can vmkping it. Vmotion attempt fails on 9% and errors with the source host cannot connect to the destination host. If I restart the two switches of 2910 I can then perform a vMotion and the vmkping is a success.

    Help, please?

    Thank you

    lansley2000 wrote:

    I have since read up on the various load balancing options and find that your method is preferable during the method of "ip hash.

    I'll make the change to "port based" and link the two switches

    Hello Simon, I think it's a good option to do, since the hash IP load balancing is a bit special and really requires both interfaces to connect to the same physical switch, which must also have a specific configuration. If you like the results after the new changes.

  • "Home CPU/memory/connection" (host) changes from green to gray, then gray to green?

    Hey everybody,

    I'm trying to track down a problem with one of my two hosts. My Cluster (2 guests in HA/vMotion) is pretty basic, but runs a lot of VM that requires an availability of 100% (as if we want to accept less ). This is the result I get every two weeks. It's a bit concerning to know that for some reason a node is abandoned, or is it same stall? I see no vMotion alerts or the tasks in that time. Nothing seems to break. Uptime on each virtual computer and the node in question leads me to believe that nothing is really wrong, but it can be worse than what I think. I mean he's only 17 seconds... how bad could it be, right?

    I'm assuming "Host memory usage", "host CPU usage", 'Swap host service rate console', etc. go from green to gray, then gray green means that it is not a resource problem, just an indicator that it is "grayed out" because there no report or an interruption of the connection.

    I guess I am wondering if it is network related, associated hardware partner, vsphere host or something I can't even think. The host disconnects for 7 seconds and no quick vMotioning can't. I think 30 seconds is the rule in front of him vMotions? I mean, I had rather not vMotion, if I can avoid it.

    Whatever it is, what do you think?

    Alarm 'Hosting service console swap rate' on (HOSTNAME) changed from grey to green
    Info
    06/07/2011 19:53:35
    (HOSTNAME)

    Alarm "Host memory using" on (HOSTNAME) changed from grey to green
    Info
    06/07/2011 19:53:35
    (HOSTNAME)

    'Use of the UC to host' alarm on (HOSTNAME) changed from grey to green
    Info
    06/07/2011 19:53:35
    (HOSTNAME)

    Alarm 'Host fell' on (HOSTNAME) sent by e-mail to (ADDRESS);
    Info
    06/07/2011 19:53:26
    (HOSTNAME)

    Alarm 'Host fell' on (HOSTNAME) triggered an action
    Info
    06/07/2011 19:53:26
    (HOSTNAME)

    'Host fell' alarm on (HOSTNAME) has changed from yellow to green
    Info
    06/07/2011 19:53:26
    (HOSTNAME)

    Alarm 'Connection and power supply home State' on (HOSTNAME) changed from red to green
    Info
    06/07/2011 19:53:26
    (HOSTNAME)

    A connection established
    Info
    06/07/2011 19:53:25
    (HOSTNAME)

    A connection established
    Info
    06/07/2011 19:53:25
    (HOSTNAME)

    Alarm 'Connection and power host State' on (HOSTNAME) sent by e-mail to (ADDRESS);
    Info
    06/07/2011 19:53:20
    (HOSTNAME)

    "Failed to connect to host" alarm: sent an SNMP trap for the entity (HOSTNAME)
    Info
    06/07/2011 19:53:20
    (HOSTNAME)

    'The host connection failure' on (HOSTNAME) alarm action
    Info
    06/07/2011 19:53:20
    (HOSTNAME)

    "The host connection failure" alarm on (HOSTNAME) changed from gray to gray
    Info
    06/07/2011 19:53:20
    (HOSTNAME)

    'Hosting service console swap rate' alarm on (HOSTNAME) changes from green to grey
    Info
    06/07/2011 19:53:19
    (HOSTNAME)

    Alarm "Host memory using" on (HOSTNAME) changes from green to grey
    Info
    06/07/2011 19:53:19
    (HOSTNAME)

    'Use of the UC to host' alarm on (HOSTNAME) changes from green to grey
    Info
    06/07/2011 19:53:19
    (HOSTNAME)

    Alarm 'Host fell' on (HOSTNAME) changes from green to yellow
    Info
    06/07/2011 19:53:19


    (HOSTNAME)

    'Connection and power host State' on (HOSTNAME) alarm action
    Info
    06/07/2011 19:53:19
    (HOSTNAME)

    Alarm 'Connection and power supply home State' on (HOSTNAME) goes from green to red
    Info
    06/07/2011 19:53:19
    (HOSTNAME)

    Host is not responding
    error
    06/07/2011 19:53:18
    (HOSTNAME)

    My memory, I cannot keep records for a long time. Last year, I think that I have seen this problem and it was a bug. There is also a patch for it. It was a BUG where the way every now and then, the confidence in me it was no problem at all in the perspective of the environment.

    I don't remember the article or the revision of patch has this connection, but you may need to check the kb.vmware.com to see if you can find.

  • DMA between host and target FPGA is not supported for this remote system.

    I try to cover with my FPGA (on the cRIO-9002) of the RTO.  I have install upward of anOpen good VI reference without error, but as soon I try to access thefifo I error-63001 and the attached message wrote:

    Error-63001 occurredat reference FPGA VI opened in the target - multi rate - variables - fileIO_old.vi

    Possible reasons:

    NOR-RIO FPGACommunications framework: (Hex 0xFFFF09E7) DMA from the host to the FPGA targetis not supported for this remote system. Another method for controller of e/s or climatiqueLes associated with the FPGA target.

    What other I/O optionsdo I need to move the data asynchronously to the RTO for the FPGA. I have triedcreating memory, but it seems that I can't write to the memory of the RTOSside.

    We have also a 9012sitting around will using this cRIO rather solve this problem.

    I'm very very greenwhen it comes to LabView, so I apologize if this is an easy question.

    As stated in the readme of the driver NOR-RIO, DMA is not taken in charge from the host to the FPGA on the cRIO-900 x series. The cRIO-901 x supports DMA transfers between host and FPGA and FPGA to host all the cRIO-900 x series controllers only support transfers the FPGA host DMA. As a result, LabVIEW returns an error if you try to transfer using DMA controller for cRIO-900 x.

    The 9012 looks like the ideal solution, you are very lucky to have additional hardware laying around

  • vCenter Server displays the error message: unable to connect to the host

    vCenter Server displays the error message: unable to connect to the host

    Symptoms

    • vCenter Server cannot connect to a host when you perform operations such as:

    o Storage vMotion

    o cold migration

    o cloning a virtual machine

    o the model deployment

    • Newspapers vpxd that contains an entry similar to:

    [2009-06-04 19:27:16.326 error "App" 4444] [VpxdInvtHost] IP address change for 10.223.122.143 to 10.223.127.197 unhandled, verification of the SSL certificate is not enabled.

    • You see errors similar to:

    Unable to connect to the host o

    o [2009-06-04 19:27:09.952 'Libs' 3902384 WARNING] [NFC ERROR] NfcNewAuthdConnectionEx: unable to connect to peer (numRetries = 2). Error: Unable to connect to the host 10.223.122.143: connection timed out

    • vCenter Server shows the VMS as being disconnected then connected.

    Hello

    Resolution

    Cause

    This problem can occur if an ESX host's IP address is changed while being managed by vCenter Server.

    Check the cause

    To check the cause of the problem:

    1. Log in as root to the ESX host using a SSH client.
    1. In the file etc/opt/vmware/vpxa/vpxa.cfg, find the IP address of the host. The entry looks like:


      10.21.48.121

      Note: for more information about editing the files, see installation in VMware ESX configuration files (1017022).

    Troubleshooting

    If the IP address is incorrect, perform the following steps in order. If the operation does not resolve the problem, continue to the next step. Don't skip a step.

    1. Disconnect and then reconnect the host:
    1. Right click on the ESX host in vCenter Server and click Disconnect.
    1. Reconnect the ESX host in vCenter Server.
    1. Restart the VirtualCenter agent on the ESX host:
    1. Stop the service of vpxa with the command:

      # service vmware-vpxa stop

    1. Open the /etc/opt/vmware/vpxa/vpxa.cfg file in a text editor and correct the IP address of the ESX host.
    1. Start the service of vpxa with the command:

      # service vmware-vpxa start

      Note: for VMware ESXi, you may have to restart all the management agents. For more information, see restart the agents on an ESX or ESXi Server (1003490) management .

    1. Rebuild the VirtualCenter agent on the ESX host configuration file:

      Attention: this step removes all the Statistics counters historical host and the virtual machine. If VMware ESX host is running in virtual machines that starts in a permitted CVS environment, you maybe won't be able to add the host without stopping the virtual machines first.

    1. Right click on the ESX host in vCenter Server and click Disconnect.
    1. Remove the ESX host disconnected from vCenter Server.
    1. Backup the file vpxa.cfg with the command:

      # mv /etc/opt/vmware/vpxa/vpxa.cfg /etc/opt/vmware/vpxa/vpxa.oldcfg

    1. Add the ESX host disconnected to the server vCenter inventory.
    1. Run the following command to view the contents of /etc/opt/vmware/vpxa/vpxa.cfg and confirm that the host IP address is correct:

      # cat /etc/opt/vmware/vpxa/vpxa.cfg

  • Using VMotion with 2 ESX and VCenter

    Hi all

    I just installed with ESX 2 VSphere and & VCenter. I can't use VMotion to migrate a virtual machine running one ESX towards each other.

    My setup is as follows:

    the iSCSI Software initiator.

    data store even shared by 2 facilitators.

    same conf network on the 2 hosts, none vlan used (set to 0):

    • vSwitch0 for the Service console, connected to the network of the company (vmnik0)

    • vSwitch1 for virtual machine network (connected to the company network vmnic1) and VMkernel (for vmotion, connected to the production network: san, vmnic2).

    Error displayed (at 10%): a general error occurred: the VMotion failed because the ESX host failed to connect to the VMotion network, please check your physical network configuration and settings network VMotion.

    vmnic2 on ESX1 is configured with 255.255.0.0 192.168.130.X mask and connected to eth0 on iSCSI SAN

    vmnic2 on ESX2 is configured with 255.255.0.0 192.168.131.X mask and connected to eth1 on iSCSI SAN

    Thanks for help

    alelievre wrote:

    vmnic2 on ESX1 is configured with 255.255.0.0 192.168.130.X mask and connected to eth0 on iSCSI SAN

    vmnic2 on ESX2 is configured with 255.255.0.0 192.168.131.X mask and connected to eth1 on iSCSI SAN

    Two VLAN different connection to the iSCSI SAN. You should have the same subnet, but a different IP addresses (if any) connecting to the San from each host (depends on the SAN)... For example 192.168.130.25 for ESX1 and 192.168.130.30 for ESX2. Unless your SAN network covers actually two subnets on your local network, you create a question where you don't need to. I would also use separate NETWORK card for vMotion traffic and another for iSCSI. Separate them VM traffic too (makes everything cleaner and less chance of collisions and too load performance causing one issues for each other. This is why it is a good idea to have at least four, if not six, physical NIC (or ports) within an ESX/ESXi server.

    VMware VCP4

    Review the allocation of points for "useful" or "right" answers.

  • FFT Error 2015 LabVIEW with crew

    I was invited by my work to upgrade to the production floor. Our production is currently using labview 2012 with about 20 different testers on this. I downloaded and installed labview 2015 runtime and installed on all machines that are needed to upgrade.

    However I noticed a mistake that I can't explain. For some reason, when im trying to build an executable of some testers that have been made by a third-party testing company I get some errors of markup upward. These errors do not appear on the code that we have developed in house, its only third-party programs that are these errors of markup. I have attached a photo of the errors. The other mistake bed

    «Labview: resource not found.»

    An error occurred loading «NI_MAPro.lvlib:ma_FFT with Hanning.vi» VI

    LabVIEW support 3 error code: could not load façade. »

    I have raised a request for assistance with National Instruments, but it's looking like they're not too sure whether. Anyone have any ideas on what I might try?

    I have re-installed labview, re-installed the run-time engine, tried several pc and he always comes back with this error. I checked the dependencies between the two and the location for NI_MAPro.lvlib is exactly the same, there seems to be some indifferences, so I can't explain as to why I get this error.

    Thanks a lot for any help

    Colin

    When you created the executable in 2015, you also created an installer for it?

    You say that you have downloaded and installed the runtime of 2015.  But I think the executable needs something that is not a part of this performance.  My first guess is the lvanlys.dll.

    Try to create a simple VI that comes is a simulation of signal and filtering and an FFT.  Create and .exe and try to run on other machines to see if you still have a problem.  If you do, try to create an installer for this simple executable file and then run that.  See if you still have a problem.  Then see if you still have a problem with your actual executable file.

  • When I try to reply to messages on some websites via Outlook, I get: "no socket error 11001 protocol smtp port 25 google host was not found."

    When I try to reply to messages on some Internet sites via outlook, I get, no socket error 11001 protocol smtp port 25 google host cannot be found.  also when attempt to send from outlook, I get, google found 3 error socket port 110 Protocol pop 0X800CCC0D.i am not very good at such things but can follow directions if they are not complicated to. A few years ago someone set up my computer and I remember their delete something with outlook, because I was going to use google to e mail.but I'm not sure. This problem became a big drawback.

    original title:, not socket error11001 protocol smtp port 25 host not found google, google can't find ox8oocccod

    Hello

    see this link:

    http://www.FixYa.com/support/t2859101-cannot_get_or_send_mail_error

Maybe you are looking for