[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

Package: xen-linux-system-2.6.32-5-xen-amd64
Version: 2.6.32-21
Severity: important

Hi, Did you receive this bug report? I hadn't received a bug ID even
though receiving the copy of the original report. Likely because the
address it was sent from originally was invalid.


Hi All,                                                                                                                                           
Im running Xen 4.0.1-rc6 Debian squeeze with pvops 2.6.32-21 kernel.                                                                              
Today I noticed (when kerberos to the domain controllers stopped                                                                                  
working..) that the clock was 50 minutes out in dom0 -- This caused the                                                                           
HVM windows domain controllers to have the wrong time.                                                                                            
I'm not sure if this is a kernel issue or a xen issue, but the only                                                                               
thing related is I can see the following in the kernel log:                                                                                       
Oct  2 18:50:33 havhost1 kernel: [623480.977748] Clocksource tsc unstable (delta = -2999660303788 ns)                                             
But I also see in the dmesg log that xen is using it's own clock.                                                                                 
[    7.676563] Switching to clocksource xen                                                                                                       
I can't identify anything else in the logs to indicate when the time                                                                              
might have changed. I have a few other dom0 at the same level that                                                                                
haven't decided to change the time.                                                                                                               
Can anyone confirm whether xen controls the time or the kernel? Also                                                                              
when I corrected the time in dom0 it was still wrong in HVM domU -- How                                                                           
long does it take for this to propogate? (I rebooted the VM's to correct                                                                          
it immediately).                                                                                                                                  

It appears the HVM domU (windows server 2008)
unexpectedly shut down at 18:51, after the unstable clocksource error.
qemu-dm logs show a reset "reset requested in cpu_handle_ioreq." and
xend.log shows a reboot 
Any other pointers on how to ensure stability of clocks from dom0 to                                                                              
domU HVM hosts (and pv for that matter..) would be appreciated. NTP was running
but also appeared to have crashed at the same time.                                                                                   

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xen-linux-system-2.6.32-5-xen-amd64 depends on:
ii  linux-image-2.6.32-5-xen-amd 2.6.32-21   Linux 2.6.32 for 64-bit PCs, Xen d
ii  xen-hypervisor-3.2-1-amd64 [ 3.2.1-2     The Xen Hypervisor on AMD64
ii  xen-hypervisor-4.0-amd64 [xe 4.0.1~rc6-1 The Xen Hypervisor on AMD64

xen-linux-system-2.6.32-5-xen-amd64 recommends no packages.

xen-linux-system-2.6.32-5-xen-amd64 suggests no packages.

Reply to: