Article ID: 2051, created on Jul 25, 2007, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo containers for Linux 4.7
  • Virtuozzo containers for Windows

Symptoms

VE migration of a specific VE fails with the following error:

C:\>vzmigrate -A 192.168.45.81 -U Administrator -P password 9991
connection adjust...
migrate 9991->9991
migration started
connect
get SSH keys
set SSH keys
prepare migration
close connection
Operation migrate with the VPS(s) VEID9991 Migration of the following VEs with VEIDs 9991 to 192.168.45.81 is started.
Processing stage CheckParameters
Operation migrate with the VPS(s) VEID9991 Migration of the following VEs with VEIDs 9991 to 192.168.45.81 is finished with errors: #3404 V2V migration failed : SWAHaulControlOperator with id 'vzmigrate\_v2v\_serializer' stage 'CheckParameters' failed : Virtuozzo API function call 'VZVolumeMount' failed err = 183.
migration error 0xd4c V2V migration failed : SWAHaulControlOperator with id 'vzmigrate\_v2v\_serializer' stage 'CheckParameters' failed : Virtuozzo API function call 'VZVolumeMount' failed err = 183
migration finished

Cause

Error code 183 means that VE with the same GUID already exists on the destination node. Such situation could occur if the same VE was restored from backup with different ID or it had been migrated earlier and ID has been changed then.

Resolution

As a workaround the VE can simply be cloned – GUID will be changed in this case – and then migration of the cloned VE will be possible.

d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 965b49118115a610e93635d21c5694a8 e8e50b42231236b82df27684e7ec0beb 0c05f0c76fec3dd785e9feafce1099a9

Email subscription for changes to this article
Save as PDF