<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cross vCenter Migration - Failing to Relocate in VMware vSphere™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cross-vCenter-Migration-Failing-to-Relocate/m-p/2739947#M34741</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;6.7 may or may not need them, I just don't have one to check.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 14 Jun 2018 18:52:38 GMT</pubDate>
    <dc:creator>sjesse</dc:creator>
    <dc:date>2018-06-14T18:52:38Z</dc:date>
    <item>
      <title>Cross vCenter Migration - Failing to Relocate</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cross-vCenter-Migration-Failing-to-Relocate/m-p/2739944#M34738</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Relocate works great for powered off VMs. I can't get powered on VMs to work. Source is vSphere 6.0 U3 and destination is vSphere 6.7. I keep getting "The target host does not support the virtual machine's current hardware requirements." Both sites have EVC set to Ivy Bridge, so I am not sure what it means by hardware requirements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Source is ESXi 6.0 Build 7967664 (Latest)&lt;/P&gt;&lt;P&gt;Number of microcode updates:1&lt;/P&gt;&lt;P&gt;Original Revision:0x0b000021&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Current Revision:0x0b00002a&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Destination is ESXi 6.7 Build 8169922 (Latest)&lt;/P&gt;&lt;P&gt;Number of microcode updates:0&lt;/P&gt;&lt;P&gt;Original Revision:0x0b00002a&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Current Revision:0x0b00002a&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I even double checked the CPUID Feature Flags to be certain. There are no CPU affinity settings configured or issues with resources/reservations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I am reading this site correctly. &lt;A href="https://kb.vmware.com/s/article/2106952" title="https://kb.vmware.com/s/article/2106952"&gt;VMware Knowledge Base&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vSphere 6.0 U3 to vSphere 6.5 U2 and later* (* This includes all VMware Cloud on AWS versions and vSphere 6.7.) vMotion is supported. So what am I missing? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Jun 2018 23:39:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cross-vCenter-Migration-Failing-to-Relocate/m-p/2739944#M34738</guid>
      <dc:creator>ITaaP</dc:creator>
      <dc:date>2018-06-12T23:39:07Z</dc:date>
    </item>
    <item>
      <title>Re: Cross vCenter Migration - Failing to Relocate</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cross-vCenter-Migration-Failing-to-Relocate/m-p/2739945#M34739</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here is the KB related to this :&lt;A href="https://kb.vmware.com/s/article/52085" title="https://kb.vmware.com/s/article/52085"&gt;VMware Knowledge Base&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With latest vSphere releases, there is little change in vMotion and EVC behavior if your cluster has some hosts does not have these patches applied. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Quoting from KB: &lt;/P&gt;&lt;H3 data-aura-rendered-by="24:115;a" style="padding-top: 10px; padding-bottom: 5px; font-size: 14px; font-family: Arial, Helvetica, sans-serif, 'Bitstream Vera Sans'; color: #000000;"&gt;&lt;SPAN style="font-size: 10pt; font-family: arial, helvetica, sans-serif;"&gt;vMotion and EVC Information&lt;/SPAN&gt;&lt;/H3&gt;&lt;P&gt;&lt;SPAN data-aura-rendered-by="24:115;a" style="color: rgba(77, 76, 76, 0.9); font-size: 12px; font-family: arial, helvetica, sans-serif;"&gt;A&lt;SPAN style="font-size: 10pt;"&gt;n ESXi host that is running a patched vSphere hypervisor with updated microcode will see new CPU features that were not previously available.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 10pt;"&gt;These new features will be exposed to all Virtual Hardware Version 9+ VMs that are powered-on by that host. Because these virtual machines now see additional CPU features, vMotion to an ESXi host lacking the microcode or hypervisor patches applied will be prevented.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 10pt;"&gt;The vCenter patches enable vMotion compatibility to be retained within an EVC cluster.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-size: 10pt;"&gt;In order to maintain this compatibility the new features are hidden from guests within the cluster until all hosts in the cluster are properly updated.&amp;nbsp; At that time, the cluster will automatically upgrade its capabilities to expose the new features. Unpatched ESXi hosts will no longer be admitted into the EVC cluster.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: rgba(77, 76, 76, 0.9); font-size: 10pt; font-family: arial, helvetica, sans-serif;"&gt;Can you confirm whether your source cluster has all hosts patched with build you specified i.e. &lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;7967664&lt;/SPAN&gt; ? Post applying these patches, whether power cycle was done? Whether your destination cluster has all hosts with "&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;8169922" build? &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Jun 2018 13:19:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cross-vCenter-Migration-Failing-to-Relocate/m-p/2739945#M34739</guid>
      <dc:creator>vThinkBeyondVM</dc:creator>
      <dc:date>2018-06-14T13:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: Cross vCenter Migration - Failing to Relocate</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cross-vCenter-Migration-Failing-to-Relocate/m-p/2739946#M34740</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are these fully updated? There are non critical patched for cpu microcode which can cause this, it was for the spectre/meltdown patches. Looking at your information&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Source is ESXi 6.0 Build 7967664 (Latest)&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Number of microcode updates:1&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Original Revision:0x0b000021&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Current Revision:0x0b00002a&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Destination is ESXi 6.7 Build 8169922 (Latest)&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Number of microcode updates:0&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Original Revision:0x0b00002a&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Current Revision:0x0b00002a&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The destination doesn't have microcode updates listed. If you have update manager, check the non critical update baseline. See if there is a cpu microcode patch that should be applied.&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Jun 2018 18:45:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cross-vCenter-Migration-Failing-to-Relocate/m-p/2739946#M34740</guid>
      <dc:creator>sjesse</dc:creator>
      <dc:date>2018-06-14T18:45:53Z</dc:date>
    </item>
    <item>
      <title>Re: Cross vCenter Migration - Failing to Relocate</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cross-vCenter-Migration-Failing-to-Relocate/m-p/2739947#M34741</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;6.7 may or may not need them, I just don't have one to check.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Jun 2018 18:52:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cross-vCenter-Migration-Failing-to-Relocate/m-p/2739947#M34741</guid>
      <dc:creator>sjesse</dc:creator>
      <dc:date>2018-06-14T18:52:38Z</dc:date>
    </item>
    <item>
      <title>Re: Cross vCenter Migration - Failing to Relocate</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cross-vCenter-Migration-Failing-to-Relocate/m-p/2739948#M34742</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Below articles will help you to understand vMotion and EVC behavior post the patches you applied.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Confirming whether entire EVC cluster is patched or not and see new cpubits are available on all hosts (new cpu bits got introduced into these patches)&lt;/P&gt;&lt;P&gt;&lt;A href="http://vthinkbeyondvm.com/pyvmomi-script-confirm-whether-evc-cluster-patched-not-spectre-vulnerability/" title="http://vthinkbeyondvm.com/pyvmomi-script-confirm-whether-evc-cluster-patched-not-spectre-vulnerability/"&gt;http://vthinkbeyondvm.com/pyvmomi-script-confirm-whether-evc-cluster-patched-not-spectre-vulnerability/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. This is again related post: &lt;A href="http://vthinkbeyondvm.com/adding-host-empty-evc-cluster-fails-simple-workaround/" title="http://vthinkbeyondvm.com/adding-host-empty-evc-cluster-fails-simple-workaround/"&gt;http://vthinkbeyondvm.com/adding-host-empty-evc-cluster-fails-simple-workaround/&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Jun 2018 01:42:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cross-vCenter-Migration-Failing-to-Relocate/m-p/2739948#M34742</guid>
      <dc:creator>vThinkBeyondVM</dc:creator>
      <dc:date>2018-06-15T01:42:25Z</dc:date>
    </item>
  </channel>
</rss>

