From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gaio@lilliput.linux.it>
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 0D72B62A72
for <pve-user@lists.proxmox.com>; Sat, 12 Feb 2022 11:40:41 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id EC3831ADA
for <pve-user@lists.proxmox.com>; Sat, 12 Feb 2022 11:40:10 +0100 (CET)
Received: from picard.linux.it (picard.linux.it [IPv6:2001:1418:10:5::2])
(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 729081AD0
for <pve-user@lists.proxmox.com>; Sat, 12 Feb 2022 11:40:10 +0100 (CET)
Received: by picard.linux.it (Postfix, from userid 10)
id 139393C9E98; Sat, 12 Feb 2022 11:40:04 +0100 (CET)
Received: from news by eraldo.lilliput.linux.it with local (Exim 4.89)
(envelope-from <gaio@lilliput.linux.it>) id 1nIpl3-0006lh-RJ
for pve-user@lists.proxmox.com; Sat, 12 Feb 2022 11:36:01 +0100
From: Marco Gaiarin <gaio@lilliput.linux.it>
Date: Fri, 11 Feb 2022 12:03:54 +0100
Organization: Il gaio usa sempre TIN per le liste, fallo anche tu!!!
Message-ID: <odshdi-fah.ln1@hermione.lilliput.linux.it>
X-Trace: eraldo.lilliput.linux.it 1644661492 25803 192.168.1.24 (12 Feb 2022
10:24:52 GMT)
X-Mailer: tin/2.4.4-20191224 ("Millburn") (Linux/5.4.0-99-generic (x86_64))
X-Gateway-System: SmartGate 1.4.5 <news.lilliput.linux.it>
To: pve-user@lists.proxmox.com
X-SPAM-LEVEL: Spam detection results: 0
AWL -0.377 Adjusted score from AWL reputation of From: address
BAYES_00 -1.9 Bayes spam probability is 0 to 1%
DATE_IN_PAST_12_24 1.049 Date: is 12 to 24 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
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: [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 <pve-user.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>,
<mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-user/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>,
<mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Sat, 12 Feb 2022 10:40:41 -0000
PVE 6.4, updated to the latest patch.
I've P2V an old debian squeeze box, 32bit, that have an impressive clock
drift, even if they had 'ntpd' up&running.
I've tried to remove '/etc/adjtime' and reboot, but nothing changed.
The strange thing is i got in logs:
Feb 10 15:15:37 sdinny kernel: [ 9481.004112] Clocksource tsc unstable (delta = 63065327 ns)
but:
sdinny:~# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
kvm-clock hpet acpi_pm
sdinny:~# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
kvm-clock
So 'tsc' is even not listed on clocksources, nor are used.
What i'm missing?! Thanks.
--
``... La memoria conta veramente solo se tiene insieme l'impronta del
presente e il progetto del futuro, se permette di fare senza dimenticare
quel che si voleva fare, di diventare senza smettere di essere,
di essere senza smettere di diventare...'' (Italo Calvino)