Performing hot-add of CPU/Memory/Controller on Clustered Virtual Machine post upgrade to ESXi 8.0U3 or later fails with error "The hot-plug operation failed"
Article ID: 389070
Updated On:
Products
Issue/Introduction
- Performing hot-add of ethernet on Clustered Virtual Machine (VM) fails with error "
The hot-plug operation failed Hot plug operation failed to start. hot-add of ethernet failed"
- /vmfs/volumes/<datastore>/<VM name>/vmware.log:
YYYY-MM-DDTHH:MM:SS Wa(03) vmx - Requesting hot-add of 'ethernet4'.YYYY-MM-DDTHH:MM:SS No(00) vmx - ConfigDB: Unsetting all entries with prefix "ethernet4."YYYY-MM-DDTHH:MM:SS No(00) vmx - ConfigDB: Setting ethernet5.allowGuestConnectionControl = "FALSE"YYYY-MM-DDTHH:MM:SS No(00) vmx - ConfigDB: Setting ethernet5.virtualDev = "vmxnet3"YYYY-MM-DDTHH:MM:SS No(00) vmx - ConfigDB: Setting ethernet5.opaqueNetwork.id = "<network UUID>"YYYY-MM-DDTHH:MM:SS No(00) vmx - ConfigDB: Setting ethernet5.opaqueNetwork.type = "<>"YYYY-MM-DDTHH:MM:SS No(00) vmx - ConfigDB: Setting ethernet5.shares = "normal"YYYY-MM-DDTHH:MM:SS No(00) vmx - ConfigDB: Setting ethernet5.addressType = "vpx"YYYY-MM-DDTHH:MM:SS No(00) vmx - ConfigDB: Setting ethernet5.generatedAddress = "<MAC address>"YYYY-MM-DDTHH:MM:SS No(00) vmx - ConfigDB: Setting ethernet5.uptCompatibility = "TRUE"YYYY-MM-DDTHH:MM:SS No(00) vmx - ConfigDB: Setting ethernet5.pciSlotNumber = "xxxx"YYYY-MM-DDTHH:MM:SS No(00) vmx - ConfigDB: Setting ethernet5.present = "TRUE"YYYY-MM-DDTHH:MM:SS In(05) vmx - Hot-adding ethernet4.YYYY-MM-DDTHH:MM:SS In(05) vmx - HotPlug: Queued ethernet4 add.YYYY-MM-DDTHH:MM:SS In(05) vmx - VigorTransport_ServerSendResponse opID=m41k242n-27864464-auto-gl8cx-h5:73349698-eb-01-32-c15f seq=498: Completed EthernetClass.SetPresent request in 4287 US.YYYY-MM-DDTHH:MM:SS In(05) vmx - VigorTransportProcessClientPayload: opID=m41k242n-27864464-auto-gl8cx-h5:73349698-eb-01-32-c15f seq=507: Receiving HotPlugManager.EndBatch request.YYYY-MM-DDTHH:MM:SS Er(02) vmx - FSR is not supported for disks on a physically shared bus.YYYY-MM-DDTHH:MM:SS In(05) vmx - HotPlug: Unable to initiate hot-plug operation.....YYYY-MM-DDTHH:MM:SS Er(02) vmx - FSR is not supported for disks on a physically shared bus.YYYY-MM-DDTHH:MM:SS In(05) vmx - HotPlug: Unable to initiate hot-plug operation...YYYY-MM-DDTHH:MM:SS In(05) vmx - Devices: Migration failed. Aborting hot-plug.YYYY-MM-DDTHH:MM:SS In(05) vmx - HotPlug: Hot-add of ethernet4 failed.
Environment
vSphere 8.0 Update 3
Cause
The issue is a result of fast-suspend-resume (FSR) being blocked for VMs participating in shared-disk clustering configuration. FSR has never been supported for such VMs. It is an oversight that the operation is not blocked in earlier releases.
Resolution
This is an expected behavior post upgrade to vSphere 8.0 Update 3 and later.
In order to resolve the issue, Proceed to power off the VM and add the desired device (CPU/Memory/Controller device). Refer to How to Add a Network Interface Controller to a Virtual Machine
Additional Information
Incompatible features/configurations for VMX Live Patch/update include:
- frozen instant clone parents, refer to Instant clone parents are incompatible with Live Patch
- vSphere Fault Tolerance
- DirectPath I/O devices that do not support live migration
- vSphere Pods
- VMs participating in shared-disk clustering configuration
In regards to Windows Server Failover Clustering, Refer to
Microsoft Windows Server Failover Clustering (WSFC) with shared disks on VMware vSphere 7.x: Guidelines for supported configurations
In regards to RHEL High Availability Cluster, Refer to
RHEL High Availability Cluster on VMware vSphere 7.x, 8.0: Guidelines for supported configurations
Feedback
