This is a known bug that SMB won't play very well in the V2V context.
The easy workaround:
run the conversion and target locally attached storage on the host, and perform a live migration/storage migration afterwards to your SMB share.
can you try this and give me some feedback?
-kn
I actually tried this yesterday and it does work. The interesting thing is that I have performed these from an actual physical machine to SMB storage, sometimes with an erroneous error at the end saying that it failed because of storage (but it doesn't fail) and sometimes with no error.
The site I'm working with is using exclusively SMB storage, most hosts are in a cluster, and they don't have enough local storage to accommodate many of the VM's. I could either set-up a CSV across the cluster or set up a separate host to use as a migration conduit, but either way takes more time.
It's "good" to know this is a know issue...I've seen a few posts alluding to it...but do you know if there's either an MS article on it or if it's acknowledged and they're working on it? It's kind of crummy to have to jump through additional hoops to move someone off of VMware since we're telling them how GREAT SCVMM integration and management is :(