locked
Time Jump with Hyper-V and Centos 7 RRS feed

  • Question

  • We’re experiencing an issue with Redhat 7 and Hyper-V running 2012 R2.

    When we reboot, the time shifts upon startup. I believe this happens when the System Bios or EUFI sets the time during the initial boot.  Here is an example from /var/log/messages.

    Feb 26 10:31:13 es4 systemd: Stopping Hyper-V VSS daemon...

    Feb 26 10:31:13 es4 systemd: Stopping System Logging Service...

    Feb 26 10:31:13 es4 systemd: Stopping Kernel Samepage Merging (KSM) Tuning Daemon...

    Feb 26 10:31:13 es4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="933" x-info="http://www.rsyslog.com"] exiting on signal 15.

    Feb 26 10:31:49 es4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="933" x-info="http://www.rsyslog.com"] start

    Feb 26 22:17:51 es4 journal: Runtime journal is using 8.0M (max 592.3M, leaving 888.5M of free 5.7G, current limit 592.3M).

    Feb 26 22:17:51 es4 kernel: Initializing cgroup subsys cpuset

    Feb 26 22:17:51 es4 kernel: Initializing cgroup subsys cpu

    Feb 26 22:17:51 es4 kernel: Initializing cgroup subsys cpuacct

    Feb 26 22:17:51 es4 kernel: Linux version 3.10.0-123.20.1.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.2 20140120 (Red Hat 4.8.2-16) (GCC) ) #1 SMP Thu Jan 29 18:05:33 UTC 2015

    Feb 26 22:17:51 es4 kernel: Command line: BOOT_IMAGE=/vmlinuz-3.10.0-123.20.1.el7.x86_64 root=/dev/mapper/centos-root ro rd.lvm.lv=centos/swap vconsole.font=latarcyrheb-sun16 rd.lvm.lv=centos/root crashkernel=auto vconsole.keymap=us rhgb quiet LANG=en_US.utf8

    Feb 26 22:17:51 es4 kernel: e820: BIOS-provided physical RAM map: --SKIPPING VARIOUS BOOT MESSAGES—

     

    Feb 26 22:18:08 es4 systemd: Starting Activation of DM RAID sets...

    Feb 26 22:18:08 es4 kernel: input: PC Speaker as /devices/platform/pcspkr/input/input1

    Feb 26 22:18:08 es4 systemd: plymouth-start.service: main process exited, code=killed, status=11/SEGV

    Feb 26 22:18:08 es4 systemd: Unit plymouth-start.service entered failed state.

    Feb 26 22:18:08 es4 kernel: hv_utils: Registering HyperV Utility Driver

    Feb 26 22:18:08 es4 kernel: hv_vmbus: registering driver hv_util

    Feb 26 10:31:46 es4 systemd: Time has been changed

    Feb 26 10:31:46 es4 kernel: hv_vmbus: registering driver hyperv_keyboard

    Feb 26 10:31:46 es4 kernel: input: AT Translated Set 2 keyboard as /devices/LNXSYSTM:00/device:00/ACPI0004:00/VMBUS:00/vmbus_0_3/serio0/input/input2

    Feb 26 10:31:46 es4 kernel: hv_vmbus: registering driver hyperv_fb

    Feb 26 10:31:46 es4 kernel: fb: conflicting fb hw usage hyperv_fb vs EFI VGA - removing generic driver

    Feb 26 10:31:46 es4 kernel: Console: switching to colour dummy device 80x25

    Feb 26 10:31:46 es4 kernel: hyperv_fb: Screen resolution: 1152x864, Color depth: 32

    Feb 26 10:31:46 es4 kernel: Console: switching to colour frame buffer device 144x54

    Feb 26 10:31:46 es4 kernel: alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)

    Feb 26 10:31:46 es4 kernel: alg: No test for crc32 (crc32-pclmul)

    Feb 26 10:31:46 es4 systemd: Starting LVM2 PV scan on device 8:3...

    Feb 26 10:31:46 es4 systemd: Started Activation of DM RAID sets.

     

    I’ve looked at the system time in GRUB to confirm this, and it appears the time is shifted ahead when it is booted, as GRUB has the new incorrect system time. The jump is somewhat random and appears to be several hours or up to two days ahead.

     

    We are on a 2012 R2 Hyper-V cluster and we have seen this on multiple hypervisors. On both hypervisors, I’ve upgraded to the latest Microsoft updates. I’ve also seen this with Gen1 and Gen2 VMs and multiple CentOS kernels including the latest: 3.10.0-123.20.1.el7.x86_64  (haven’t tested Redhat).

     

    This issues interferes with some licensing software we use that is time sensitive. The licensing software thinks we are monkeying with the system time and shuts down.

     

    Again, I’ve searched for evidence of this issue and haven’t found anyone in any forums who’s having the same problem, but I don’t know how big the install base is for Hyper-V RHEL/CentOS 7 is. Even if you can’t look into it, a point in the right direction would be appreciated. I’m fine with submitting this to Microsoft support as well, but am pretty unfamiliar with that process.

     

    Thanks in advance,

    Nate
    Thursday, February 26, 2015 7:40 PM

All replies