Browsing vVol datastore triggers host disconnect from vCenter
book
Article ID: 393516
calendar_today
Updated On:
Products
VMware vCenter Server
Issue/Introduction
On browsing a virtual volumes datastore in the vSphere Client, host disconnects from vCenter with error "An error occurred while communicating with the remote host."
Within the vVol datastore directory, the VM names are listed as naa.#################### instead of VM display name
Similar loggings in hostd.log
YYYY-MM-DDTHH:MM:SS.789Z warning hostd[#########] [Originator@6876 sub=Libs opID=########-#####-####-####-##:########-##-##-#### user=vpxuser:#######-##\####] #########:VVOLLIB : VVolLib_QueryAllConfigVVolNamesAndIds:5063: [POSSIBLE VP BUG] No friendlyName from VP on VVol (CID: ########-####-####-####-############# VVolId: rfc####.########-####-####-####- #############).
Environment
VMware vSphere ESXi 7.0 U3
Cause
VASA Provider does not return VMW_VVolName in the metadata query operation. This causes invalid memory derefrence and results into the hostd crash.