vMotion fails with the error: Failed to connect and reserve network I/O resource : DVSwitch xx xx ... port ####. Failed with error status: Out of resources.
search cancel

vMotion fails with the error: Failed to connect and reserve network I/O resource : DVSwitch xx xx ... port ####. Failed with error status: Out of resources.

book

Article ID: 345402

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

 

For VMs with vNIC reservation in place, vMotion fails with the error: Failed to connect and reserve network I/O resource : DVSwitch xx xx ... port ####. Failed with error status: Out of resources.

 

The vmx logs(vmware.log) would indicate below warning.

[YYYY-MM-DDTHH:MM:SS].803Z In(05) vmx - [msg.migrate.waitdata.platform] Failed waiting for data. Error bad0017. Out of resources.
[YYYY-MM-DDTHH:MM:SS].803Z In(05) vmx - [vob.vmotion.dvs.state.restore.failed] vMotion migration [a5c0915:4018306704830071695] failed to get DVS state in the restore phase from the source host <IP_Address>
[YYYY-MM-DDTHH:MM:SS].803Z In(05) vmx - [vob.net.dvport.insufficient.resources] Failed to connect and reserve network I/O resource: DVSwitch # # # # # # # #-# # # # # # # # port ####. Failed with error status: Out of resources.


vmkernel log of the destination host will report the below errors: 
 

[YYYY-MM-DDTHH:MM:SS].795Z cpu38:13894739)WARNING: VMotionSend: 3568: 4022596704830075763 D: failed to get DVS state in the restore phase from the source host <IP_Address>
[YYYY-MM-DDTHH:MM:SS].795Z cpu38:13894739)WARNING: VMotionSend: 5896: 4022596704830075763 D: Failed handling message reply GET_DVS_STATE: Out of resources
[YYYY-MM-DDTHH:MM:SS].795Z cpu38:13894739)Migrate: 102: 4022596704830075763 D: MigrateState: Failed
[YYYY-MM-DDTHH:MM:SS].795Z cpu38:13894739)WARNING: Migrate: 256: 4022596704830075763 D: Failed: Out of resources (0xbad0017) @0x420015e43ffd
[YYYY-MM-DDTHH:MM:SS].803Z cpu22:13894724)WARNING: Migrate: 6460: 4022596704830075763 D: Migration considered a failure by the VMX.  It is most likely a timeout, but check the VMX log for the true error.

Environment

VMware vSphere ESXi 7.x

Cause

VM's vNIC reservation is set but the System traffic is not defined the vDS (Network I/O Control).

 

Resolution

 

  • Configure Bandwidth Allocation for System Traffic
  • The Network I/O control needs a system reservation set on the VM traffic on the DVS level.
  • Without this, the reservation is not met on the vNIC.
  • Assign bandwidth for host management, virtual machines, NFS storage, vSphere vMotion, vSphere Fault Tolerance, vSAN, and vSphere Replication on the physical adapters that are connected to a vSphere Distributed Switch.
  • To enable bandwidth allocation for virtual machines by using Network I/O Control, configure the virtual machine system traffic.

 

Additional Information

 

Note:

The bandwidth reservation for virtual machine traffic is also used in admission control.
When you power on a virtual machine, admission control verifies that enough bandwidth is available.
For more information , refer vSphere Networking Document at-

vSphere Networking - VMware vSphere 7.0