From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id C755B62648 for ; Mon, 21 Feb 2022 18:46:40 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B55471C730 for ; Mon, 21 Feb 2022 18:46:10 +0100 (CET) Received: from picard.linux.it (picard.linux.it [213.254.12.146]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 028411C703 for ; Mon, 21 Feb 2022 18:46:07 +0100 (CET) Received: by picard.linux.it (Postfix, from userid 10) id 602773CA17B; Mon, 21 Feb 2022 18:46:00 +0100 (CET) Received: from news by eraldo.lilliput.linux.it with local (Exim 4.89) (envelope-from ) id 1nMCbS-0008J1-2a for pve-user@lists.proxmox.com; Mon, 21 Feb 2022 18:36:02 +0100 From: Marco Gaiarin Date: Mon, 21 Feb 2022 11:19:40 +0100 Organization: Il gaio usa sempre TIN per le liste, fallo anche tu!!! Message-ID: References: X-Trace: eraldo.lilliput.linux.it 1645464807 31843 192.168.1.24 (21 Feb 2022 17:33:27 GMT) To: Arjen via pve-user X-Mailer: tin/2.4.4-20191224 ("Millburn") (Linux/5.4.0-100-generic (x86_64)) X-Gateway-System: SmartGate 1.4.5 Cc: pve-user@lists.proxmox.com In-Reply-To: ; from SmartGate on Mon, Feb 21, 2022 at 18:36:02PM +0100 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.760 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DATE_IN_PAST_06_12 1.543 Date: is 6 to 12 hours before Received: date JMQ_SPF_NEUTRAL 0.5 SPF set to ?all KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_SHORT 0.001 Use of a URL Shortener for very short URL SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [PVE-User] Old, 32bit, debian and clock drift. X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Feb 2022 17:46:40 -0000 Mandi! Arjen via pve-user In chel di` si favelave... > Sorry, I must have missed that. Other people also encountered your problem: > https://v13.gr/2016/02/15/running-an-ntp-server-in-a-vm-using-kvm/ > Instead of disabling ntpd, do not use the kvm-clock source on the NTP server VM. > Either way, make sure not to combine the two. OK, i've give it a try, for now, manually changing the clocksource with: echo 'hpet' > /sys/devices/system/clocksource/clocksource0/current_clocksource But some things seems strange to me... 1) this happen on *TWO* VMs in two different installation; i've dozen of similar installation where: root@vdmsv1:~# cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock and clock are perfectly in sync; true that these problematic VMs are pretty old debian, but not older than others that works as expected. 2) other docs, like: https://docs.oracle.com/en/database/oracle/oracle-database/21/ladbi/setting-clock-source-vm.html confirm that 'tsc' is the preferred clock source for VMs; but in these box that depicted the trouble, 'TSC' clock source get 'kicked off' because 'unreilable'. So, doing a little 'survey' on my VMs, seems that *all* VMs use by default 'kvm-clock' as the default clock source, but on those two VMs 'tsc' clock source is unreilable, and get kicked off, and 'kvm-clock' is unreilable too, but get not kicked off. Really, really strange... -- Chi parla male, pensa male e vive male. Bisogna trovare le parole giuste: le parole sono importanti! Nanni Moretti in Palombella Rossa