** Changed in: lxc (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1569679
Title:
lxc failed to do lxc-checkpoint again
Status in
Hi guys,
Can someone post a full log from a container where this fails? I'm
curious if it has the warning,
+ WARN("using host's /dev/null for container init's std
fds, migraiton won't work");
If so, it seems like the containers rootfs isn't set up correctly and
all is behaving as
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1569679
Title:
lxc failed to do lxc-checkpoint again
Status in
Thanks, Tycho: Here is the new bug: #1581818
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1569679
Title:
lxc failed to do lxc-checkpoint again
Status in lxc package in
Hi Frank,
On Sun, May 08, 2016 at 09:15:29AM -, 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
>
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?
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Strange. Basically it's using the host's /dev/null as described in
7a55c1576e2752e27882c52e34edcb8388120ad1, but I'm not sure why it would
be doing that if you have a valid /dev/null in the container.
If you turn on autodev does it work?
--
You received this bug notification because you are a
See also: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1561434
lxc-checkpoint works well under -
>> CRIU Version: 2.0-2ubuntu2
>> LXC Version: 2.0.0~rc13-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in
It has, and "echo 1 > /dev/null" works inside the container.
Old lxc & criu version can make successful checkpoint but current
version can't. My container doesn't change anything.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Right. I'm guessing your container doesn't have a proper /dev/null
itself? That will cause this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1569679
Title:
lxc failed to
The config is as same as it was previously.
lxc.pts = 1024
lxc.console = none
lxc.tty = 0
lxc.pivotdir = lxc_putold
lxc.autodev = 0
...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Do you have autodev turned off in the container without the container
itself having a /dev/null? I think that will still trigger this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
$ cat dump.log
Error (files-reg.c:1101): Can't lookup mount=235 for fd=0 path=/null
Error (cr-dump.c:1303): Dump files (pid: 11964) failed with -1
Error (cr-dump.c:1600): Dumping FAILED.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Can you show the output in the dump.log in the checkpoint directory?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1569679
Title:
lxc failed to do lxc-checkpoint again
15 matches
Mail list logo
