Open main menu

OpenVZ Virtuozzo Containers Wiki β

Migration fails

Revision as of 11:37, 7 May 2010 by 143.205.116.240 (talk) (Solution)

This article describes known reasons of migration failures, and solutions for those.

Contents

Problem #1

Symptoms

After giving vzmigrate -v --online <ip address> <veid> the following message appears:

Error: undump failed: Invalid argument
Stopping container ...
Restoring failed:
iptables-restore exited with 1
rst_restore_net: -22

Reason

The container which you wish to migrate uses some iptables modules, that are not loaded on destination node. Consequently iptables-restore fails.

Solution

Load all iptables kernel modules that are used by container on destination node.

Links

Problem #2

Symptoms

The system runs 028stab031 or older kernels and after giving vzmigrate -v --online <ip address> <veid> the following message appears:

Live migrating container
    Suspending container
Setting up checkpoint...
        suspend...
Can not suspend container: Device or resource busy
file on unsupported FS: magic 0bad1dea
Checkpointing failed
Error:  Failed to suspend container

Reason

The container which you wish to migrate uses inotify mechanism (magic 0bad1dea), that is not supported by 028stab031 and older kernels.

Solution

  • for 2.6.18 rhel5 based kernels: Update till 028stab035 or newer kernel
  • for 2.6.18 mainstream based kernels: Update till 028stab043 or newer kernel
  • I had this problem when iptables was not installed in the guest, aptitude install iptables resolved it.

Links


Problem #3

Symptoms

After giving vzmigrate -v --online <ip address> <veid> the following message appears:

Dumping container
Setting up checkpoint...
        join context..
        dump...
Can not dump container: Device or resource busy
unsupported netdevice tun0
Checkpointing failed
Error:  Failed to dump container

Reason

Checkpointing doesn't support tun device inside container till 2.6.18-028stab049 and 2.6.9-023stab044.14 kernels. This device is usually used for VPN via the TUN/TAP device in container.

Solution

  • for 2.6.18 based kernels: update till 028stab049 or newer kernel
  • for 2.6.9 based kernels: update till 023stab044.14 or newer kernel

Links