RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1264382 - windows 8.1/windows2012 r2 fail to specify base="2006-06-17" as RTC time
Summary: windows 8.1/windows2012 r2 fail to specify base="2006-06-17" as RTC time
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.2
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Yvugenfi@redhat.com
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-18 10:38 UTC by Xueqiang Wei
Modified: 2019-02-20 02:57 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-22 11:28:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Xueqiang Wei 2015-09-18 10:38:47 UTC 
Description of problem:

Boot win8-64.1/win2012-64r2 guest with -rtc base="2006-06-17",clock=host,driftfix=slew, it doesn't change date inside guest. 

guest windows 7 is ok, guest RHEL7.2 is ok.


I downgrade to qemu-kvm-rhev-2.1.2-23.el7 to try, also hit this issue. 


Version-Release number of selected component (if applicable):
Kernel-3.10.0-314.el7.x86_64
qemu-kvm-rhev-2.3.0-22.el7
seabios-1.7.5-11.el7.x86_64
seabios-bin-1.7.5-11.el7.noarch


How reproducible:
100%


Steps to Reproduce:
1. boot guest w/o network
  # qemu-kvm ... -net none 
2. set time zone to Beijing(UTC +08:00) in guest 
  For linux: 
  # mv /etc/localtime /etc/localtime.bak 
  # ln -sf /usr/share/zoneinfo/Asia/Shanghai /etc/localtime 
  # reboot 
  For Windows: 
  Click time -> 'Change date and time settings' -> 'Change time zone' 
  choose 'UTC +08:00(Beijing, Chongqing)'
3. boot the guest with kvm-clock
/usr/libexec/qemu-kvm \
    -name 'virt-tests-vm1'  \
    -sandbox off  \
    -machine pc  \
    -nodefaults  \
    -vga qxl \
    -device intel-hda,bus=pci.0,addr=03 \
    -device hda-duplex  \
    -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20150911-182017-1qMDjwx6,server,nowait \
    -mon chardev=qmp_id_qmpmonitor1,mode=control  \
    -chardev socket,id=qmp_id_catch_monitor,path=/tmp/monitor-catch_monitor-20150911-182017-1qMDjwx6,server,nowait \
    -mon chardev=qmp_id_catch_monitor,mode=control \
    -device pvpanic,ioport=0x505,id=idtlvMTr  \
    -chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0-20150911-182017-1qMDjwx6,server,nowait \
    -device isa-serial,chardev=serial_id_serial0  \
    -chardev socket,id=seabioslog_id_20150911-182017-1qMDjwx6,path=/tmp/seabios-20150911-182017-1qMDjwx6,server,nowait \
    -device isa-debugcon,chardev=seabioslog_id_20150911-182017-1qMDjwx6,iobase=0x402 \
    -device nec-usb-xhci,id=usb1,bus=pci.0,addr=04 \
    -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,format=raw,file=/home/win8-64.1-virtio.raw \
    -device ide-drive,id=image1,drive=drive_image1 \
    -m 4096  \
    -smp 4,maxcpus=4,cores=2,threads=1,sockets=2  \
    -cpu 'Conroe',+kvm_pv_unhalt,+cx16 \
    -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1  \
    -spice port=3000,disable-ticketing  \
    -boot order=cdn,once=c,menu=off,strict=off \
    -enable-kvm \
    -monitor stdio \
    -rtc base="2006-06-17",clock=host,driftfix=slew  \
    -net none \
4. check the system time in guest and host
  For linux guest
  4.1 # date
  For window guest, in cmd.exe
  4.1 >echo %TIME%

Actual results:
date isn't changed inside guest

Expected results:
guest date is  2006-06-17


Additional info:
cpu info:
processor	: 7
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU           E5310  @ 1.60GHz
stepping	: 11
microcode	: 0xbc
cpu MHz		: 1595.927
cache size	: 4096 KB
physical id	: 1
siblings	: 4
core id		: 3
cpu cores	: 4
apicid		: 7
initial apicid	: 7
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca lahf_lm dtherm tpr_shadow vnmi flexpriority
bogomips	: 3191.89
clflush size	: 64
cache_alignment	: 64
address sizes	: 38 bits physical, 48 bits virtual
power management:
Comment 2 Xueqiang Wei 2015-09-18 11:10:51 UTC 
also hit this issue on:
kernel-3.10.0-316.el7.x86_64
qemu-kvm-rhev-2.3.0-23.el7
Comment 4 Yvugenfi@redhat.com 2015-09-22 11:28:32 UTC 
Looks like Windows "feature".

1. Windows Server doesn't let to set time "back". You can set it forward just to check that passing a date to -rtc effects Windows OS.

2. Also it is better to disable NTP ("Internet time synchronisation") on Windows when doing time related tests.
Comment 5 Li Xiaohui 2019-01-14 06:24:12 UTC 
Hi Yan,
Recently we met some similar bugs, so want to ask you for some help.

From your comment 4, I want to know:
1.For Windows Server guest, do we only need test set guest system time forward?
2.For Windows Desktop guest, do we need test set guest time both forward and back?

Looking forward for your reply.

Best Regards,
Li Xiaohui.
Comment 6 Li Xiaohui 2019-01-14 06:26:23 UTC 
Added to Comment 5 tip 2
2.For Windows Desktop or linux guest, do we need test set guest time both forward and back?
Comment 7 Yvugenfi@redhat.com 2019-01-14 13:48:35 UTC 
I think mainly we are interested in moving the time forward (as this is the main case for syncing the time).
Comment 8 Li Xiaohui 2019-01-18 07:52:57 UTC 
(In reply to Yan Vugenfirer from comment #7)
> I think mainly we are interested in moving the time forward (as this is the
> main case for syncing the time).

Hi Yan, 
Here I have to confirm with you again whether need test set rhel guest time back, because some bug about this has been fixed ago[1] or is beening handled now[2].
(About windows guest, we will only test set guest time forward in future)

[1] Bug 966808 - fail to specify base="2006-06-17" as RTC time
[2] Bug 1623401 - Fail to specify base="2001-01-01" as RTC time at RHEL8 guest

If need not test set rhel guest time back, we won't open such bugs[2] in the future, and will modify our polarion related cases. Because we think this change maybe isn't a small influence, so want to get your once more confirm.

Best Regards,
Li Xiaohui
Comment 9 Yvugenfi@redhat.com 2019-01-19 20:22:11 UTC 
(In reply to Li Xiaohui from comment #8)
> (In reply to Yan Vugenfirer from comment #7)
> > I think mainly we are interested in moving the time forward (as this is the
> > main case for syncing the time).
> 
> Hi Yan, 
> Here I have to confirm with you again whether need test set rhel guest time
> back, because some bug about this has been fixed ago[1] or is beening
> handled now[2].
> (About windows guest, we will only test set guest time forward in future)
> 
> [1] Bug 966808 - fail to specify base="2006-06-17" as RTC time
> [2] Bug 1623401 - Fail to specify base="2001-01-01" as RTC time at RHEL8
> guest
> 
> If need not test set rhel guest time back, we won't open such bugs[2] in the
> future, and will modify our polarion related cases. Because we think this
> change maybe isn't a small influence, so want to get your once more confirm.
> 
> Best Regards,
> Li Xiaohui
Hi Li,

Unfortunately, I don't know what's the correct behavior for RHEL. I will try to find out.

Best regards,
Yan.
Comment 12 Li Xiaohui 2019-02-20 02:57:42 UTC 
Hi,
Thanks all very much, I will correct related cases.
Cheers,
Li Xiaohui
Note You need to log in before you can comment on or make changes to this bug.