SCVMM P2V conversion fails during ‘Make operating system virtualizable’

You may run into the problem that a P2V conversion to a machine with an IBM SAN using an older version of SDDDSM fails.  SDDDSM is the IBM MPIO Device Specific Module.

I have also seen this with SCVMM 2007 on Windows Server 2003 with Virtual Server 2005

Now, I had a similar issue with SCVMM 2008 on Windows Server 2008 with Hyper-V

Error (3101)
VMM failed to mount VHD file \\?\<SomeVolumeGuid\vhd>  on the <hostname> server. A timeout occurred.
 (Internal error code: 0x80990C1D)

Recommended Action
Check Device Manager/System Devices to make sure that Microsoft Virtual Server Storage Bus is installed and functional. If it is not, install VHDMount component of Virtual Server. Restart Virtual Disk Service, and then try the operation again.

This problem is fixed in SDDDSM version and greater.

From <>

Defects fixed in 2.4.0.x

4336 Unmounting Virtual Devices in Microsoft virtual Server Fails.

After updating to a recent SDDDSM Version, P2V worked as expected.





Comments (1)

  1. DanSpec says:


    I dont have an ibm san, but I am getting this same error when I attempt to P2V a MS 2003 server we have using vmm 2008 R2. I am migrating it to a MS 2003 host running MS VS 2005 R2.

    Do you have any suggestions as to what might fix this? I read at the link below which said that removing my VS 2005 installation from the host, then installing the current virtual server from scvmm servers vs directory would fix a problem with vm creation template throwing this same error.

    Do you think this might work?

    Server details:

    SCVMM 2008 R2 – on a MS 2008 Server

    Host: Server 2003 running Virtual Server 2005 R2

    (All updates are current as far as I know)

    Physical Machine: Server 2003, no IIS, 40gb primary drive, 499gb software raid5(3 disk) secondary drive.

    I am getting HD errors on the C Drive of the physical server and need to get this done ASAP.

    Any help would be greatly appriciated.

    Kind regards,




    Are you getting the same error 3101 ?

    You might try if the migration to another Server, ideally Hyper-V works, and later migrate it to the VS Server

Skip to main content