On Sat, May 23, 2009 at 11:36:15AM +0900, [email protected] wrote: > Hello Josiney, > > Josiney de Souza: > > r...@vcg:~# vzctl chkpnt 104 dumpfile dump.104 > > Setting up checkpoint... > > suspend... > > dump... > > Can not dump container: Invalid argument > > Error: pg->mapping!=f_mapping: 08048000 c0c37b60 dfaa9e84 43824 > > Error: dump_one_vma: funkey page > > Checkpointing failed > > r...@vcg:~# > > --- > > > > My system is Debian Lenny and vzctl package version is 3.0.23-1dso1. > > I build my kernel from 2.6.27 sources, following steps in AUFS page and > > applying the kernel patch 2.6.27-briullov.1-combined . > > > > Checkpointing from a local filesystem root (ReiserFS) or NFS filesystem root > > works, but not from AUFS root. > > Although I could not fully understand what your environment is, > please try this patch.
Sorry about the first text, I will try to explain better now. =) First, we have the OpenVZ (http://wiki.openvz.org/Main_Page), a virtualization solution. With OpenVZ, we can freeze a virtual machine suspending and dumping all VM context to a file (called checkpoint). This dump file is used to restore context later. Originally, all the files of a virtual machine (also called VE - Virtual Environment) is placed in /var/lib/vz/private/NUM_VE, where NUM_VE is the number identifier of a VE. On the last e-mail, NUM_VE was 104 according my example. In my case, I will not use the local filesystem as VE root, but I will mount this VE root with AUFS. Before this, I have two NFS filesystems that will be branchs of AUFS: one as RO+WH and other as RW, as shown in my /etc/fstab. --- 200.17.202.224:/raizes/openvz-etch /media/openvz-etch nfs ro,defaults,tcp,noauto 0 0 200.17.202.224:/raizes/adicional/heavyarms /media/heavyarms nfs rw,defaults,tcp,noauto 0 0 aufsroot /var/lib/vz/private/104 aufs br:/media/heavyarms=rw:/media/openvz-etch=ro+wh,noauto 0 0 --- Unfortunately, this new VE root does not work for checkpointing a VM context, showing that error. But, when I transform VE root only in a NFS filesystem or when I use the local filesystem as VE root, everything works fine. Did you see shomething like that before? Or have any idea what I'm doing wrong? > Or give me the full instruction to reproduce the problem. > Reproduce the problem is a kind boring, because have a lot of steps to be followed. They are: 1- Download kernel 2.6.27 source files 2- Apply the kernel patch in http://wiki.openvz.org/Download/kernel/2.6.27/2.6.27-briullov.1 3- Add AUFS source files in this new kernel tree NOTE: these steps are for give the AUFS and the OpenVZ access 5- Follow the OpenVZ Quick Installation Guide (from Configuring): http://wiki.openvz.org/Quick_installation#Configuring NOTE: as we build our kernel, we have to edit /etc/init.d/vz to not use kernel modules. This script will bring up our virtual interface venet0 6- Create a VE NOTE: At this point, we have a local VE root, located in /var/lib/vz/ 7- Provide a OpenVZ template as NFS filesystem 8- Provide a empty directory as NFS filesystem 9- Mount AUFS in /var/lib/vz/private/NUM_VE, where (7) is RO+WH and (8) is RW 10- Start the VE 11- Run as superuser vzctl chkpnt NUM_VE dumpfile <dump file> > > J. R. Okajima > Thank you. -- Josiney de Souza C3SL: http://www.c3sl.ufpr.br Trans Falls: http://www.transfalls.com.br ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com
