Did your machine continue to run successfully on the second machine ? Do you see something like this in the logs:
Jun 15 14:27:01 test4 CRON[2268]: PAM unable to dlopen(/lib/security/pam_unix.so) Jun 15 14:27:01 test4 CRON[2268]: PAM [dlerror: /lib/security/pam_unix.so: failed to map segment from shared object: Cannot allocate memory] Jun 15 14:27:01 test4 CRON[2268]: PAM adding faulty module: /lib/security/pam_unix.so Jun 15 14:27:01 test4 CRON[2268]: PAM unable to dlopen(/lib/security/pam_env.so) Jun 15 14:27:01 test4 CRON[2268]: PAM [dlerror: /lib/security/pam_env.so: failed to map segment from shared object: Cannot allocate memory] Jun 15 14:27:01 test4 CRON[2268]: PAM adding faulty module: /lib/security/pam_env.so Jun 15 14:27:01 test4 CRON[2268]: PAM unable to dlopen(/lib/security/pam_limits.so) Jun 15 14:27:01 test4 CRON[2268]: PAM [dlerror: /lib/security/pam_limits.so: failed to map segment from shared object: Cannot allocate memory] Jun 15 14:27:01 test4 CRON[2268]: PAM adding faulty module: /lib/security/pam_limits.so Jun 15 14:27:01 test4 CRON[2270]: PAM unable to dlopen(/lib/security/pam_unix.so) I had a problem with this procedure on Debian Lenny. http://bugzilla.openvz.org/show_bug.cgi?id=1292 If your machine is really stable can you describe your environment ? (Distribution, Kernel etc.) Regards, Robert > On chlivek3 I did this: > > > chlivek3:~# export VEID=233204 > > chlivek3:~# vzctl chkpnt $VEID --suspend Setting up checkpoint... > > suspend... > > get context... > > Checkpointing completed succesfully > > chlivek3:~# vzctl chkpnt $VEID --dump --dumpfile /tmp/$VEID > Setting up > > checkpoint... > > join context.. > > dump... > > Checkpointing completed succesfully > > chlivek3:~# vzctl chkpnt $VEID --kill > > Killing... > > chlivek3:~# vzlist -a > > CTID NPROC STATUS IP_ADDR HOSTNAME > > > 192002 11 running 192.168.1.2 dnetc > > > 233204 - mounted 195.113.233.204 mig.cesnet.cz > > > chlivek3:~# vzctl umount $VEID > > Container is unmounted > > chlivek3:~# vzlist -a > > CTID NPROC STATUS IP_ADDR HOSTNAME > > > 192002 11 running 192.168.1.2 dnetc > > > 233204 - stopped 195.113.233.204 mig.cesnet.cz > > chlivek3:~# umount /vz/private/$VEID > > 0n chlivek2 I did this: > > > chlivek2:~# mount LABEL=233204 /vz/private/233204/ chlivek2:~# scp > > r...@chlivek3:/tmp/233204 /tmp/ > > 233204 100% 1823KB > 1.8MB/s 00:00 > > chlivek2:~# ls -l /tmp/233204 > > -rw------- 1 root root 1866624 srp 10 17:33 /tmp/233204 chlivek2:~# > > vzctl restore 233204 --undump --dumpfile /tmp/233204 Restoring > > container ... > > Starting container ... > > Container is mounted > > undump... > > Adding IP address(es): 195.113.233.204 Setting CPU units: 1000 > > Configure meminfo: 65536 > > get context... > > Container start in progress... > > Restoring completed succesfully > > chlivek2:~# vzctl restore 233204 --resume Resuming... > > chlivek2:~# vzlist -a > > CTID NPROC STATUS IP_ADDR HOSTNAME > > > 192002 11 running 192.168.1.2 dnetc > > > 233204 8 running 195.113.233.204 mig.cesnet.cz > > > VE is up and working. After this I feel very powerful! ;) > _______________________________________________ Users mailing list [email protected] https://openvz.org/mailman/listinfo/users
