Attempting to power on a restored virtual machine fails with the error: An error was received from the ESX host while powering on VM

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Powering on a restored virtual machine fails.
• A virtual machine fails to power on after a restore.
• In the vSphere Client, you see entries similar to:
  
  An error was received from the ESX host while powering on VM virtual_machine.
  Failed to start the virtual machine.
  Module DevicePowerOn power on failed.
  
  An error was received from the ESX host while powering on VM Guest_recovered.
  Failed to start the virtual machine.
  Module DevicePowerOn power on failed.
  Unable to create virtual SCSI device for scsi0:0, '/vmfs/volumes/5136586a-2f549592-adc7-2c768a4f9620/Guest_recovered.vmdk'
  Failed to attach filter 'hbr_filter' to scsi0:0: Bad parameter (195887111).
  hbr_filter missing required option: gid.
  
  An error was received from the ESX host while powering on VM Guest_recovered.
  Failed to start the virtual machine.
  Module DevicePowerOn power on failed.
  Unable to create virtual SCSI device for scsi0:0, '/vmfs/volumes/4cba568d-f994f502-f56e-e41f1344f9da/Guest_recovered.vmdk'
  Failed to attach filter 'None' to scsi0:0: Not found (195887107).
  
  An unexpected error was received from the ESX host while powering on VM vm-number

You see the following errors under the tasks of ESXi hosts -

Task Name : Power On virtual machine
Status    : hbr_filter missing required option: gid. Failed to start the virtual machine. Module DevicePowerOn power on failed. Unable to create virtual SCSI device for scsi0:0, '/vmfs/volumes/601af123-ff100a9c-1065-0012b545c010/VMware/VMware.vmdk' Failed to attach filter 'hbr_filter' to scsi0:0: Bad parameter (195887111).
Error stack:
Module DevicePowerOn power on failed.
Unable to create virtual SCSI device for scsi0:0, '/vmfs/volumes/601af123-ff100a9c-1065-0012b545c010/VMware/VMware.vmdk'
Failed to attach filter 'hbr_filter' to scsi0:0: Bad parameter (195887111). hbr_filter missing required option: gid.

Cause

This issue occurs when the virtual machine configuration file (.vmx) is corrupted.

Resolution

To resolve this issue, create a new virtual machine configuration file and point it to the existing virtual disk (.vmdk) file.

To create a new virtual machine configuration file and point it to the existing .vmdk file:

1. Connect to vCenter Server using the vSphere Client as an administrator
2. Note the original virtual machines configuration so you can recreate it exactly
3. Right-click the affected virtual machine and click Remove from Inventory
   
   Note: The virtual machine must be powered down to remove from inventory
    
4. Right-click the ESX/ESXi host where you want the virtual machine to run
5. Click the New Virtual Machine
6. Select Custom
7. Since the old machine was removed from inventory, you can name the virtual machine the same as before or name it differently
8. Select the desired datastore for the new virtual machine
9. Select the same virtual machine version as the original virtual machine
10. Select the same operating system, CPU, memory, networking, and SCSI controller as the original machine
11. Select Use an existing virtual disk
12. Browse to and select the .vmdk file from the original virtual machine
13. In Advanced options, select the configuration as it was on the original virtual machine. If you do not know what this was, leave it as default
14. Click Finish to complete the Create New Virtual Machine wizard

This procedure recreates the configuration file (.vmx) for the virtual machine and other supporting files.You can now start the virtual machine from the inventory of the vSphere Client.

Workaround:

Hash out the SCSI disks attached to the hbr_filter in the VMX file. These lines can be hashed or removed completely from the VMX file and it will have no impact on the VM operations or future replication operations. vSphere replication will recreate this information when the VM is added back to replication.  

#scsi0:0.hbr_filter.rdid = "RDID-1b6d1c5e-234e-362e-29c5-6d77134f9bd7"
#scsi0:0.hbr_filter.persistent = "hbr-persistent-state-RDID-1b6d1c5e-234e-362e-29c5-6d77134f9bd7.psf"
#scsi0:0.filters = "hbr_filter"
#scsi0:1.hbr_filter.rdid = "RDID-56c4254e-cdf7-3f7c-b107-437bf665857f"
#scsi0:1.hbr_filter.persistent = "hbr-persistent-state-RDID-56c4254e-cdf7-3f7c-b107-437bf665857f.psf"
#scsi0:1.filters = "hbr_filter"
#scsi0:2.hbr_filter.rdid = "RDID-412840c8-5012-3e1d-84e3-f6e12249afb1"
#scsi0:2.hbr_filter.persistent = "hbr-persistent-state-RDID-412840c8-5012-3e1d-84e3-f6e12249afb1.psf"
#scsi0:2.filters = "hbr_filter"

Reload the VMX file and power ON the VM 

Reloading a vmx file without removing the virtual machine from inventory (1026043)

Additional Information

リストアした仮想マシンをパワーオンしようとすると次のエラーで失敗する： An error was received from the ESX host while powering on VM Guest_recovered.
vMotioning virtual machines fails with Error: Failed to attach filter 'yyy' to scsi
尝试打开已还原虚拟机的电源失败，并显示错误：打开虚拟机电源时收到来自 ESX 主机的错误 (An error was received from the ESX host while powering on VM)