[pve-devel] openvz vm migration bug?

Dietmar Maurer dietmar at proxmox.com
Fri Nov 1 15:39:25 CET 2013


> If one of this actions fail, it MUST be restored on current node.

At some point it is no longer possible to restore on current node.

> Now we can see something like this:
> 
> Nov 01 13:32:55 container is running - using online migration Nov 01 13:32:56
> starting rsync phase 1
> -----------
> Nov 01 13:34:18 start live migration - suspending container Nov 01 13:34:18
> dump container state Nov 01 13:34:18 copy dump file to target node Nov 01
> 13:34:20 starting rsync (2nd pass) Nov 01 13:34:20 dump 2nd level quota Nov 01
> 13:34:20 copy 2nd level quota to target node Nov 01 13:34:22 initialize
> container on remote node 'node2'
> Nov 01 13:34:22 initializing remote quota Nov 01 13:34:22 turn on remote quota
> Nov 01 13:34:22 load 2nd level quota Nov 01 13:34:22 starting container on
> remote node 'node2'
> Nov 01 13:34:22 restore container state
> Nov 01 13:34:23 Restoring container ...
> Nov 01 13:34:23 Starting container ...
> Nov 01 13:34:23 Container is mounted
> Nov 01 13:34:23 	undump...
> Nov 01 13:34:23 Setting CPU units: 1000
> Nov 01 13:34:23 Setting CPUs: 1
> Nov 01 13:34:23 Setting devices
> Nov 01 13:34:23 Error: undump failed: Cannot allocate memory Nov 01 13:34:23

You just do not have enough free memory on that node?



More information about the pve-devel mailing list