Latest Posts



Translate

Total Pageviews

Friday, 8 August 2014

Troubleshooting migration compatibility error: Device is a SCSI controller engaged in bus-sharing (1003797)

Symptoms

  • VMware vMotion migration fails.
  • VMware vMotion migration fails to start.
  • When performing a vMotion migration, you see a compatibility error similar to:

    Unable to migrate from <source server> to <destination server>: Virtual machine is configured to use a device that prevents migration: Device '<device>' is a SCSI controller engaged in bus-sharing.
  • VMware Storage vMotion migration fails.
  • VMware Storage vMotion migration fails to start.
  • When performing a VMware Storage vMotion migration, you see a compatibility error similar to:

    Virtual machine is configured to use a device that prevents the operation: Device 'SCSI controller X' is a SCSI controller engaged in bus-sharing.
    Device 'SCSI controller X' is a SCSI controller engaged in bus-sharing.

Cause

This issue occurs if you have a SCSI controller in use in a virtual machine, which has the bus-sharing mode changed to either virtual or physical. This configuration is used in virtual machines that are running Microsoft Cluster Services (MSCS).

Resolution

VMware does not permit vMotion or Storage vMotion migrations when a virtual machine is using SCSI bus-sharing. This includes Oracle RAC and MSCS virtual machines located on Storage DRS datastore clusters.

To work around this issue, VMware recommends migrating a virtual machine that is participating in SCSI bus-sharing by powering down the virtual machine that resulted in the error message and performing a cold migration to the new host. For more information on cold migrations, see Cold Migrations from the vSphere 5 documentation Center.

For more information on Oracle RAC, see Appendix A of the Oracle Databases on VMware RAC Deployment Guide.

For information on specific virtual machine configurations which can prevent migration of a virtual machine with vMotion, see Overview of migration compatibility error messages (1003684)
Source:-