Software⏱️ 3 min read📅 2026-06-11

How to Fix: vSphere error when powering virtual machine

vSphere error when powering virtual machine: Invalid value for configuration key "scsi0:4.fileName" and "scsi0:3(fileName)". Fix: Update the VMX file to match the rules in /etc/vmware/configrules.

Quick Answer: Update the VMX file to ensure it matches the rules specified in /etc/vmware/configrules, specifically for the "Virtual SCSI Devices" rule.

The error 'Failed to start the virtual machine (error-18)' indicates that the vSphere setup is unable to configure the virtual machine according to the rules specified in /etc/vmware/configrules. This issue affects users who have successfully installed VMware and vSphere on their local machine, added VMX files from datastore to inventory, but are experiencing this specific error when powering up a virtual machine.

This error can be frustrating for administrators as it prevents them from starting the virtual machine, which is essential for their work. However, by following the steps outlined in this guide, you should be able to resolve the issue and get your virtual machine up and running.

🔍 Why This Happens

  • The primary reason for this error is that the VMX file path '/disk2/vmserver/hdisks/hpbsni_3ndDisk_tmpDB.vmdk' does not match the configuration key 'scsi0:4.fileName'. The value was not accepted by the rule 'Virtual SCSI Devices', indicating a mismatch between the specified path and the expected format.
  • An alternative reason for this error could be that the VMX file path '/disk2/vmserver/hdisks/hpbsni_2ndDisk.vmdk' does not match the configuration key 'scsi0:3.fileName'. This also results in an invalid value being accepted by the rule, leading to the same error.

🚀 How to Resolve This Issue

Correcting the VMX File Path

  1. Step 1: Verify that the VMX file path matches the configuration key 'scsi0:4.fileName'. Check the '/disk2/vmserver/hdisks' directory for any discrepancies.
  2. Step 2: Rename or move the conflicting VMX file to a different location, ensuring it does not conflict with the specified configuration key.
  3. Step 3: Update the configuration key 'scsi0:4.fileName' in /etc/vmware/configrules to match the corrected VMX file path.

Reconfiguring the Virtual SCSI Devices Rule

  1. Step 1: Open the '/etc/vmware/configrules' file in a text editor and navigate to the section related to 'Virtual SCSI Devices'.
  2. Step 2: Review the configuration rules for any references to the conflicting VMX file path. Update or remove these references as necessary.

🎯 Final Words

By following the steps outlined in this guide, you should be able to resolve the error and get your virtual machine up and running. Remember to verify that the VMX file paths match the configuration keys and update any necessary configuration rules to avoid similar issues in the future.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions