Hi AaronKColleage,
The disk conversion process is done to "patch" the VM to accommodate for differences between platforms and to try to ensure a bootable VM. During the migration process, things like disk UUID, networks, etc will change, so the disk conversion process attempts to accommodate for this.
Have you opened a Support Case for the behavior yet? Regrettably we won't be able to tell what went wrong with the conversion over the forums as it will require a review of the debug logs for a proper answer.
Also a small hint: Were the backups of the source machine taken with Guest Indexing enabled? For *Nix machines, the Guest Indexing process does a bit more than just collect information about files on the system, and it often helps (is required) for V2V conversions like this. Give it a shot with indexing enabled if it was not enabled and see if it goes better.
The disk conversion process is done to "patch" the VM to accommodate for differences between platforms and to try to ensure a bootable VM. During the migration process, things like disk UUID, networks, etc will change, so the disk conversion process attempts to accommodate for this.
Have you opened a Support Case for the behavior yet? Regrettably we won't be able to tell what went wrong with the conversion over the forums as it will require a review of the debug logs for a proper answer.
Also a small hint: Were the backups of the source machine taken with Guest Indexing enabled? For *Nix machines, the Guest Indexing process does a bit more than just collect information about files on the system, and it often helps (is required) for V2V conversions like this. Give it a shot with indexing enabled if it was not enabled and see if it goes better.
Statistics: Posted by david.domask — Sep 30, 2025 8:03 am






