Hi Stefan,
I was doing some research and I couldn't find a statement that says it is not supported. Even as vCenter manages all the vvol construction it looks like it is supported or should work anyway (its another VM at the end)
Did you have the issue with only one host or did you try again the same to other host and encounter the same issue?
(There was and old issue related to sizes of disks that generated errors in vmotions in the past. It is worth a try: Check the disk sizes for your vCenter, and make it to a round number, like 50GB, no 49,39GB for example)
Do you have other things running in vvols? Did you test other vms migrations?
