Migration fails - Revision history

143.205.116.240: /* Solution */

2010-05-07T11:39:19Z

‎Solution

143.205.116.240: /* Solution */

2010-05-07T11:38:12Z

‎Solution

143.205.116.240: /* Solution */

2010-05-07T11:37:33Z

‎Solution

Botinki Kira: Robot: Cosmetic changes

2008-03-19T07:13:33Z

Robot: Cosmetic changes

Botinki Kira: Robot: Automated text replacement (-VE +container)

2008-03-11T12:04:05Z

Robot: Automated text replacement (-VE +container)

Kir: /* Symptoms */ break lines

2008-03-11T10:59:23Z

‎Symptoms: break lines

Kir: solution not workaround!

2007-12-14T15:02:02Z

solution not workaround!

Vass: /* Workaround */ formatting fix

2007-12-02T22:08:01Z

‎Workaround: formatting fix

Vass: /* Reason */ formatting fix

2007-12-02T22:06:02Z

‎Reason: formatting fix

Vass: /* Workaround */ TUN is now supported.

2007-12-02T22:04:09Z

‎Workaround: TUN is now supported.

@@ Line 19: / Line 19: @@
 === Solution ===
 Load all iptables kernel modules that are used by container on destination node.
 === Links ===

@@ Line 48: / Line 48: @@
 * 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
 === Links ===

@@ Line 48: / Line 48: @@
 * 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
 === Links ===

@@ Line 2: / Line 2: @@
 == Problem #1 ==
-===  Symptoms ===
+=== Symptoms ===
 After giving <tt>vzmigrate -v --online <ip address> <veid></tt>
 the following message appears:
@@ Line 26: / Line 26: @@
 == Problem #2 ==
-===  Symptoms ===
+=== Symptoms ===
 The system runs <tt>028stab031</tt> or older kernels and
 after giving <tt>vzmigrate -v --online <ip address> <veid></tt>
@@ Line 56: / Line 56: @@
 == Problem #3 ==
-===  Symptoms ===
+=== Symptoms ===
 After giving <tt>vzmigrate -v --online <ip address> <veid></tt>
 the following message appears:

@@ Line 7: / Line 7: @@
 <pre>
 Error: undump failed: Invalid argument
-Stopping VE ...
+Stopping container ...
 Restoring failed:
 iptables-restore exited with 1
@@ Line 14: / Line 14: @@
 === Reason ===
-The VE which you wish to migrate uses some iptables modules, that are not
+The container which you wish to migrate uses some iptables modules, that are not
 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 container on destination node.
 === Links ===
@@ Line 31: / Line 31: @@
 the following message appears:
 <pre>
-Live migrating VE
+Live migrating container
-     Suspending VE
+     Suspending container
 Setting up checkpoint...
          suspend...
-Can not suspend VE: Device or resource busy
+Can not suspend container: Device or resource busy
 file on unsupported FS: magic 0bad1dea
 Checkpointing failed
-Error:  Failed to suspend VE
+Error:  Failed to suspend container
 </pre>
 === Reason ===
-The VE which you wish to migrate uses inotify mechanism (magic 0bad1dea), that is not
+The container which you wish to migrate uses inotify mechanism (magic 0bad1dea), that is not
 supported by <tt>028stab031</tt> and older kernels.
@@ Line 60: / Line 60: @@
 the following message appears:
 <pre>
-Dumping VE
+Dumping container
 Setting up checkpoint...
          join context..
          dump...
-Can not dump VE: Device or resource busy
+Can not dump container: Device or resource busy
 unsupported netdevice tun0
 Checkpointing failed
-Error:  Failed to dump VE
+Error:  Failed to dump container
 </pre>
 === Reason ===
-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 container 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 container.
 === Solution ===

@@ Line 1: / Line 1: @@
-This article contents known reasons of migration failures.
+This article describes known reasons of migration failures, and solutions for those.
 == Problem #1 ==
@@ Line 16: / Line 16: @@
 loaded on destination node. Consequently <tt>iptables-restore</tt> fails.
-=== Workaround ===
+=== Solution ===
 Load all iptables kernel modules that are used by VE on destination node.
 === Links ===
-* http://bugzilla.openvz.org/show_bug.cgi?id=631
+* {{bug|631}}
 * 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.
-=== Workaround ===
+=== Solution ===
 * 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
@@ Line 50: / Line 50: @@
 === Links ===
-* http://bugzilla.openvz.org/show_bug.cgi?id=552
+* {{bug|552}}
 * 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.
-=== Workaround ===
+=== Solution ===
 * 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
 === Links ===
-* http://bugzilla.openvz.org/show_bug.cgi?id=642
+* {{Bug|642}}
 * http://forum.openvz.org/index.php?t=tree&goto=14826&#msg_14826
 [[Category:Troubleshooting]]

@@ Line 74: / Line 74: @@
 === Workaround ===
-You should not use <tt>tun</tt> device in VE to migrate  it. If you're using VPN in VE, just stop VPN, then produce the online migration and after that start the VPN. Of course, all current connections to VPN will be lost :(.
+Just use 2.6.18-028stab049 or 2.6.9-023stab044.14 (and later) OpenVZ kernels.
 === Links ===