Migration of a Virtual Machine fails with the following error:
Unable to migrate because the image file used by its device is stored outside the virtual machine bundle.
if path to device is different from the
Home folder even if it's a symlink to the same location you'll face issues during migration. Example of configuration that will cause issues:
# ls -l /vz/vmprivate lrwxrwxrwx 1 root root 14 Sep 17 2013 /vz/vmprivate -> /var/parallels # prlctl list vm2 -i | egrep '^Home|hdd' | grep -v order Home: /var/parallels/vm2.pvm/ hdd0 (+) sata:0 image='/var/parallels/vm2.pvm/harddisk.hdd' 65536Mb hdd1 (+) sata:2 image='/vz/vmprivate/vm2.pvm/harddisk1.hdd' 4096Mb
On the output above you can see that hdd1 was added to the VM using a symlink instead of
In that scenario migration from PSBM 5 would fail, and migration from PCS 6 will silently disconnect hdd with "external" path.
This behavior is confirmed as a bug with internal ID #PSBM-24811.
This bug will be fixed in one of the future updates.
For now you may use workaround - to change the paths such hdds so they match
Stop the virtual machine
# prlctl stop vm2
Reconfigure "external" hdd:
# prlctl set vm2 --device-set hdd1 --image '/var/parallels/vm2.pvm/harddisk1.hdd'
Start the Virtual Machine
# prlctl stat vm2
- Complete migration
NOTE: for PCS 6 it will be necessary to migrate VM back to the source node, or to move "external" hdd manually to destination node and register it anew.