[Bug 1586762] Re: Clock skew from host when using adt-virt-qemu runner

Martin Pitt martin.pitt at ubuntu.com
Mon May 30 13:23:13 UTC 2016

This was fixed almost a year ago in Ubuntu 15.10 (wily) in

autopkgtest (3.16.3) unstable; urgency=medium

  * Don't invoke QEMU with -localtime. QEMU defaults to and Linux prefers the
    hw clock in UTC. This avoids large time jumps when doing NTP.
 -- Martin Pitt <mpitt at debian.org>  Thu, 27 Aug 2015 19:54:51 +0200

So I suggest using the version in trusty-backports or running
autopkgtest directly from git in your Jenkins instance.

** Changed in: autopkgtest (Ubuntu)
       Status: New => Fix Released

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.

  Clock skew from host when using adt-virt-qemu runner

Status in autopkgtest package in Ubuntu:
  Fix Released

Bug description:
  We were having issues when trying to collect Junit test results for
  MAAS due to the fact that Jenkins was throwing an error saying the
  report was too old. We later found that this was because the clock on
  the testbed was 3 or so hours behind the host. We noted there is some
  code in the adt-virt-qemu runner which attempts to correct the
  timezone to the hosts timezone but running this on a qemu instance we
  had started ourselves didn't seem to reproduce the issue. After
  comparing the qemu-system-x86_64 call made by adt-virt-qemu to one we
  had handcrafted ourselves we noted the presence of the '-localtime'
  argument in the command used by adt-virt-qemu. Removing this fixed the
  clock skew.

  At a minimum there needs to be a way to unspecify -localtime so we can
  fix the situation in our environment. If the argument is no longer
  needed it should be removed wholesale.

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list