Problem Overview After upgrading your VMware ESXi host to version 7.0u3s , you may encounter a critical issue: The attached FC (Fibre Channel) datastore disappears , and all virtual machines stored on that shared storage become “inaccessible” . This issue is common during ESXi version upgrades, where datastores fail to auto-mount due to changes in system recognition or mount configurations. Symptom Description vSphere Web Client still displays the storage device under the hardware list. However, df -h shows that the mount point is missing . Virtual machines that resided on the FC datastore now appear as “Invalid” in the inventory. ✅ This confirms it's not a driver or firmware issue , but rather a mount-related problem. Root Cause During the upgrade, ESXi may not automatically remount previously attached volumes , even though the storage device is visible. The datastore still exists, but it needs to be manually re-mounted using the correct UUID. How ...
🛠 Summary: Fixing vGPU and VVTD Conflict in VMware After work, I received an urgent alert — a virtual machine failed to add a GPU, showing the error: “Virtual machines using vGPU devices do not support VVTD.” This was due to a conflict between NVIDIA vGPU and Intel VVTD (Virtualization-based Trusted Platform Module). vGPU allows shared access to GPU resources via software, while VVTD requires direct hardware passthrough. These two technologies are incompatible by design. Emergency Scenario: Critical Error in Production Environment Just after leaving the office yesterday, I received an urgent message: A virtual machine in our system failed to add a GPU, and the situation looked serious! Rubbing my eyes, I logged into the vSphere Client. The moment I clicked "Add PCI Device," a glaring error popped up: "Virtual machines using vGPU devices do not support VVTD." Seeing the vGPU profile for NVIDIA GRID M60-2Q in the console, I suddenly realized—this was likel...