vzmigrate fails

xelkano

New Member
May 24, 2011
14
0
1
Hello,

I have an issue with vzmigrate in proxmox 1.8 doing an online migration:

Code:
/bin/sh /usr/sbin/vzmigrate -v --online XX.XX.XX.XX 101

Starting online migration of CT 101 to XX.XX.XX.XX
OpenVZ is running...
   Loading /etc/vz/vz.conf and /etc/vz/conf/101.conf files
   Check IPs on destination node: XX.XX.XX.XX
Preparing remote node
   Copying config file
101.conf                                                                                                                   100% 1616     1.6KB/s   00:00    
Saved parameters for CT 101
   Creating remote container root dir
   Creating remote container private dir
Initializing remote quota
   Quota init
   Turning remote quota on
Syncing private
Live migrating container...
   Suspending container
Setting up checkpoint...
    suspend...
    get context...
Checkpointing completed succesfully
   Dumping container
Setting up checkpoint...
    join context..
    dump...
Can not dump container: Invalid argument
Error: unknown inode mode 0, magic 0x9041934
Checkpointing failed
Error: Failed to dump container
Resuming...
If I try to make a checkpoint:

# vzctl chkpnt 101
Setting up checkpoint...
suspend...
dump...
Can not dump container: Invalid argument
Error: unknown inode mode 0, magic 0x9041934
Checkpointing failed

PVE versions:

Code:
ii  libpve-storage-perl               1.0-17                     Proxmox VE storage management library
ii  pve-firmware                      1.0-11                     Binary firmware code for the pve-kernel
ii  pve-kernel-2.6.32-4-pve           2.6.32-33                  The Proxmox PVE Kernel Image
ii  pve-manager                       1.8-17                     The Proxmox Virtual Environment
ii  pve-qemu-kvm                      0.14.0-3                   Full virtualization on x86 hardware
ii  vzctl                             3.0.26-1pve4               OpenVZ - server virtualization solution - co
Proxmox installation was with Bare-metal ISO Installer.

Thank you very much for your help.
 
Thanks for your fast reply!

Is possible to see somewhere current bugs on 2.6.32 kernel branch?

Best regards.
 
Hi,

i am on 2.6.18-6 on our productive server. When i will migrate a machine i get an error:

Code:
/usr/bin/ssh -t -t -n -o BatchMode=yes 192.168.1.3 /usr/sbin/vzmigrate --online 192.168.1.2 211
Starting online migration of CT 211 to 192.168.1.2
Preparing remote node
Initializing remote quota
Syncing private
Live migrating container...
Syncing 2nd level quota
Error: Failed to undump container
vzquota : (error) Quota is not running for id 211
Connection to 192.168.1.3 closed.
VM 211 migration failed -

and a other machine

Code:
/usr/bin/ssh -t -t -n -o BatchMode=yes 192.168.1.3 /usr/sbin/vzmigrate --online 192.168.1.2 110
Starting online migration of CT 110 to 192.168.1.2 
Preparing remote node 
Initializing remote quota 
Syncing private 
Live migrating container... 
Error: Failed to dump container 
Connection to 192.168.1.3 closed. 
VM 110 migration failed -

Whats wrong?

Regards, Valle
 
Last edited:
Hi Dietmar,

i hope this helps to find the bug(?)

Code:
proxmox02:~# vzmigrate --online --remove-area yes -v 192.168.1.2 211
Starting online migration of CT 211 to 192.168.1.2
OpenVZ is running...
   Loading /etc/vz/vz.conf and /etc/vz/conf/211.conf files
   Check IPs on destination node: 
Preparing remote node
   Copying config file
211.conf                                                                                                                                                                                                                                    No changes in CT configuration, not saving
   Creating remote container root dir
   Creating remote container private dir
Initializing remote quota
   Quota init
   Turning remote quota on
Syncing private
Live migrating container...
   Suspending container
Setting up checkpoint...
    suspend...
    get context...
Checkpointing completed succesfully
   Dumping container
Setting up checkpoint...
    join context..
    dump...
Checkpointing completed succesfully
   Copying dumpfile
