1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

VMotion from Xeon D host to E3-1265 V2 host

Discussion in 'VMware, VirtualBox, Citrix' started by K D, Apr 20, 2017.

  1. K D

    K D Active Member

    Joined:
    Dec 24, 2016
    Messages:
    456
    Likes Received:
    104
    I have a few VMs running in a host with Xeon D 1518 that I need to Migrate to a host with E3-1265 V2.

    I get this error.

    Code:
    The target host does not support the virtual machine's current hardware requirements.
    To resolve CPU incompatibilities, use a cluster with Enhanced vMotion Compatibility (EVC) enabled. See KB article 1003212.
    1 GB pages are not supported (PDPE1GB).
    MOVBE is unsupported.
    FMA3 is unsupported.
    How can I fix this? Both are standalone hosts (not part of a cluster) that are managed by vcsa.
     
    #1
  2. Evan

    Evan Well-Known Member

    Joined:
    Jan 6, 2016
    Messages:
    1,057
    Likes Received:
    138
    Set enhanced EVC, you will need to set the EVC to the lowest level of the oldest least capable cluster member.
    If it's not currently set correctly which it won't be by the sounds it will need a restart though.

    I assumed it can be set for sand alone hosts as well...
     
    #2
    K D likes this.
  3. K D

    K D Active Member

    Joined:
    Dec 24, 2016
    Messages:
    456
    Likes Received:
    104
    Thanks. I do not have any clusters. So I should create a new cluster with the right level of EVC and add the 2 hosts to it? No change will be required to the VMs?
     
    #3
  4. K D

    K D Active Member

    Joined:
    Dec 24, 2016
    Messages:
    456
    Likes Received:
    104
    1. Created a new Cluster with EVC level at Ivy Bridge
    2. Moved VCSA, DC and couple of other critical VMs to a third host and shutdown all other VMs
    3. Moved host 1 and host 2 into the cluster.
    4. Shutdown all VMs except VCSA and VMotioned them into host 1.
    5. Booted up all VMs and now able to move them between the hosts.
    Now : How do I move VCSA also into this new cluster. I cannot shut down VCSA like I did the others VMs.
     
    #4
  5. K D

    K D Active Member

    Joined:
    Dec 24, 2016
    Messages:
    456
    Likes Received:
    104
    NVM Figured it out. Shutdown VCSA and used OVF Tool to move the VM between hosts. VCSA took a longer time to come up on first boot in the new host. But everything looks good now.

    Point to note : When moving the VM using OVF Tool, thin provisioned disk changed to thick provisioned disk 240GB in size and filled up the data store. So I did a storage VMotion and changed it back to thin provisioned.


    Thanks @Evan

    Code:
    Microsoft Windows [Version 10.0.14393]
    (c) 2016 Microsoft Corporation. All rights reserved.
    
    C:\>cd C:\Program Files\VMware\VMware OVF Tool
    
    C:\Program Files\VMware\VMware OVF Tool>ovftool.exe vi://root@172.xxx.xxx.001
    Accept SSL fingerprint (5B:C9:EA:BF:3F:E8:D3:1B:82:D5:D4:E9:7D:D5:A5:2D:8D:C7:A7:B9) for host 172.xxx.xxx.001 as source type.
    Enter login information for source vi://172.xxx.xxx.001/
    Username: root
    Password: ******************
    Error: Found wrong kind of object (ResourcePool). Possible completions are:
      stor1.dns.net
      Win2012R2_DC_Base
      hades.dnet.dns.net
      vcsa.esxi.dns.net
    
    C:\Program Files\VMware\VMware OVF Tool>ovftool -ds=ADT-RAID-DS vi://root@172.xxx.xxx.001/vcsa.esxi.dns.net vi://root@172.xxx.xxx.002
    Enter login information for source vi://172.xxx.xxx.001/
    Username: root
    Password: ******************
    Opening VI source: vi://root@172.xxx.xxx.001:443/vcsa.esxi.dns.net
    Enter login information for target vi://172.xxx.xxx.002/
    Username: root
    Password: ******************
    Opening VI target: vi://root@172.xxx.xxx.002:443/
    Deploying to VI: vi://root@172.xxx.xxx.002:443/
    Transfer Completed
    Completed successfully
     
    #5
  6. Evan

    Evan Well-Known Member

    Joined:
    Jan 6, 2016
    Messages:
    1,057
    Likes Received:
    138
    Sorry did not get to reply in time but seems your all sorted :)
     
    #6
  7. nk215

    nk215 Active Member

    Joined:
    Oct 6, 2015
    Messages:
    212
    Likes Received:
    52
    When I need to move VCSA to another host, I usually just clone and delete the original.
     
    #7
Similar Threads: VMotion Xeon
Forum Title Date
VMware, VirtualBox, Citrix Slow vmotion in ESX (nvme2nvme@56GbE) Feb 26, 2017
VMware, VirtualBox, Citrix What VMware software should I download for Vmotion, DRS, HA, etc? Feb 13, 2014
VMware, VirtualBox, Citrix xeon d cluster Jan 14, 2016
VMware, VirtualBox, Citrix Intel Xeon D-1540 10GbE X552/X557 driver/VIB for VMware ESXi 6 coming SOON! Oct 19, 2015
VMware, VirtualBox, Citrix ESXi Hardware compatiblity with Xeon E56xx Sep 24, 2015

Share This Page