vmware migrate invalid configuration for device 12

Now the difference in OS is not what is important, but the point in time the template was created is!. The only thing different was the OS used, this was also pointed out by the customer. I took a look at the former template VM's that did go through a successful storage migration and compared the virtual hardware to the ones that failed. When I looked at this issue at first I had no idea what could be the cause of this issue, although it looked like it had something to do with the VM virtual hardware. They failed at 99% with a 'invalid configuration for device 12' error. Well so much for the idea, about 80% of the former template VM's failed the storage migration task. In this way they could leverage the ease of migrating them by Storage vMotion. After all VM's of a particular datacenter were moved successfully, it was time to move the templates.Īs templates cannot be moved by the use of Storage vMotion, the customer first converted them to normal VM's. One of the inevitable tasks involved is moving VM's and Templates to datastores that reside on the new SAN. The current EMC SAN solution was being replaced by a new EMC SAN solution comprised of VPLEX and VMAX components.

During one of my recent projects (replacing ESXi hosts, from rack servers to blades) there was also a second project ongoing that touched the VMware environment.

Vmware migrate invalid configuration for device 12