Difference between revisions of "Migration fails"
m (→Workaround: formatting fix) |
(solution not workaround!) |
||
| Line 1: | Line 1: | ||
| − | This article | + | This article describes known reasons of migration failures, and solutions for those. |
== Problem #1 == | == Problem #1 == | ||
| Line 16: | Line 16: | ||
loaded on destination node. Consequently <tt>iptables-restore</tt> fails. | loaded on destination node. Consequently <tt>iptables-restore</tt> fails. | ||
| − | === | + | === Solution === |
Load all iptables kernel modules that are used by VE on destination node. | Load all iptables kernel modules that are used by VE on destination node. | ||
=== Links === | === Links === | ||
| − | * | + | * {{bug|631}} |
* http://forum.openvz.org/index.php?t=tree&th=2756&mid=14198&&rev=&reveal= | * http://forum.openvz.org/index.php?t=tree&th=2756&mid=14198&&rev=&reveal= | ||
| Line 44: | Line 44: | ||
supported by <tt>028stab031</tt> and older kernels. | supported by <tt>028stab031</tt> and older kernels. | ||
| − | === | + | === Solution === |
* for 2.6.18 rhel5 based kernels: Update till <tt>028stab035</tt> or newer kernel | * for 2.6.18 rhel5 based kernels: Update till <tt>028stab035</tt> or newer kernel | ||
* for 2.6.18 mainstream based kernels: Update till <tt>028stab043</tt> or newer kernel | * for 2.6.18 mainstream based kernels: Update till <tt>028stab043</tt> or newer kernel | ||
| Line 50: | Line 50: | ||
=== Links === | === Links === | ||
| − | * | + | * {{bug|552}} |
* http://forum.openvz.org/index.php?t=tree&goto=14780&#msg_14780 | * http://forum.openvz.org/index.php?t=tree&goto=14780&#msg_14780 | ||
| Line 72: | Line 72: | ||
Checkpointing doesn't support <tt>tun</tt> device inside VE till <tt>2.6.18-028stab049</tt> and <tt>2.6.9-023stab044.14</tt> kernels. This device is usually used for [[VPN via the TUN/TAP device]] in VE. | Checkpointing doesn't support <tt>tun</tt> device inside VE till <tt>2.6.18-028stab049</tt> and <tt>2.6.9-023stab044.14</tt> kernels. This device is usually used for [[VPN via the TUN/TAP device]] in VE. | ||
| − | === | + | === Solution === |
* for 2.6.18 based kernels: update till <tt>028stab049</tt> or newer kernel | * for 2.6.18 based kernels: update till <tt>028stab049</tt> or newer kernel | ||
* for 2.6.9 based kernels: update till <tt>023stab044.14</tt> or newer kernel | * for 2.6.9 based kernels: update till <tt>023stab044.14</tt> or newer kernel | ||
=== Links === | === Links === | ||
| − | * | + | * {{Bug|642}} |
* http://forum.openvz.org/index.php?t=tree&goto=14826&#msg_14826 | * http://forum.openvz.org/index.php?t=tree&goto=14826&#msg_14826 | ||
[[Category:Troubleshooting]] | [[Category:Troubleshooting]] | ||
Revision as of 15:02, 14 December 2007
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 argumentStopping VE ... Restoring failed: iptables-restore exited with 1 rst_restore_net: -22
Reason
The VE 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 VE 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 VE
Suspending VE
Setting up checkpoint...
suspend...
Can not suspend VE: Device or resource busy
file on unsupported FS: magic 0bad1dea
Checkpointing failed
Error: Failed to suspend VE
Reason
The VE 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
Links
Problem #3
Symptoms
After giving vzmigrate -v --online <ip address> <veid> the following message appears:
Dumping VE
Setting up checkpoint...
join context..
dump...
Can not dump VE: Device or resource busy
unsupported netdevice tun0
Checkpointing failed
Error: Failed to dump VE
Reason
Checkpointing doesn't support tun device inside VE 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 VE.
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
