Hi,
We are testing Proxmox and are fairly impressed with the functionality and usibility. However, we are expreciencing problems with the OpenVZ online migration feature.
Our test setup consists of two Dell PowerEdge 1850's (therefore, KVM functionality isn't available on these machines). Both installations run Proxmox 1.2 (the master was upgraded from 1.1, the node is a clean 1.2 install) and thus are running kernel 2.6.24-5-pve. Both have two NIC's in a bridged configuration (no idea if that is relevant or not).
When attempting an online migration of a CentOS 5.3 container from the master to the node - or the other way around - via de Proxmox GUI, we get the following output:
/usr/sbin/vzmigrate --online 192.168.12.161 104
OPT:--online
OPT:192.168.12.161
Starting online migration of CT 104 to 192.168.12.161
Preparing remote node
Initializing remote quota
Syncing private
Live migrating container...
Error: Failed to dump container
VM 104 migration failed -
When we enter the following command in the terminal:
/usr/sbin/vzmigrate -v --online 192.168.12.161 104
We get the following output:
OPT:-v
OPT:--online
OPT:192.168.12.161
Starting online migration of CT 104 to 192.168.12.161
OpenVZ is running...
Loading /etc/vz/vz.conf and /etc/vz/conf/104.conf files
Check IPs on destination node: 192.168.12.170
Preparing remote node
Copying config file
104.conf 100% 1404 1.4KB/s 00:00
Saved parameters for CT 104
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: d_path is invisible /dev/ptyp0
Checkpointing failed
Error: Failed to dump container
Resuming...
When we try to do an online migration of a Ubuntu 8.10 container, we get almost the same output, except for:
Error: d_path cannot be looked up /dev/ptyp0
Migrations without the online option work flawlessly, but of course, that results in downtime of about 10 seconds.
Is this a general problem with OpenVZ/Kernel 2.6.24-5-pve/Proxmox 1.2, or is this something only we are experiencing? And if so, does anyone know a fix?
Thanks in advance for your help!
We are testing Proxmox and are fairly impressed with the functionality and usibility. However, we are expreciencing problems with the OpenVZ online migration feature.
Our test setup consists of two Dell PowerEdge 1850's (therefore, KVM functionality isn't available on these machines). Both installations run Proxmox 1.2 (the master was upgraded from 1.1, the node is a clean 1.2 install) and thus are running kernel 2.6.24-5-pve. Both have two NIC's in a bridged configuration (no idea if that is relevant or not).
When attempting an online migration of a CentOS 5.3 container from the master to the node - or the other way around - via de Proxmox GUI, we get the following output:
/usr/sbin/vzmigrate --online 192.168.12.161 104
OPT:--online
OPT:192.168.12.161
Starting online migration of CT 104 to 192.168.12.161
Preparing remote node
Initializing remote quota
Syncing private
Live migrating container...
Error: Failed to dump container
VM 104 migration failed -
When we enter the following command in the terminal:
/usr/sbin/vzmigrate -v --online 192.168.12.161 104
We get the following output:
OPT:-v
OPT:--online
OPT:192.168.12.161
Starting online migration of CT 104 to 192.168.12.161
OpenVZ is running...
Loading /etc/vz/vz.conf and /etc/vz/conf/104.conf files
Check IPs on destination node: 192.168.12.170
Preparing remote node
Copying config file
104.conf 100% 1404 1.4KB/s 00:00
Saved parameters for CT 104
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: d_path is invisible /dev/ptyp0
Checkpointing failed
Error: Failed to dump container
Resuming...
When we try to do an online migration of a Ubuntu 8.10 container, we get almost the same output, except for:
Error: d_path cannot be looked up /dev/ptyp0
Migrations without the online option work flawlessly, but of course, that results in downtime of about 10 seconds.
Is this a general problem with OpenVZ/Kernel 2.6.24-5-pve/Proxmox 1.2, or is this something only we are experiencing? And if so, does anyone know a fix?
Thanks in advance for your help!