Migration Restrictions for Containers

Listed below are the limitations you should take into account when migrating physical computers to Containers.

• If the source physical computer has several IP addresses assigned to it, all of those are reassigned to the same venet0 device on the destination host. This virtual network adapter is used to interconnect all Containers on a host and the server itself. After migration, you can create additional virtual network adapters inside the resulting Container and assign necessary IP addresses to network adapters as you see fit. For more details, see Managing Adapters in Containers.
• During migration, you may specify only one partition on the source physical computer that will be migrated to a Container together with all its quotas. All other partitions will be copied without their quota limits. Moreover, the quota limits of the selected partition will be applied to the entire Container after migration.
• While migrating a physical server running a Linux operating system with a security-enhanced (SE) Linux kernel, keep in mind that Virtuozzo currently does not support SE Linux kernels, and the resulting Container will not support the SE features of the source.
• If any of your files and/or directories on the source physical computer have extended attributes associated with them, these attributes will be lost after migration.
• Raw devices on the source physical computer cannot and will not be migrated to the resulting Container on the destination host.
• Any applications bound to the MAC address of the source physical computer will not run inside the resulting Container after migration. In this case, you can do one of the following:
  • Obtain new licenses for applications that require them and install those anew inside the Container.
  • Try to reconfigure applications which do not require a license for working without being bound to a MAC address.
• If migration fails at a stage when rsync is transferring files and directories from the source physical computer to the resulting Container, the already copied files and directories will remain in the /vz/private/<CT_ID> directory on the destination host, probably occupying much disk space. You can keep this directory to speed up a new migration attempt, or you can delete it manually by using the rm utility.
• Migrating physical computers with system volumes formatted as ReiserFS is not supported.
• Migration of GUID Partition Table (GPT) disks is not supported.