Trying to P2V a server to a CSV volume and getting host placement rating 0 for all Hyper-V hosts although there is enough space available on the CSV volume. This is a known issue with VMM 2012; VMM uses space available on the local drives for calculating available storage in host placement.
Workarounds for this issue is listed in KB2685247. I wanted to share that the behavior is still the same with SP1 UR1. If you are lucky and have enough space on the local drives for at least the used space of the drive you are converting, you can successfully convert using “dynamic disk” to CSV volume (well, at least you can pass host placement screen) and then after the conversion, you can convert the disk to fixed. Method 2 was not acceptable in my case which is to add drives to the hosts and I personally would not want to try out PowerShell method (3) in this case.