- ESXi 7.0 running with local VMFS datastores setup on multiple U.2 NVMe Intel® SSD DC P4510 Series in each server. Not a vSAN setup.
https://ark.intel.com/content/www/us/en/ark/products/series/122570/intel-ssd-dc-p4510-series.html - During an HCL audit, we needed to update the NVMe driver from VMware’s to Intel’s.
VMware ESXi 7.0 intel-nvme-vmd 2.0.0.1146 NVMe Driver for Intel
https://my.vmware.com/web/vmware/downloads/details?downloadGroup=DT-ESXI70-INTEL-INTEL-NVME-VMD-2001146&productId=967 - The Release_Notes_intel_nvme_vmd-2.0.0.1146.pdf warns “Data Stores May Disappear after Upgrading from VMware NVMe inbox Driver to Intel VMD Driver or Intel NVMe Drive”
- The re-signature process “esxcli storage vmfs snapshot resignature -u” worked to allow the local datastores to appear with “snap” added and new UUID. Exploring the datastore shows all of the VM folders and data.
Register All VMs on a ESXi Datastore via CLI
- All the VMs on the local datastores were still inaccessible since the VMX file was looking for the same datastore and UUID per the .VMX file.
- SSH into the ESXi host and run this command to Register all .vmx files on each datastore in scope. Replace “Datastore_Name” with the real name. In my lab test setup “nfs2”
- find /vmfs/volumes/Datastore_Name/ -maxdepth 2 -name ‘*.vmx’ -exec vim-cmd solo/registervm “{}” \;
- find /vmfs/volumes/nfs2/ -maxdepth 2 -name ‘*.vmx’ -exec vim-cmd solo/registervm “{}” \;
- Setup
- ESXi 7.0 running with local VMFS datastores setup on multiple U.2 NVMe Intel® SSD DC P4510 Series in each server. Not a vSAN setup.
https://ark.intel.com/content/www/us/en/ark/products/series/122570/intel-ssd-dc-p4510-series.html - During an HCL audit, we needed to update the NVMe driver from VMware’s to Intel’s.
VMware ESXi 7.0 intel-nvme-vmd 2.0.0.1146 NVMe Driver for Intel
https://my.vmware.com/web/vmware/downloads/details?downloadGroup=DT-ESXI70-INTEL-INTEL-NVME-VMD-2001146&productId=967 - The Release_Notes_intel_nvme_vmd-2.0.0.1146.pdf warns “Data Stores May Disappear after Upgrading from VMware NVMe inbox Driver to Intel VMD Driver or Intel NVMe Drive”
- The re-signature process “esxcli storage vmfs snapshot resignature -u” worked to allow the local datastores to appear with “snap” added and new UUID. Exploring the datastore shows all of the VM folders and data.
- ESXi 7.0 running with local VMFS datastores setup on multiple U.2 NVMe Intel® SSD DC P4510 Series in each server. Not a vSAN setup.
- Issue
- All the VMs on the local datastores were still inaccessible since the VMX file was looking for the same datastore and UUID per the .VMX file.
- Fix
- SSH into the ESXi host and run this command to Register all .vmx files on each datastore in scope. Replace “Datastore_Name” with the real name. In my lab test setup “nfs2”
- find /vmfs/volumes/Datastore_Name/ -maxdepth 2 -name ‘*.vmx’ -exec vim-cmd solo/registervm “{}” \;
- find /vmfs/volumes/nfs2/ -maxdepth 2 -name ‘*.vmx’ -exec vim-cmd solo/registervm “{}” \;
