After the Upgrade to vsphere 8 u3 unable to vMotion with error : "Error message: A general system error occured: Launch failure Out of resources"

Products

• VMware vSphere ESXi

Issue/Introduction

• After upgrading ESXi from 7.x to 8.x, vMotion to upgraded esxi failed with error message

Error message: A general system error occured: Launch failure <timestamp> Out of resources Cause: Out od resources <timestamp>

• You are using NFS storage which connect to storage through custom TCP/IP stack
• You have several vmkernels in same subnet but different TCP/IP stack

Environment

vSphere ESXi 8.x

 

Cause

• Using custom TCP/IP stack for NFS has been deprecated from vSphere 8.0
• NFS datastore is mounted through a vmkernel IP on default TCP/IP stack which is not configured on Storage side. Therefore the datastore is in read-only mode for this esxi
• To check the IP used to connect to NFS server:

#esxcli network ip connection list | grep -E "Proto|2049"

Proto  Recv Q  Send Q  Local Address        Foreign Address      State        
tcp         0       0  <esxi_vmk0_ip>:<tcp_port>    <nfs_server_ip>:2049   ESTABLISHED

 

 

Resolution

• Use vmkernel on Default TCP/IP stack to connect NFS server.
• Configure NFS server storage policiy accordingly

Additional Information

https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-storage-8-0/working-with-datastores-in-vsphere-storage-environment/nfs-datastore-concepts-and-operations-in-vsphere-environment/configuring-the-nfs-datastore.html#GUID-62A8B27B-B1E0-4E99-A001-C815A70746FA-en

Configure VMkernel Binding for NFS 3 Datastores

For NFS 3 datastores, you can use the vSphere Client to connect the datastore to the desired VMkernel adapters.

• Set up the NFS storage environment.
• Create and configure a VMkernel adapter on default TCP/IP stack.