9 Responses

  1. P. Cruiser
    P. Cruiser at |

    The very strange thing about all of this is how VMware still, even with the latest version of its vCenter Server Appliance, uses multiple disks all on the same single LSI Logic Parallel virtual disk controller.

  2. Tony Williams
    Tony Williams at |


    Thank you for writing this blog post. Would you say that your opinion is the PVSCI should now be a default in VMware environments, or should this still be used for performance and on a case-by-case basis? I think as of one of the 5.5 updates, PVSCSI is supported for MSCS. Any other caveats for making this a default?

  3. Fouad El akkad
    Fouad El akkad at |

    Thanks for this great post, like always.
    Wich Tool can we use to mesure an actual DB VM, IO, and also the amont of queue in controller ?

    1. albertwt
      albertwt at |


      You can use this freeware https://labs.vmware.com/flings/io-analyzer it is versatile and easy to use.

      let me know once you get it tested or have found something else.

  4. GK
    GK at |

    If all the disks are on the same datastore are you getting any benefits from multiple controllers?

  5. Mike Dehaan
    Mike Dehaan at |

    I’m currently battling an issue very similar to this and had a few questions.

    1)What type of log entries have you seen from Windows/SQL from the corruptions?
    2) When the issue can be recreated, what type of traffic typical causes? Just high IO?

    Oddly enough, we’ve only had problems when running VM Hw Ver 13.

    Just to give a little more info, the specific SQL server having issues is w2012r2 w/ SQL 2016. We have PVSCSI adapters but we haven’t defined the SCSI queue in Windows.


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.