Setup consists of:
VMM 2012 RC
3 node cluster of Windows 2008 R2 Deployed via VMM 2012 Bare Metal Deployment
3 FC Luns with ample freespace

What I'm seeing during a V2V from an ESX VM is that if I don't have sufficent free space on the local system drive (in my case E: since this is a bare metal deployed system) or If I don't mark the local system drive for placement,  I can't complete the wizard because of warnings about the E: drive either not having enough space or it not being available for placement.

Only if I free up space on the local system drive AND mark it for placment, can I then get to the next screen to select a shared LUN.

Anyone else see this?

I've seen something similar but with P2V. It detects that neither of my two servers have enough storage available for a 2TB .vhd when they both have a connection to a 4.5TB volume cluster volume via C:\ClusterShared\Volume1. It seems it is only taking into account the space available on the local volumes as the default for VMM 2012 is to create non-highly available VMs, so the .vhds must be placed in the local file system. This means it won't take into account any space available on cluster shared volumes.

The system volume has to be available for placement if you want to place the .vhds on the cluster though as that is where the cluster folder is located.

I got round this by thin provisioning a LUN and connecting it directly to the cluster node. The wizard then detects that there is enough space on the local file system (in this case on Z:\) but allowing placement on C:\ also means that I can change the default storage location for the new .vhds from Z:\ to C:\ClusterStorage\Volume1 and deploy a HA VM during the P2V process.

I've seen something similar but with P2V. It detects that neither of my two servers have enough storage available for a 2TB .vhd when they both have a connection to a 4.5TB volume cluster volume via C:\ClusterShared\Volume1. It seems it is only taking into account the space available on the local volumes as the default for VMM 2012 is to create non-highly available VMs, so the .vhds must be placed in the local file system. This means it won't take into account any space available on cluster shared volumes.

The system volume has to be available for placement if you want to place the .vhds on the cluster though as that is where the cluster folder is located.

I got round this by thin provisioning a LUN and connecting it directly to the cluster node. The wizard then detects that there is enough space on the local file system (in this case on Z:\) but allowing placement on C:\ also means that I can change the default storage location for the new .vhds from Z:\ to C:\ClusterStorage\Volume1 and deploy a HA VM during the P2V process.

Hello,

Im facing the very same issue, and I have followed your idea by connecting a LUN directly to the node, but when I run the p2v guide in VMM2012 I still get the dreadful "there is not enough space on the available volumes", I really thought this would be the solution for me but as it seems no :(

Do you have any other ideas ?

IIRC the volume had to be formatted otherwise the cluster node won't see it.

You could try creating a thin provisioned .VHD file on your cluster node and mount that as a Z:\ drive?

I think you might have to refresh the cluster node too so that SCVMM picks up the newly connected drive...

Thx for rapid reply :)

Well, I sure can see the disk on the node, in this case as e:\ , however its not empty, so you believe it will work if I reformat it prior to P2V ?

also in the log of VMM a refresh states that it has found e:after refresh.

Just found this, check it out:

http://support.microsoft.com/kb/2685247

Edit: Oh and you don't need a freshly formattted drive. Just one that you can copy files to. I was assuming you'd created a new LUN without a partition on it.

Did it not work after the refresh found the E: drive then?

• Edited by fusiongroup Friday, July 27, 2012 1:48 PM

Just found this, check it out:

http://support.microsoft.com/kb/2685247

Edit: Oh and you don't need a freshly formattted drive. Just one that you can copy files to. I was assuming you'd created a new LUN without a partition on it.

Did it not work after the refresh found the E: drive then?

• Edited by fusiongroup Friday, July 27, 2012 1:48 PM

Just found this, check it out:

http://support.microsoft.com/kb/2685247

Edit: Oh and you don't need a freshly formattted drive. Just one that you can copy files to. I was assuming you'd created a new LUN without a partition on it.

Did it not work after the refresh found the E: drive then?

• Edited by fusiongroup Friday, July 27, 2012 1:48 PM

Just found this, check it out:

http://support.microsoft.com/kb/2685247

Edit: Oh and you don't need a freshly formattted drive. Just one that you can copy files to. I was assuming you'd created a new LUN without a partition on it.

