vMotion or Storage vMotion Fails at 80% with Error "Invalid configuration for device '12'"
search cancel

vMotion or Storage vMotion Fails at 80% with Error "Invalid configuration for device '12'"

book

Article ID: 396442

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • Performing compute or storage vMotion of a VM fails after 80% with below error
    "Failed to relocate virtual machine <VM Name>: Invalid configuration for device '12'."
  • Host Logs show below error

    Hostd.log

    YYYY-MM-DDTHH:MM:SS Er(163) Hostd[2099497]: [Originator@6876 sub=Hostsvc opID=m9iyf8gq-68829-auto-1h3y-h5:70015501-f2-01-9e-372d sid=523b580c user=vpxuser:VSPHERE.LOCAL\Administrator] Failed to search logical switch by switchId: xx xx xx xx xx xx xx xx-xx xx xx xx xx xx xx d4 portgroup: dvportgroup-1620 error: N3Vim5Fault8NotFound9ExceptionE(Fault cause: vim.fault.NotFound)

    YYYY-MM-DDTHH:MM:SS In(166) Hostd[2099497]: [Originator@6876 sub=Hostsvc opID=m9iyf8gq-68829-auto-1h3y-h5:70015501-f2-01-9e-372d sid=523b580c user=vpxuser:VSPHERE.LOCAL\Administrator] Unable to look up dvs xx xx xx xx xx xx xx xx-xx xx xx xx xx xx xx

    YYYY-MM-DDTHH:MM:SS Er(163) Hostd[2099497]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx/xxxx-xxxx/xxxx-xxxx.vmx opID=m9iyf8gq-68829-auto-1h3y-h5:70015501-f2-01-9e-372d sid=523b580c user=vpxuser:VSPHERE.LOCAL\Administrator] Device spec doesn't match up with dvport/dvpg configuration

Environment

vSphere 7.0
vSphere 8.0

Cause

This issue may occur as port group VM is connected does not exist on destination host

Resolution

This issue occurs as  invalid port group is selected for one of the network cards in the virtual machine.
To resolve this issue,

1. Change the VM's port group to one that is available on both the source and destination hosts.

  • "Edit the virtual machine's settings" in vCenter and Navigate to the virtual network adapter 
  • Change the connected port group to a new port group that is available on both source and destination host
  • Save the changes and attempt the vMotion again.

2. If Step 1 doesn’t fix the issue, disconnect and reconnect the ESXi. Follow document Disconnecting and Reconnecting an ESXi Host

Or 

1. Disconnect network adapter of the VM before vMotion from the source host and reconnect the new network adapter from the destination host on other cluster   ( Validate the port group that is different from the other cluster)