Hi Frank,

On Sun, May 08, 2016 at 09:15:29AM -0000, Frank Kloeker wrote:
> I have the same issue on a fresh installed Ubuntu-16.04 VM on OpenStack,
> but not in a VM on Citrix XenCenter. Are there some depedencies from the
> hypervisor?

This is not the same issue,

> criu 2.0-2ubuntu3 amd64
> lxd  2.0.0-0ubuntu4 amd64
> lxd-client 2.0.0-0ubuntu4 amd64 
> 
> snapshot_dump.log:
> 
> Error (cr-dump.c:1600): Dumping FAILED.
> 
> lxc.log:
> 
>             lxc 20160508091123.039 INFO     lxc_criu - criu.c:exec_criu:392 - 
> execing: /usr/sbin/criu dump --tcp-established --file-locks --link-remap 
> --force-irmap --manage-cgroups --ext-mount-map auto --enable-external-sharing 
> --enable-external-masters --enable-fs hugetlbfs --enable-fs tracefs -D 
> /var/lib/lxd/containers/c1/rootfs/state -o 
> /var/lib/lxd/containers/c1/rootfs/state/dump.log -vvvvvv -t 6418 
> --freeze-cgroup /sys/fs/cgroup/freezer///lxc/c1 --ext-mount-map 
> /dev/console:console --external tty[880
>             lxc 20160508091123.041 DEBUG    lxc_commands - 
> commands.c:lxc_cmd_handler:893 - peer has disconnected
>             lxc 20160508091123.074 ERROR    lxc_criu - criu.c:do_dump:879 - 
> dump failed with 1
> 
> When I enter this manually, I get the message:
> Error (image.c:404): Can't open dir /var/lib/lxd/containers/c1/rootfs/state: 
> No such file or directory

Can you please file a new issue and post the contents of
/var/log/lxd/c1/*.log?

Tycho


> -- 
> You received this bug notification because you are a member of Ubuntu
> containers team, which is subscribed to lxc in Ubuntu.
> Matching subscriptions: lxc
> https://bugs.launchpad.net/bugs/1569679
> 
> Title:
>   lxc failed to do lxc-checkpoint again
> 
> Status in lxc package in Ubuntu:
>   Confirmed
> 
> Bug description:
>   When doing lxc-checkpoint, it replies:
> 
>   lxc-checkpoint: criu.c: do_dump: 879 dump failed with 1
> 
>   Checkpointing xxx failed.
> 
>   ============
> 
>   About my ENV:
> 
>   # uname -a
>   Linux ubuntu 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:01:02 UTC 2016 
> x86_64 x86_64 x86_64 GNU/Linux
> 
>   # lsb_release -a
>   Distributor ID:     Ubuntu
>   Description:        Ubuntu Xenial Xerus (development branch)
>   Release:    16.04
>   Codename:   xenial
> 
>   # apt-cache policy lxc
>   lxc:
>     Installed: 2.0.0-0ubuntu1
>     Candidate: 2.0.0-0ubuntu1
>     Version table:
>    *** 2.0.0-0ubuntu1 500
>           500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
>           100 /var/lib/dpkg/status
> 
>   # apt-cache policy criu
>   criu:
>     Installed: 2.0-2ubuntu3
>     Candidate: 2.0-2ubuntu3
>     Version table:
>    *** 2.0-2ubuntu3 500
>           500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
>           100 /var/lib/dpkg/status
> 
>   ============
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: lxc 2.0.0-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
>   Uname: Linux 4.4.0-18-generic x86_64
>   NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
>   ApportVersion: 2.20.1-0ubuntu1
>   Architecture: amd64
>   Date: Wed Apr 13 12:44:20 2016
>   PackageArchitecture: all
>   ProcEnviron:
>    LANGUAGE=zh_CN:zh
>    TERM=xterm-256color
>    PATH=(custom, no user)
>    LANG=zh_CN.UTF-8
>    SHELL=/bin/bash
>   SourcePackage: lxc
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   defaults.conf:
>    lxc.network.type = veth
>    lxc.network.link = lxcbr0
>    lxc.network.flags = up
>    lxc.network.hwaddr = 00:16:3e:xx:xx:xx
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1569679/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569679

Title:
  lxc failed to do lxc-checkpoint again

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1569679/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to