dump.211                                                                                                                                                                                                                                       Syncing private (2nd pass)
Syncing 2nd level quota
   Dumping 2nd level quota
   Copying 2nd level quota
quotadump.211                                                                                                                                                                                                                                  Load 2nd level quota
   Undumping container
Restoring container ...
Starting container ...
vzquota : (warning) Quota is running for id 211 already
Container is mounted
    undump...
Setting CPU units: 1000
Setting CPUs: 1
Configure veth devices: veth211.0 veth211.1 
Adding interface veth211.0 to bridge vmbr0 on CT0 for CT211
Adding interface veth211.1 to bridge vmbr1 on CT0 for CT211
Error: undump failed: Bad address
Restoring failed:
Error: AF_PACKET binding failed: -22
Error: AF_PACKET binding failed: -22
Error: do_rst_mm 65112760
Error: rst_mm: -14
Error: make_baby: -14
Error: rst_clone_children
Error: make_baby: -14
Error: rst_clone_children
Error: make_baby: -14
Error: rst_clone_children
Container start failed
Stopping container ...
Container was stopped
Container is unmounted
Error: Failed to undump container
Resuming...
vzquota : (error) Quota is not running for id 211

Regards, Valle
 
Yesterday i have upgraded both productive server to proxmox 1.9. I downloaded a new debian template debian-6.0-standard_6.0-4_i386.tar.gz and testes the openvz online migration but it fails :(

Does openvz online migration realy work? It have never worked for me :(

Code:
proxmox02:~# vzmigrate --online -r yes -v 192.168.1.2 115
Starting online migration of CT 115 to 192.168.1.2
OpenVZ is running...
   Loading /etc/vz/vz.conf and /etc/vz/conf/115.conf files
   Check IPs on destination node: 192.168.1.81
Preparing remote node
   Copying config file
115.conf                                                                                    100% 1399     1.4KB/s   00:00
No changes in CT configuration, not saving
   Creating remote container root dir
   Creating remote container private dir
Initializing remote quota
   Quota init
   Turning remote quota on
Syncing private
Live migrating container...
   Suspending container
Setting up checkpoint...
        suspend...
        get context...
Checkpointing completed succesfully
   Dumping container
Setting up checkpoint...
        join context..
        dump...
Checkpointing completed succesfully
   Copying dumpfile
dump.115                                                                                    100%  169MB  56.3MB/s   00:03
   Syncing private (2nd pass)
Syncing 2nd level quota
   Dumping 2nd level quota
   Copying 2nd level quota
quotadump.115                                                                               100%   21     0.0KB/s   00:00
   Load 2nd level quota
   Undumping container
Restoring container ...
Starting container ...
vzquota : (warning) Quota is running for id 115 already
Container is mounted
        undump...
Adding IP address(es): 192.168.1.81
Setting CPU units: 1000
Setting CPUs: 1
Error: undump failed: Cannot allocate memory
Restoring failed:
Error: do_rst_mm 45118736
Error: rst_mm: -12
Error: make_baby: -12
Error: rst_clone_children
Stopping container ...
Container start failed
Container was stopped
Container is unmounted
Error: Failed to undump container
Resuming...
vzquota : (error) Quota is not running for id 115

Machine 1:
Code:
proxmox01:~# pveversion -v
pve-manager: 1.9-24 (pve-manager/1.9/6542)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-43
pve-kernel-2.6.32-6-pve: 2.6.32-43
qemu-server: 1.1-32
pve-firmware: 1.0-13
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.28-1pve5
vzdump: 1.2-15
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6

Machine 2:
Code:
proxmox02:~# pveversion -v
pve-manager: 1.9-24 (pve-manager/1.9/6542)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-43
pve-kernel-2.6.32-6-pve: 2.6.32-43
qemu-server: 1.1-32
pve-firmware: 1.0-13
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.28-1pve5
vzdump: 1.2-15
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6

Regards, Valle
 
Hi Dietmar,

thanx, that works. Why INITLOG=yes is default on? I have switched it off in a old configuration. A Update override my settings and switched the parameter to yes.

Regards and big thanx,

Valle
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!