Problem : Date definitively fixed (at 2014-08-25) , hwclock allright

[Dieu]

Hello,

i have a mysterious problem.
1) is NOT an UTC / Time zone problem + (edit) NOT a "ntpd" problem


########### INFORMATIONS of servers :
2) DESTINATION
-------------------
ROOT - DESTINATION # pveversion -vproxmox-ve-2.6.32: not correctly installed (running kernel: 3.2.59-01-amd64-proxmox)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: not correctly installed
vzprocps: not correctly installed
vzquota: not correctly installed
pve-qemu-kvm: 1.7-8
ksm-control-daemon: not correctly installed
glusterfs-client: 3.4.2-1

ROOT -DESTINATION # uname -a
Linux DESTINATION 3.2.59-01-amd64-proxmox #1 SMP Tue Jun 3 11:48:44 CEST 2014 x86_64 GNU/Linux
-------------------

3) SOURCE (proxmox v2)
-------------------
ROOT - SOURCE # pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 3.2.52-01-amd64-proxmox
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: not correctly installed
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-3
vzctl: not correctly installed
vzprocps: not correctly installed
vzquota: not correctly installed )

ROOT - SOURCE # uname -a
Linux SOURCE 3.2.52-01-amd64-proxmox #1 SMP Mon Oct 28 12:01:23 CET 2013 x86_64 GNU/Linux
-------------------

########### INFORMATIONS of servers !

[EDIT] --------------------
Debian 7.6 in both and similar kernel :
# uname -a
Linux SOURCE 3.2.59-01-amd64 {-proxmox} #1 SMP

On my vm exactly :
Linux SOURCE 3.2.59-01-amd64 #1 SMP
Debian 7.6

On my proxmox V3:
Linux SOURCE 3.2.59-01-amd64-proxmox #1 SMP
Debian 7.6
On my proxmox V2:
Linux SOURCE 3.2.52-01-amd64-proxmox #1 SMP
Debian 7.6

666.conf
-------------
bootdisk: virtio0
cores: 2
ide2: none,media=cdrom
memory: 2048
name: my-vm
net0: virtio=MAC ADRESS
onboot: 1
ostype: l26
sockets: 1
virtio0: my-lvm-vstore:vm-666-disk-1,size=50G
------------

add or not "localtime: 1" in 666.conf have no effect !
-------------------- [EDIT]



So my problem ; i migrated one VM from "SOURCE" to "DESTINATION" = in order proxmox v2 to proxmox v3.




Today 2014-08-28 when i started my VM (on proxmox V3) "date" say 2014-08-25@15:44
hwclock have good time : 2014-08-28@10:00 (when i write this)


When i started my VM on proxmox V2; the SAME VM, the same /etc/pve/qemeu-serrver/666.conf And the same LVM
Date and hwclock are good !


In first case proxmox V3 date is always 2014-08-25 ("date" say it) but hwclock have good time (time of my server)
In second case proxmox V2 date is good and hwclock too.


What i tryed (on my VM) :
1) hwclock --hctosys didn't work, "date" reset after reboot.
2) modify /etc/rcS to add some thing like "hwclock --hctosys" take no effect. (and more tries)
3) hwclock --adjust to modify /etc/adjtime ; to take effet
4) delete /etc/adjtime ; my hwclock reset to "date"
(and i neeed to make hwclock --sete --date "good date")


In all case "date" say 2014-08-25@15h44
Instead of hwclock say the "real time"


(NB : in all case i started in single mode ; there is an fsck issue to "future"
and i use single mode for down my network interface ; i don't want to update "date" by ntp : I want to solve this problem )



[EDIT] --------------------
For example :
1) My VM still running
2) i update "date" with hwclock or ntpd ; is same result !
3) Date reply Thu aug 28 12:00 = "real time" / good time
4) # reboot
5) When my VM restart
a) problem with fsck "wrong date ; from future" ... date reply >> 2014-08-25@15:44 last mount Thu aug 28 12:00 = "today" / actual time.
b) "give root password for maintenance (or type CTRL-D to continue )"
c) typing root password
d) my-vm # hwclock && date
Thu aug 28 12:00 ( = today )
Mon aug 25 15:44

Is it clear with example ?

If you prefer like : Groundhog Day or Edge of tomorow ! ^_^
This "image" is more comprehensive ??
-------------------- [EDIT]
So i presume i missed something but...


If you have any question to need more informations of my case you welcome
If you have any suggestions, with pleasure

thank you,

L.

 

[udo]

Hello,

