Article number
Affected Versions
Source Hypervisor
Target Hypervisor

Configuring Protected VM with VMware Paravirtual SCSI (PVSCSI) does not boot on fail-over

Viewed 936 times

Root Cause

A user may question if the Paravirtual SCSI (PVSCSI) controller type is the reason why the recovery VM does not boot.

More about the Paravirtual SCSI (PVSCSI) controller, please see the VMware KB article "Configuring disks to use VMware Paravirtual SCSI (PVSCSI) controllers (1010398)".


When a user configures the protected VM to use the VMware Paravirtual SCSI (PVSCSI) controller, upon failover, the recovery VM may not boot.


If using the Paravirtual SCSI PVSCSI controller, and the recovery VM does not boot, it is likely due to the boot drive not being assigned to controller ID 0 and SCSI ID 0:0.

Configure the boot drive (e.g C: on Windows) to be on "controller ID=0"  and "SCSI ID=0" (0:0)