Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Troubleshooting Migration compatibility error: Virtual machine has CPU and/or memory affinities configured, preventing VMotion (1003842)

Last Updated: 3/21/2024Categories: Total Views: 29851Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

When performing a VMotion migration the following compatibility warning is displayed:

Unable to migrate from <source server> to <destination server>: Virtual machine has CPU and/or memory affinities configured, preventing VMotion .

Resolution

Overview

This error means that CPU affinities have been set for either CPU or Memory to reserve resources on the virtual machine. This configuration is provided to give more control over the allocation of resources in your ESX Server environment.

Typically, this issue is a result of CPU affinity being configured so that the virtual machine runs on a specific set of CPUs.

Note: Scheduling Affinity is hidden in DRS clusters in fully automated mode. If the virtual machine was migrated from an ESX Server 2.x environment see the Additional Information Section of this article if the steps in the workaround do not apply.

Workaround

To workaround the issue you must ensure that there is no CPU affinity configured for the virtual machine. To check the CPU affinity:

Log in to the VirtualCenter as an administrator from the Virtual Infrastructure client.

Right-click on the Virtual Machine.

Click Edit Settings.

Click the Resources tab.

Click the Advanced CPU option.

Check the Scheduling Affinity Section to see if affinity has been set. If affinity has been configured, select the No Affinity radio button to remove the affinity configuration so that you are able to migrate the virtual machine.

To remove the affinity settings in vCenter Server 4.1x and 5.0x, remove the string in Clear the string to remove affinity settings.

Alternatively, you can power off the virtual machine and perform a cold migration to the new host.

Related Information

In some instances this unable to migrate error is seen when a virtual machine has been migrated from ESX Server 2.x to ESX Server 3.x even though no affinities have been set. In these cases sched.mem.affinity = "0" may be in the configuration file for the virtual machine. If this parameter is present in the configuration file for the virtual machine, it can cause the issue to occur in VirtualCenter 2.x.

To remove sched.mem.affinity = "0" from the configuration file:

Log in to the VirtualCenter as an administrator from the Virtual Infrastructure Client.

Shutdown the virtual machine.

Right-click the Virtual Machine.

Click Edit Settings.

Click the Options tab.

Make note of the location of the Virtual Machine Configuration File in the General options section.

Click Cancel.

Right-click the Virtual Machine.

Click Remove from Inventory.

Note: This does not delete the virtual machine, it is removed from inventory.

Log in to your ESX Server service console as root from either an SSH session or directly from the console of the server.

Navigate to the virtual machine's directory noted in Step 6. For example:

[root@server] # cd /vmfs/volumes/<datastore>/<virtual machine>/

where <datastore> is the VMFS volume, and <virtual machine> is the directory that the virtual machine is stored in.

Use an editor such as nano to edit the configuration file of the virtual machine. The file is typically named <virtual machine>.vmx .

Look for a line that shows: sched.mem.affinity = "0" and remove the line and then save the file.

Type logout to log out of the ESX Server.

From the Virtual Infrastructure Client, browse to the datastore and directory that you noted in step 6.

Right-click the virtual machine configuration file (virtual machine.vmx ) and re-register the virtual machine by clicking Add to Inventory.

Power the virtual machine on again, and retry the VMotion.

移行の互換性エラー「仮想マシンには CPU またはメモリのアフィニティ、あるいはその両方が構成されているため、VMotion を実行できません」のトラブルシューティング
对迁移兼容性错误进行故障排除：虚拟机已配置 CPU 和/或内存关联性，这将阻止 VMotion 运行

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 6.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant