1577235975 Q * Aiken Remote host closed the connection
1577248199 M * Bertl  off to bed now ... have a good one everyone!
1577248202 N * Bertl Bertl_zZ
1577251644 J * Aiken ~Aiken@b951.h.jbmb.net
1577266060 J * fstd ~fstd@xdsl-78-35-82-26.nc.de
1577266527 Q * fstd_ Ping timeout: 480 seconds
1577267949 Q * Ghislain Quit: Leaving.
1577268537 Q * Carpoon Ping timeout: 480 seconds
1577268654 J * Carpoon ~Carpoon@217.13.106.146
1577269726 Q * padde Remote host closed the connection
1577269796 J * padde ~padde@cc3po.patrick-nagel.net
1577275205 Q * Aiken Remote host closed the connection
1577276522 J * Ghislain ~Ghislain@adsl1.aqueos.com
1577276834 J * Ghislain1 ~Ghislain@adsl2.aqueos.com
1577277186 Q * Ghislain Ping timeout: 480 seconds
1577282348 N * Bertl_zZ Bertl
1577282353 M * Bertl  morning folks!
1577285000 M * Guy- Bertl: hi! with 4.9.207-vs2.3.9.9, the start time of guest processes appears to be misreported -- is this known?
1577285010 M * Guy- root     47423  0.0  0.0   7308   448 pts/0    SN   15:18   0:00      \_ sleep 1h
1577285017 M * Guy- I just started this sleep(1)
1577285062 M * Bertl what's the start time here?
1577285082 M * Guy- 15:18
1577285086 M * Guy- it's about 24 minutes in the past
1577285102 M * Bertl and the time inside the guest is correct?
1577285105 M * Guy- yes
1577285112 M * Bertl and when was it started?
1577285139 M * Guy- not quite 5 hours ago
1577285154 M * Bertl is the time virtualization enabled?
1577285170 M * Bertl i.e. does it show an uptime of about 5 hours?
1577285170 M * Guy- # CONFIG_VSERVER_VTIME is not set
1577285182 M * Guy- it shows an uptime of 4:49
1577285201 M * Guy- I can restart a guest to see if it makes a difference
1577285202 M * Bertl hmm, so the host was restarted about 5 hours ago?
1577285210 M * Guy- yes, the host booted 5 hours ago
1577285218 M * Bertl yes, please restart the guest
1577285244 M * Bertl it is probably an artefact from the VTIME changes which should be disabled but are not
1577285295 M * Guy- Bertl: after restart, the guest thinks all processes inside it started at 10:45
1577285299 M * Guy- which is when the host started, I guess
1577285313 M * Bertl yeah, makes sense
1577285421 M * Guy- is there some quick fix for this? would it help if I enabled VSERVER_VTIME?
1577285610 M * Bertl it might, checking now
1577286074 M * Bertl does your guest have VIRT_UPTIME set?
1577286095 M * Bertl I presume so, and if yes, then disabling that should provide a quick fix
1577286144 M * Guy- not unless that's the default
1577286169 M * Bertl try to add ~VIRT_UPTIME
1577286220 M * Bertl (context flags)
1577286222 M * Guy- fwiw, the uptime inside the guest is correct (15 minutes now for the one I restarted)
1577286225 M * Guy- but I'll try
1577286245 M * Bertl yeah, it is a missing #ifdef for the CONFIG_VSERVER_VTIME
1577286276 M * Bertl i.e. with CONFIG_VSERVER_VTIME disabled, the VIRT_UPTIME shouldn't do anything
1577286289 M * Guy- if you tell me where the ifdef is missing, I can rebuild the kernel
1577286305 M * Bertl will upload a patch shortly
1577286335 M * Guy- adding ~VIRT_UPTIME to /etc/vservers/.defaults/cflags didn't help
1577286341 M * Guy- trying with the specific guest config now
1577286351 M * Guy- that helped!
1577286379 M * Guy- I don't suppose there's a way to turn this flag off for running guests? :)
1577286389 M * Bertl yes, there is
1577286460 M * Guy- I'm looking at chcontext(8)
1577286549 M * Guy- but that doesn't seem to do it
1577286628 M * Guy- vattribute --xid 128 --flag '~VIRT_UPTIME'
1577286631 M * Guy- this works
1577286678 M * Bertl there you go :)
1577286947 M * Bertl http://vserver.13thfloor.at/Experimental/delta-vtime-fix02.diff
1577287009 M * Guy- thanks!
1577287021 M * Guy- Bertl: this shouldn't affect 4.4.x, right?
1577287212 M * Bertl nope
1577287235 M * Bertl 4.4.x doesn't have the boottime changes yet
1577302776 J * Aiken ~Aiken@b951.h.jbmb.net
1577311511 M * Guy- Bertl: I confirm that delta-vtime-fix02.diff fixes the problem
1577311605 M * Bertl excellent! tx!