Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

Migrating a virtual machine between two different vDS version (79446)

Last Updated: 2/26/2024Categories: TroubleshootingTotal Views: 48391Language:
JapaneseEnglishGerman

50 like this article

Subscribe to get an email
newsletter with new updates

50 people found this helpful Please provide article feedback:

Symptoms

When attempting to migrate a virtual machine from one vSphere Distributed Switch (vDS) to another, you experience these symptoms:

The migration fails.

You see these errors in the vSphere Web Client similar to:

The target host doesn’t support the virtual machines current hardware requirements. The destination virtual switch version or type (VDS 7.0.0) is different than the minimum required version or type (VDS 6.6.0) necessary to migrate VM from source virtual switch.

Cause

This issue occurs because there are comparisons being made between the vDS on the source and destination ESXi Hosts/vCenter for the vMotion operation.

The vDS versions must match!

A live migration (a.k.a. Hot Migration) between DVS/vDS versions, is NOT recommended.

Impact / Risks

Migration of the virtual machine would fail, resulting in the error above.

Note: If the below workaround is applied to hot-migrate a VM between vDS/DVS versions, the VM may lose network connectivity.

Resolution

This is an expected behavior when migrating between mixed vSphere Distributed Switches.

To resolve this issue:

upgrade the vDS with the lower version to match that of the higher one, if possible.

Alternatively, power-off the VM and then do the migration (cold migration).

Note: The workaround should only be used for the vMotion between different DVS versions for migrations between on-prem and VMware Cloud. If the below workaround is applied to hot-migrate a VM between vDS/DVS versions, the VM may lose network connectivity.

Workaround

To work around this issue:

vCenter Server 6.5.x and vCenter Server 6.7.x

Log in to the vCenter Server using the HTML5 or vSphere Web Client.

Highlight your vCenter Server name in the left-hand column and then click on the Configure tab on the right.

Go to Advanced Settings and click Edit Settings.

At the bottom of the pop-up window, add the following property in the Name section:

config.migrate.test.NetworksCompatibleOption.AllowMismatchedDVSwitchConfig

Set the value to true.

Click Add.

Click Save.

Re-try the migration.

vCenter Server 7.0.x and later

Log in to the vCenter Server using the HTML5 or vSphere Web Client.

Highlight your vCenter Server name in the left-hand column and then click on the Configure tab on the right.

Go to Advanced Settings and click Edit Settings.

At the bottom of the pop-up window, add the following property in the Name section:

config.vmprov.enableHybridMode

Set the value to true.

Click Add.

Click Save.

Re-try the migration.

Note: For enabling hybrid mode in vCenter, the target DVS version must be at least 6.0.0.

Note: The workaround should only be used for the vMotion between different DVS versions for migrations between on-prem and VMware Cloud. If the below workaround is applied to hot-migrate a VM between vDS/DVS versions, the VM may lose network connectivity.

Related Information

Note: At this time, the workaround does not work if the source vDS is version 7.0.3.

config.vmprov.enableHybridMode = false (default setting)

Destination vDS version

Source vDS version

6.5.0

6.6.0

7.0.0

7.0.2

7.0.3

6.5.0

✅

❌

❌

❌

❌

6.6.0

❌

✅

❌

❌

❌

7.0.0

❌

❌

✅

❌

❌

7.0.2

❌

❌

❌

✅

❌

7.0.3

❌

❌

❌

❌

✅

config.vmprov.enableHybridMode = true (workaround applied)

Destination vDS version

Source vDS version

6.5.0

6.6.0

7.0.0

7.0.2

7.0.3

6.5.0

✅

✅

✅

✅

✅

6.6.0

✅

✅

✅

✅

✅

7.0.0

✅

✅

✅

✅

✅

7.0.2

✅

✅

✅

✅

✅

7.0.3

❌

❌

❌

❌

✅

Understand vMotion networking requirements (59232)
Blog: Hot and Cold Migrations; Which Network is Used?

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglishGerman

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere

Related Versions:

VMware vSphere 7.0.x

VMware vSphere 6.7.x

VMware vSphere 6.5.x

Take Our Survey

Support Assistant