User`s guide
Operations on Virtual Machines and Containers 62
Non-NTFS volumes cannot be migrated.
After the physical server migration, the Quality of Service packet scheduler is disabled
inside the Container irrespective of its state on the server before the migration began.
You cannot migrate physical servers running the 32-bit version of Windows Server to
destination servers running the 64-bit version of Parallels Containers, neither can you move
physical servers running the 64-bit version of Windows Server to servers running the 32-bit
version of Parallels Containers.
Requirements for Migrating to Virtual Machines
Any physical computer that you plan to migrate to a virtual machine must have the Parallels
agent installed. The agent can be installed on computers meeting the following requirements.
Hardware Requirements
700 (or higher) MHz x86 or x64 processor (Intel or AMD).
256 MB or more RAM.
50 MB of hard disk space for installing the Parallels agent package.
Ethernet or WiFi network adapter.
Software Requirements
For software requirements, see the table in General Migration Requirements (p. 50).
Additional Requirements for Migrating Servers with Parallels Server Bare Metal
If you plan to migrate a server running the Parallels Server Bare Metal software, you should first
make sure that the snapapi26 and snumbd26 modules are not loaded on the server. You can
use the following command to check this:
# lsmod | grep snapapi26
# lsmod | grep snumbd26
If any of these modules are loaded, unload them by running the rmmod command. If the rmmod
command fails to unload any of these modules, do the following:
1 Stop the Parallels Server Bare Metal service:
# /etc/init.d/vz stop
2 Unload the modules:
# rmmod snapapi26
# rmmod snumbd26
3 Start the Parallels Server Bare Metal service again:
# /etc/init.d/vz start
Once the modules are unloaded, proceed with migrating the server.
Notes:
1. Migrating Windows dynamic volumes and Linux logical volumes (LVM) is not supported.
2. You may also try to migrate servers with unsupported file systems. However, in this case all
disk sectors are copied successively, and you may experience problems with using the resulting
virtual machine.