Did it not work after the refresh found the E: drive then?

• Edited by fusiongroup Friday, July 27, 2012 1:48 PM

Just found this, check it out:

http://support.microsoft.com/kb/2685247

Edit: Oh and you don't need a freshly formattted drive. Just one that you can copy files to. I was assuming you'd created a new LUN without a partition on it.

Did it not work after the refresh found the E: drive then?

• Edited by fusiongroup Friday, July 27, 2012 1:48 PM

Just found this, check it out:

http://support.microsoft.com/kb/2685247

Edit: Oh and you don't need a freshly formattted drive. Just one that you can copy files to. I was assuming you'd created a new LUN without a partition on it.

Did it not work after the refresh found the E: drive then?

• Edited by fusiongroup Friday, July 27, 2012 1:48 PM

Thx, Looks promising indeed, Ill get on to it A.S.A.P ... that is after the weekend.

Have a great one :)

An update on this issue.

I could in no way get it to work even if I followed that KB and set the newly added LUN disk as "available for placement", the p2v guide still told me there was insufficient space available. I solved it by adding a standalone Hyper-V Server with sufficient space to the domain, added that host to VMM, and after doing the p2v to the standalone Host I migrated the server to the cluster, that did the trick, but it would have been great if p2v straight into the cluster as its supposed to had worked, Microsoft: please fix this "bug" A.S.A.P !

Glad you managed to work around it in the end... Although I'm surprised you managed to get it migrated as I've had the same issue when trying to migrate servers too! I ended up having to use Hyper-V admin to export the VM, copy it to the cluster and then re-import it.

James.

there's another workaround which you can try:

• when you select the drives which you want converted (the storage from the source VM), uncheck everything but the OS
• in the next screen of the wizard, choose the destination host and then select the storage which you want to use
• go back to the drivers page and select all of them :)

there's another workaround which you can try:

• when you select the drives which you want converted (the storage from the source VM), uncheck everything but the OS
• in the next screen of the wizard, choose the destination host and then select the storage which you want to use
• go back to the drivers page and select all of them :)

It still give me the error, and dot let me go into the path :(

And i dont have any available machine to do the proposed answer trick.

Also, the script wont work, i tried a diferent one with fewer settings with no luck.

there's another workaround which you can try:

• when you select the drives which you want converted (the storage from the source VM), uncheck everything but the OS
• in the next screen of the wizard, choose the destination host and then select the storage which you want to use
• go back to the drivers page and select all of them :)

I'm facing this dreadful issue. I managed to create a 2 TB dynamic disk on one of the nodes, assigned a drive letter and I can write to it with no problem.

However, it doesn't show up in the Hardware tab to enable it for placement. I believe it knows it is dynamic, so, won't even let me. The funny fact is that it shows that physical disk in the storage tab, but won't show the volume in the hardware tab.

The Volume is a 2TB MBR volume, as requested by the procedure.

luckily, I've managed to create a functional V2V PS script, but it is really annoying that you can't use the wizard.

Any ideas?

Did you refresh the cluster? Drives don't show as available for placement until after a refresh.

It's not that you've got the VM marked as highly available? As other servers in a cluster would not be able to see the volume, it won't let you deploy a HA VM to a disk of this type.

If you create a new VM, the availability bit is in the hardware configuration at the bottom. Doesn't the V2V wizard have a similar page? I'd have thought you would have to select the hardware profile of the destination VM at some point in the wizard?

I'm facing this dreadful issue. I managed to create a 2 TB dynamic disk on one of the nodes, assigned a drive letter and I can write to it with no problem.

However, it doesn't show up in the Hardware tab to enable it for placement. I believe it knows it is dynamic, so, won't even let me. The funny fact is that it shows that physical disk in the storage tab, but won't show the volume in the hardware tab.

The Volume is a 2TB MBR volume, as requested by the procedure.

luckily, I've managed to create a functional V2V PS script, but it is really annoying that you can't use the wizard.

Any ideas?

You can find it here:

http://fehse.ca/2013/10/scvmm-v2v-and-powershell/

Thank you!