Loading...
Loading...
Restoring a virtual machine (VM) to a different vCenter (VC) using Instant Access (IA) results in a power-on failure due to the inability to create a virtual SCSI device. The error messages below indicate a problem with the esx_splitter filter (which RP4VM installs). A VM was restored to a different VC using Instant Access. IA job completed successfully but failed to start the new VM. Error message: Module DevicePowerOn power on failed. Unable to create virtual SCSI device for scsi0:0, ‘/vmfs/volumes/xxxxxxx.vmdk’ Failed to attach filter ‘esx_splitter ‘ to scsi0:0: Not found (195887107).
A specific condition where the source VM is restored to a different VC using IA causes this issue. The IA job completes successfully, but the new VM fails to start due to a virtual SCSI device creation failure. The error message indicates a failure to create a virtual SCSI device for the specified VM Disk (VMDK) file. This results in a Module DevicePowerOn power on failed errorThe error message also mentions an inability to attach the esx_splitter filter to the SCSI device, with a Not found (195887107) error codeThe issue occurs when restoring a VM from a RP4VM-protected ESXi host to another ESXi host that RecoverPoint for Virtual Machines does NOT protectThe presence of the esx_splitter filter, installed by RecoverPoint for Virtual Machines, is a key factor in the failure to start the new VMThe source VM is fine and the source, target VC, and ESXi host versions are consistentRemoving the existing SCSI device and adding it again resolves the issue, indicating a configuration-related problem The issue is specific to RP4VM-protected ESXi hosts and the restoration of VMs to non-RP4VM-protected ESXi hosts.
The resolution to the VM restore issue is to remove the SCSI device from the virtual machine settings or comment out the lines containing esx_splitter in the .vmx file. Step-by-Step Guide Remove SCSI Device from Virtual Machine Settings: Go to the virtual machine settings in the vCenter Server.Click the Hardware tab.Scroll down to the SCSI Controller section.Click the Remove button next to the SCSI device.Confirm that the device is to be removed. Comment out esx_splitter in the .vmx file: Open the .vmx file in a text editor.Search for the lines containing esx_splitter.Comment out these lines by adding a '#' symbol at the beginning of each line.Save the changes to the .vmx file. Verifying the Issue is Resolved: After removing the SCSI device or commenting out esx_splitter in the .vmx file, try to power on the virtual machine again.If the virtual machine powers on successfully, the issue is resolved. Tools and Resources: The vSphere Client can be used to manage the virtual machine settings and the .vmx file. Removing the SCSI device, or commenting out 'esx_splitter' in the .vmx file may cause data loss or corruption if not done properly. Ensure to back up the virtual machine before attempting these steps.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.