Difference between revisions of "Migration fails"
Botinki Kira (talk | contribs) m (Robot: Automated text replacement (-VE +container)) |
(→Solution) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
== Problem #1 == | == Problem #1 == | ||
| − | === | + | === Symptoms === |
After giving <tt>vzmigrate -v --online <ip address> <veid></tt> | After giving <tt>vzmigrate -v --online <ip address> <veid></tt> | ||
the following message appears: | the following message appears: | ||
| Line 19: | Line 19: | ||
=== Solution === | === Solution === | ||
Load all iptables kernel modules that are used by container on destination node. | 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. | ||
=== Links === | === Links === | ||
| Line 26: | Line 27: | ||
== Problem #2 == | == Problem #2 == | ||
| − | === | + | === Symptoms === |
The system runs <tt>028stab031</tt> or older kernels and | The system runs <tt>028stab031</tt> or older kernels and | ||
after giving <tt>vzmigrate -v --online <ip address> <veid></tt> | after giving <tt>vzmigrate -v --online <ip address> <veid></tt> | ||
| Line 56: | Line 57: | ||
== Problem #3 == | == Problem #3 == | ||
| − | === | + | === Symptoms === |
After giving <tt>vzmigrate -v --online <ip address> <veid></tt> | After giving <tt>vzmigrate -v --online <ip address> <veid></tt> | ||
the following message appears: | the following message appears: | ||
Latest revision as of 11:39, 7 May 2010
This article describes known reasons of migration failures, and solutions for those.
Contents
Problem #1[edit]
Symptoms[edit]
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[edit]
The container which you wish to migrate uses some iptables modules, that are not loaded on destination node. Consequently iptables-restore fails.
Solution[edit]
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.
Links[edit]
Problem #2[edit]
Symptoms[edit]
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[edit]
The container which you wish to migrate uses inotify mechanism (magic 0bad1dea), that is not supported by 028stab031 and older kernels.
Solution[edit]
- 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
Links[edit]
Problem #3[edit]
Symptoms[edit]
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[edit]
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[edit]
- 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
