Physical server to virtual machine (P2V) migration might fail on 5% progress. This would happen only on physical servers running Linux with kernel version 4.x.
pgmirate command output would resemble following:
# pmigrate h root:email@example.com v localhost/VM_4d3f5651_p2v' Warning: the OS partition will be migrated only, the rest will be skipped Connecting to firstname.lastname@example.org:0... Querying configuration... Migrating to /var/parallels/VM_4d3f5651_p2v ... Operation progress 5 % Error: P2V migration failed For details, see the log file: /var/log/parallels.log
Meanwhile transporter log (
/var/log/parallels.log) on a physical server shows following messages:
02-04 22:34:15.890 F /AgentCore:18066:18168/ Migrating basic partition 1 02-04 22:34:15.890 I /daw:18066:18168/ Initializing snapshot for volume : secbysec 0, exclude page file 1, exclude paths count 0 02-04 22:34:15.890 F /daw:18066:18168/ Error : Failed to create snapshot for volume 02-04 22:34:15.890 F /AgentCore:18066:18168/ Error: Failed to initialize snapshot with error : 0x8103246 02-04 22:34:15.890 F /AgentCore:18066:18168/ Error: Failed to create/initialize snapshot for volume with error : 0x8103246 02-04 22:34:15.890 F /AgentCore:18066:18168/ Error: Migrate basic partition failed with error 0x8103246 02-04 22:34:15.890 F /AgentCore:18066:18168/ Basic disk migration result 0x8103246 02-04 22:34:16.106 F /AgentCore:18066:18168/ Error : Current item migration failed with error 0x8103246
Snapapi module crucial for data transfer is not loaded during migration which leads to the failure.
This issue has been recognized as a bug with internal ID #PSBM-43856. It will be fixed in one of the future updates.
Meanwhile, workaround is available - it's necessary to load the kernel module manually (on a physical server side), and re-run the migration:
# modprobe snapapi26