[CRIU] dumping LXC 1.0 container failed - unable to open irmap-cache: No such file or directory

David Shwatrz dshwatrz at gmail.com
Wed Mar 5 02:32:28 PST 2014


Hello,
I am trying to checkpoint an LXC 1.0 container and it fails.
I am trying it with crtools 1.2.

The command I use is:
criu dump -t 4983 -v4 -D images --shell-job --ext-unix-sk -o dump.log
--tcp-established --file-locks
and the log file shows this as a first error:
unable to open irmap-cache: No such file or directory
the full log fine is in:
http://pastebin.com/e3MKxmBg

more info:
lxc-indo -n fedora
shows
Name:           fedora
State:          RUNNING
PID:            4983
IP:             192.168.2.100
CPU use:        2.28 seconds
BlkIO use:      0 bytes
Memory use:     1.73 MiB
KMem use:       0 bytes
Link:           vethA5EI9Q
 TX bytes:      12.37 KiB
 RX bytes:      208.88 KiB
 Total bytes:   221.25 KiB


and the config file is:

lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = virbr0
lxc.network.ipv4 = 192.168.2.100/24

lxc.network.hwaddr = fe:2c:ef:71:90:74
lxc.rootfs = /var/lib/lxc/fedora/rootfs

# Include common configuration
lxc.include = /usr/share/lxc/config/fedora.common.conf

lxc.utsname = fedora

lxc.autodev = 1


lxc.console = none
lxc.tty = 0

And I am running the LXC container thus:

lxc-start -d -n fedora

Any ideas what went wrong ?

regards
DavidS


More information about the CRIU mailing list