i have a mysterious problem.
1) is not an UTC / Time zone problem.


...
If you have any question to need more informations of my case you welcome
If you have any suggestions, with pleasure

thank you,

L.

Hi,
how looks your ntpd?
Please post output of

grep ^server /etc/ntp.conf
ps aux | grep ntp
ls -lsa /var/lib/ntp/ntp.drift
cat /var/lib/ntp/ntp.drift

Udo

 

[spirit]

What is the guest os ?


if kvmclock is used, it should be sync to host clock. (without ntp)

cat /sys/devices/system/clocksource/clocksource0/current_clocksource

 

[Dieu]

Hello

thank you for your answer, but ;
Is not an NTP problem; not a DRIFT problem, NOT an UTC/ time zone problem !


My vm start ALWAYS at 2014-08-25@15:44 !!


My problem is "hardware clock" & "date"

When i started my VM in single mode ACKA "without network" (without ntpd of course)

hclock say to me the good time #hwclock >> REPLY Fri 28 aug 12:00 (my actually time)
date say to me wrong time # date >> REPLY mon 25 aug 15:44 !! ALWAYS !!!


You understand : on every boot i have a problem whith FSCK issue from "future" on file system,
wrong date, wrong time...

# My ntpd work finely : when i start in "normal mal" (after fsck) and with network in few time ntpd make is work and date "good time" !
# BUT when i reboot my VM, started at 2014-08-25@15:44 ...
# ntpd is not in cause !


My VM always "start" at 2014-08-25@15:44 , my hwclcok reply real/good time & ntdp work correctly

For example :
1) My VM still running
2) i update "date" with hwclock or ntpd ; is same result !
3) Date reply Thu aug 28 12:00 = "real time" / good time
4) # reboot
5) When my VM restart
a) problem with fsck "wrong date ; from future" ... date reply >> 2014-08-25@15:44 last mount Thu aug 28 12:00 = "today" / actual time.
b) "give root password for maintenance (or type CTRL-D to continue )"
c) typing root password
d) my-vm # hwclock && date
Thu aug 28 12:00 ( = today )
Mon aug 25 15:44

Is it clear ?
If you prefer like : Groundhog Day or Edge of tomorow ! ^_^
This "image" is more comprehensive ??



L.

 

[Dieu]

Hello thank you for your suggest

and yes i forgot it :

cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> kvm-clock
and "*available_clocksource"
> kvm-clock tsc hpet acpi_pm


Debian 7.6 in both and similar kernel :
# uname -a
Linux SOURCE 3.2.59-01-amd64 {-proxmox} #1 SMP

On my vm exactly :
Linux SOURCE 3.2.59-01-amd64 #1 SMP
Debian 7.6

On my proxmox V3:
Linux SOURCE 3.2.59-01-amd64-proxmox #1 SMP
Debian 7.6
On my proxmox V2:
Linux SOURCE 3.2.52-01-amd64-proxmox #1 SMP
Debian 7.6

666.conf
-------------
bootdisk: virtio0
cores: 2
ide2: none,media=cdrom
memory: 2048
name: my-vm
net0: virtio=MAC ADRESS
onboot: 1
ostype: l26
sockets: 1
virtio0: my-lvm-vstore:vm-666-disk-1,size=50G
------------

add or not "localtime: 1" in 666.conf have no effect !

I verify on my proxmox /etc/adjtime
hwclock on "my-vm" is the same time as "hwclock" on my proxmox (minus my hands to type from one to the other = 1 sec )


L.

 

[spirit]

On my proxmox :
Linux SOURCE 3.2.52-01-amd64-proxmox #1 SMP Mon Oct 28 12:01:23 CET 2013 x86_64 GNU/Linux

What is this kernel ? (It's your host kernel right ?)

 

[Dieu]

Hello,

sorry i'm editing my own post and original post to complet informations

désolé j'étais entrain d'éditer les posts de réponse et original pour ajouter les informations ad hoc


L.

 

[spirit]

Hello,

sorry i'm editing my own post and original post to complet informations

désolé j'étais entrain d'éditer les posts de réponse et original pour ajouter les informations ad hoc


L.

what is this 3.2 kernel on host ?
it's not the official proxmox kernel (pve-kernel package).
Could be great to see if it's works fine with pve-kernel. (kvm module bug for example)

 

[Dieu]

Problem solved ; done !

L.

 

[spirit]

Problem solved ; done !

L.

Can you tell us how you solve the problem ?

 

[Dieu]

Yes

 

[spirit]

Yes

? so, you do you have solved the problem ?