This bug was fixed in the package lxcfs - 2.0.8-1ubuntu1
---
lxcfs (2.0.8-1ubuntu1) bionic; urgency=medium
* Re-sync with Debian, remaining delta (for backports):
- Include upstart jobs on older Ubuntu releases
- Build-depend on dh-systemd with older debootstrap
--
** Changed in: lxcfs (Ubuntu)
Status: Fix Released => Triaged
** Changed in: lxcfs (Ubuntu Xenial)
Status: Fix Released => Triaged
** Changed in: lxcfs (Ubuntu Yakkety)
Status: Fix Released => Triaged
** Changed in: lxcfs (Ubuntu Zesty)
Status: Fix Released =>
This bug was fixed in the package lxcfs - 2.0.7-0ubuntu1~16.10.2
---
lxcfs (2.0.7-0ubuntu1~16.10.2) yakkety-proposed; urgency=medium
* Cherrypick patch reverting the virtualization of bstat field (LP:
#1654310)
-- Serge Hallyn Tue, 04 Jul 2017 13:29:14
This bug was fixed in the package lxcfs - 2.0.7-0ubuntu1~17.04.2
---
lxcfs (2.0.7-0ubuntu1~17.04.2) zesty-proposed; urgency=medium
* Cherrypick patch reverting the virtualization of bstat field (LP:
#1654310)
-- Serge Hallyn Tue, 04 Jul 2017 13:29:40
This bug was fixed in the package lxcfs - 2.0.7-0ubuntu1~16.04.2
---
lxcfs (2.0.7-0ubuntu1~16.04.2) xenial-proposed; urgency=medium
* Cherrypick patch reverting the virtualization of bstat field (LP:
#1654310)
-- Serge Hallyn Tue, 04 Jul 2017 10:43:18
After upgrading to lxcfs/xenial-proposed (2.0.7-0ubuntu1~16.04.2), the
problem is fixed for me
Inside a container:
root@apt-cacher:~# ps auxwww | grep apt
apt-cac+ 309 0.0 0.7 653476 7128 ?Ssl Jul08 1:02
/usr/sbin/apt-cacher-ng SocketPath=/run/apt-cacher-ng/socket -c
Hello Jason, or anyone else affected,
Accepted lxcfs into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxcfs/2.0.7-0ubuntu1~16.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
[Impact]
Processes within LXC container are seen as created in the future.
[Test Case]
1. create an LXC container on a host which has been up for untrivial amount of
time (say 1 hour)
2. look at "ps aux" output in START column - all the process are seen as
started in the future
[Regression
@gozdal,
would you be willing to add a SRU justification as per section 3.1 of
https://wiki.ubuntu.com/StableReleaseUpdates to the description of this
bug?
** Also affects: lxcfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: lxcfs (Ubuntu Xenial)
Importance:
I've pushed a package reverting that field to xenial-proposed - it will
await approval there.
I've set the priority to high as this seems to be affecting other
software adversely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I believe that packages for several distributions (esp. Xenial) still
contain this now-revered patch. Would it be possible to release packages
with btime virtualization reverted?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Mon, Jun 19, 2017 at 04:28:07PM -, Jason Baron wrote:
> Ok, I guess we could intercept the /proc//stat read() call and
> overwrite the starttime there with the correct value? That is, add the
> starttime from /proc//stat to the host boot time and then subtract
> that from the guest boot
Ok, I guess we could intercept the /proc//stat read() call and
overwrite the starttime there with the correct value? That is, add the
starttime from /proc//stat to the host boot time and then subtract
that from the guest boot time.
--
You received this bug notification because you are a member
On Mon, Jun 19, 2017 at 01:04:38PM -, gozdal wrote:
> This introduces a different problem: process creation time is counted as
> offset from btime:
>
> (22) starttime %llu
> The time the process started after system boot. In
> kernels before Linux 2.6, this value was
This introduces a different problem: process creation time is counted as
offset from btime:
(22) starttime %llu
The time the process started after system boot. In
kernels before Linux 2.6, this value was expressed
in jiffies. Since Linux 2.6, the value is
** Changed in: lxcfs (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654310
Title:
lxcfs: update the 'btime' field in /proc/stat to reflect guest boot
This is fixed in LXCFS 2.0.7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654310
Title:
lxcfs: update the 'btime' field in /proc/stat to reflect guest boot
time not host
To manage
I've created a pull request to address this issue:
https://github.com/lxc/lxcfs/pull/169
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654310
Title:
lxcfs: update the 'btime' field in
Thanks I've created https://github.com/lxc/lxcfs/issues/164 to track
this.
** Bug watch added: LXCFS bug tracker #164
https://github.com/lxc/lxcfs/issues/164
** Changed in: lxcfs (Ubuntu)
Importance: Undecided => Medium
** Changed in: lxcfs (Ubuntu)
Status: New => Triaged
--
You
** Package changed: make-dfsg (Ubuntu) => lxcfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654310
Title:
lxcfs: update the 'btime' field in /proc/stat to reflect guest boot
time not
20 matches
Mail list logo