Fixing VMware Virtual Machine Pvscsi Import Error

This quick post is aimed to help you fix the “Invalid target disk adapter type: pvscsi.” error that can occur when importing a virtual machine into a VMware virtualization product.

In this example I’m using VMware Workstation Pro 14 on Windows 10, however the fix should apply to other versions such as VMware Player or VMware Fusion as well.

Upon importing the virtual machine, it would error right at the start with the following message:

Invalid target disk adapter type: pvscsi.

VMware virtual machine import pvscsi error message

Now an OVA file is basically just a zip containing other files needed for the virtual machine.

In this case I used 7-Zip to extract the contents of my OVA file, which contained .mf, .ovf, and .vmdk files.

The .ovf (Open Virtualization Format) file contains XML which describes the packed virtual machine, so it’s just a text file. We’re going to edit this in our favourite text editor.

The following section defines the SCSI controller for the virtual machine, and this is where the problem lies.

        <rasd:Description>SCSI Controller</rasd:Description>

Simply edit the ‘ResourceSubType’ to lsilogic, as shown below.

        <rasd:Description>SCSI Controller</rasd:Description>

In this instance, I’ve only modified the ResourceSubType from VirtualSCSI to lsilogic. I don’t recommend changing the rest of the Item tag unless you’re still having problems, in most cases you should only need to edit the ResourceSubType.

This took me a while to work out, as when I initially searched the .ovf file I was searching for instances of ‘pvscsi’, which did not exist.

Once the .ovf file has been saved we’re not done yet, we still need to take care of the .mf file, which contains hashes of the .vmdk and .ovf files. As we just modified the .ovf file above, the hash is no longer correct, so you will receive the following error if you try to import the virtual machine at this stage:

SHA digest of file *.ovf does not match manifest.

VMware ovf hash file change

To fix this you need to install OpenSSL, I’ve installed this in Windows but the syntax should be the same regardless of operating system. Basically you want to run the following command, replacing the names of the .vmdk, .ovf, and .mf file as appropriate.

E:\>openssl sha1 .vmdk .ovf > .mf
WARNING: can't open config file: /etc/ssl/openssl.cnf


The warning isn’t really an issue here, that directory doesn’t exist on Windows. Regardless, the hashes of the .mf file are regenerated. You should now be able to simply open the .ovf file with your VMware product and it should start importing correctly.

Leave a comment ?


  1. This saved me a lot of time, thanks!

  2. Thankx a lot!! Did the trick!!

  3. It is possible just to delete the .MF . The import will ignore it not been there and continue

  4. Thank you ! It saves me !

    @Bill : thanks for the MF trick !

  5. Thanks a lot for the tip!

  6. Great Post, thanks for the help with my Fortinet VMs

  7. Thanks! Great!

  8. Just for the case you get an invalid manifest at line1, just open the file in notepad++ and convert it to UTF-8 + save. That should do it!

  9. Thank you, thank you, thank you!

    Ran into this importing Amazon’s AML2 into VMware Workstation. Works like a charm.

  10. Thanks so much for this. For anyone searching hopefully google picks this up, I used this process to successfully fix Cisco’s FMCv OVF creating a VM in VMWare workstation 14. Until Cisco fixes the VM packages this will be my go to fix for VMWare Workstation.

  11. Thanks for this, helped me get my OVA working in workstation!

  12. Thanks a lot for this tutorial.

    To make it easier, instead of openssl, I installed an exploer context menu extension that calculate file checksums in many formats

Leave a Comment

NOTE - You can use these HTML tags and attributes:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>