Migration fails

From OpenVZ Linux Containers Wiki

Jump to: navigation, search

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

Contents

[edit] Problem #1

[edit] 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

[edit] Reason

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

[edit] Solution

Load all iptables kernel modules that are used by container on destination node. Also, it seems like iptables needs to be installed inside the container.

[edit] Links

[edit] Problem #2

[edit] 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

[edit] Reason

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

[edit] Solution

[edit] Links


[edit] Problem #3

[edit] 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

[edit] 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.

[edit] Solution

[edit] Links

Personal tools
Namespaces
Variants
Actions
Navigation
Sites
Toolbox