Editing Migration fails

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
This article describes known reasons of migration failures, and solutions for those.
+
This article contents known reasons of migration failures.
  
 
== Problem #1 ==
 
== Problem #1 ==
=== Symptoms ===
+
=== 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:
 
<pre>
 
<pre>
Error: undump failed: Invalid argument
+
Error: undump failed: Invalid argumentStopping VE ...
Stopping container ...
 
 
Restoring failed:
 
Restoring failed:
 
iptables-restore exited with 1
 
iptables-restore exited with 1
Line 14: Line 13:
  
 
=== Reason ===
 
=== Reason ===
The container which you wish to migrate uses some iptables modules, that are not
+
The VE which you wish to migrate uses some iptables modules, that are not
 
loaded on destination node. Consequently <tt>iptables-restore</tt> fails.
 
loaded on destination node. Consequently <tt>iptables-restore</tt> fails.
  
=== Solution ===
+
=== Workaround ===
Load all iptables kernel modules that are used by container on destination node.
+
Load all iptables kernel modules that are used by VE on destination node.
Also, it seems like iptables needs to be installed inside the container.
 
  
 
=== Links ===
 
=== Links ===
  
* {{bug|631}}
+
* http://bugzilla.openvz.org/show_bug.cgi?id=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=
  
 
== Problem #2 ==
 
== Problem #2 ==
=== Symptoms ===
+
=== 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>
 
the following message appears:
 
the following message appears:
 
<pre>
 
<pre>
Live migrating container
+
Live migrating VE
     Suspending container
+
     Suspending VE
 
Setting up checkpoint...
 
Setting up checkpoint...
 
         suspend...
 
         suspend...
Can not suspend container: Device or resource busy
+
Can not suspend VE: Device or resource busy
 
file on unsupported FS: magic 0bad1dea
 
file on unsupported FS: magic 0bad1dea
 
Checkpointing failed
 
Checkpointing failed
Error:  Failed to suspend container
+
Error:  Failed to suspend VE
 
</pre>
 
</pre>
  
 
=== Reason ===
 
=== Reason ===
The container which you wish to migrate uses inotify mechanism (magic 0bad1dea), that is not
+
The VE which you wish to migrate uses inotify mechanism (magic 0bad1dea), that is not
 
supported by <tt>028stab031</tt> and older kernels.
 
supported by <tt>028stab031</tt> and older kernels.
  
=== Solution ===
+
=== Workaround ===
 
* 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 52: Line 50:
 
=== Links ===
 
=== Links ===
  
* {{bug|552}}
+
* http://bugzilla.openvz.org/show_bug.cgi?id=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
  
  
 
== Problem #3 ==
 
== Problem #3 ==
=== Symptoms ===
+
=== 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:
 
<pre>
 
<pre>
Dumping container
+
Dumping VE
 
Setting up checkpoint...
 
Setting up checkpoint...
 
         join context..
 
         join context..
 
         dump...
 
         dump...
Can not dump container: Device or resource busy
+
Can not dump VE: Device or resource busy
 
unsupported netdevice tun0
 
unsupported netdevice tun0
 
Checkpointing failed
 
Checkpointing failed
Error:  Failed to dump container
+
Error:  Failed to dump VE
 
</pre>
 
</pre>
  
 
=== Reason ===
 
=== Reason ===
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.
+
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 ===
+
=== Workaround ===
* for 2.6.18 based kernels: update till <tt>028stab049</tt> or newer kernel
+
Just use 2.6.18-028stab049 or 2.6.9-023stab044.14 (and later) OpenVZ kernels.
* for 2.6.9 based kernels: update till <tt>023stab044.14</tt> or newer kernel
 
  
 
=== Links ===
 
=== Links ===
* {{Bug|642}}
+
* http://bugzilla.openvz.org/show_bug.cgi?id=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]]

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Template used on this page: