Article ID: 124276, created on Jan 24, 2015, last review on Jan 24, 2015

  • Applies to:
  • Virtuozzo 6.0
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor


It is impossible to migrate container if it has bind mount configured for it.

Migration fails with the following error:

[root@pcs ~]# pmigrate c 100500 c --ssh="-p 22" root@<br>
Connection to destination node ( is successfully established<br>
Moving/copying CT#100500 -> CT#100500, [], [] ...<br>
vzctl2_env_get_param(QUOTAUGIDLIMIT) return 12000000<br>
Checking external bind mounts<br>
config ve contains ext bindmount: /mnt/100500/wincoa:/mnt/wincoa<br>
Can't move/copy CT#100500 -> CT#100500, [], [] : config ve contains ext bindmount:<br> /mnt/100500/wincoa:/mnt/wincoa 


This limitation is intentional, it is a product design which prevents actions that could be harmful.


There are two general cases for this situation:

  • If your destination server has the necessary bind-mount already configured you can ignore the warning and use --nodeps option for migration:

    # pmigrate <CTID> <IP.AD.DR.ES> --nodeps=bindmount

    Note!: you can use the same option for vzmigrate utility

  • If destination doesn't have the bind-mount point configured, and you do not intend to use it, you can remove the mount point using following command:

    # vzctl set <CTID> --bindmount_del <BIND_MOUNT> --save

    Once bind-mount is removed you can retry the migration.

Search Words


config ve contains ext bindmount

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f e8e50b42231236b82df27684e7ec0beb 0dd5b9380c7d4884d77587f3eb0fa8ef c62e8726973f80975db0531f1ed5c6a2

Email subscription for changes to this article
Save as PDF