From owner-freebsd-hackers@freebsd.org Wed Sep 23 18:35:32 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40DE3A0647B for ; Wed, 23 Sep 2015 18:35:32 +0000 (UTC) (envelope-from bmvince1@asu.edu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 226AF1B3A for ; Wed, 23 Sep 2015 18:35:32 +0000 (UTC) (envelope-from bmvince1@asu.edu) Received: by mailman.ysv.freebsd.org (Postfix) id 1EE95A0647A; Wed, 23 Sep 2015 18:35:32 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E7E5A06479 for ; Wed, 23 Sep 2015 18:35:32 +0000 (UTC) (envelope-from bmvince1@asu.edu) Received: from mail-io0-f182.google.com (mail-io0-f182.google.com [209.85.223.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E8BAF1B39 for ; Wed, 23 Sep 2015 18:35:31 +0000 (UTC) (envelope-from bmvince1@asu.edu) Received: by ioiz6 with SMTP id z6so52156452ioi.2 for ; Wed, 23 Sep 2015 11:35:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pKCjXpBkcl3JBMe8b9xx2qnsdj/sYpCEWqJHyP24hfQ=; b=Gg4FkqbYem/vKNJ3KPbexNjxRNkourcBv6uPXadr2bnqoDa0vuPMQ62O/fGErfXlmb 2tGGjuXfkDCfx6LorFCLnhGnrlL0cMDUj8HGC3QH+H3hrx2PFtXiJC5/yVrc8KrbZhsH GOllfR/83/Nq5vb59GHGLQ1pXOFhlJ53iH4F31gd4hs0W1S/lNKYGnmGXxALM7K4OMC/ 7LK0SxP0CE4YyCNvabJwIBOr29x3XwBCkxCW1RlEK7ovX1/jq1ahxw930KRezHzzb0Zb BFUADP4HW5NSdKPl3XKL6U8/thLapsUa2UCZ2Sslg75IAIDTE3KScOVS1R09ryfsqm6l 2C5Q== X-Gm-Message-State: ALoCoQn0SX4Er9CeTtNK6tCfx586M1SUTnSkfUYzYEM2Y82LEZr7/uHwBLimvioTyvCP+bpggbFf MIME-Version: 1.0 X-Received: by 10.107.129.104 with SMTP id c101mr39147926iod.141.1443031483667; Wed, 23 Sep 2015 11:04:43 -0700 (PDT) Received: by 10.36.71.18 with HTTP; Wed, 23 Sep 2015 11:04:43 -0700 (PDT) In-Reply-To: References: <39337.1442999127@critter.freebsd.dk> Date: Wed, 23 Sep 2015 11:04:43 -0700 Message-ID: Subject: Re: What IS the right NTP behaviour ? From: Brandon Vincent To: Tim Kientzle Cc: Poul-Henning Kamp , hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 18:35:32 -0000 On Wed, Sep 23, 2015 at 10:35 AM, Tim Kientzle wrote: > One concern I keep running into: Using NTP in VMs that are frequently suspended/resumed. Though I suppose this may be covered by your 'workstation' scenario (just step it after VM resume when you see the large skew). I would assume your hypervisor would sync the clock upon VM events. Does it not? Brandon Vincent