Changes
→Solution
== Problem #1 ==
=== Symptoms ===
After giving <tt>vzmigrate -v --online <ip address> <veid></tt>
the following message appears:
<pre>
Error: undump failed: Invalid argumentStopping VE argumentStopping container ...
Restoring failed:
iptables-restore exited with 1
=== Reason ===
The VE 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 container on destination node.Also, it seems like iptables needs to be installed inside the container.
=== Links ===
== Problem #2 ==
=== Symptoms ===
The system runs <tt>028stab031</tt> or older kernels and
after giving <tt>vzmigrate -v --online <ip address> <veid></tt>
the following message appears:
<pre>
Live migrating VEcontainer Suspending VEcontainer
Setting up checkpoint...
suspend...
Can not suspend VEcontainer: Device or resource busy
file on unsupported FS: magic 0bad1dea
Checkpointing failed
Error: Failed to suspend VEcontainer
</pre>
=== Reason ===
The VE container which you wish to migrate uses inotify mechanism (magic 0bad1dea), that is not
supported by <tt>028stab031</tt> and older kernels.
== Problem #3 ==
=== Symptoms ===
After giving <tt>vzmigrate -v --online <ip address> <veid></tt>
the following message appears:
<pre>
Dumping VEcontainer
Setting up checkpoint...
join context..
dump...
Can not dump VEcontainer: Device or resource busy
unsupported netdevice tun0
Checkpointing failed
Error: Failed to dump VEcontainer
</pre>
=== Reason ===
Checkpointing doesn't support <tt>tun</tt> device inside VE 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 VEcontainer.
=== Solution ===