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 861427 - Windows Guest clock slower than Linux host
Summary: Windows Guest clock slower than Linux host
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Marcelo Tosatti
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-28 15:13 UTC by Eduardo Elias Ferreira
Modified: 2012-10-16 15:26 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-16 14:31:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Sosreport (3.11 MB, application/x-xz)
2012-09-28 15:13 UTC, Eduardo Elias Ferreira 		no flags Details
View All

Description Eduardo Elias Ferreira 2012-09-28 15:13:22 UTC 
Created attachment 618638 [details]
Sosreport

Description of problem:

An user report that: 

During standard business day the Windows VM I use for some of my applications has an issue with the system clock being
slow. So over the course of the day I am correcting it between 5-10 times.


How reproducible:
I was not able to reproduce it.

Steps to Reproduce:
Just using the Windows KVM after while.

Some details woth metion:

- Tried C:\Windows\system32>bcdedit /set {default} USEPLATFORMCLOCK on
- The problem occurs with or without the <timer name='rtc' tickpolicy='catchup'/> 
- His Windows Time Server just does not work, no matter what url is used.

I asked him to run sosreport while he is experiencing the problem which is attached.
Comment 2 Ademar Reis 2012-10-09 13:41:07 UTC 
Thank you for taking the time to enter a bug report with us. We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to  guarantee the timeliness or suitability of a resolution.

If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain  it receives the proper attention and prioritization to assure a timely resolution.

For information on how to contact the Red Hat production support team, please visit: https://www.redhat.com/support/process/production/#howto
Comment 3 Marcelo Tosatti 2012-10-09 16:59:03 UTC 
(In reply to comment #2)
> Thank you for taking the time to enter a bug report with us. We appreciate
> the feedback and look to use reports such as this to guide our efforts at
> improving our products. That being said, this bug tracking system is not a
> mechanism for requesting support, and we are not able to  guarantee the
> timeliness or suitability of a resolution.
> 
> If this issue is critical or in any way time sensitive, please raise a
> ticket through your regular Red Hat support channels to make certain  it
> receives the proper attention and prioritization to assure a timely
> resolution.
> 
> For information on how to contact the Red Hat production support team,
> please visit: https://www.redhat.com/support/process/production/#howto

(In reply to comment #2)
> Thank you for taking the time to enter a bug report with us. We appreciate
> the feedback and look to use reports such as this to guide our efforts at
> improving our products. That being said, this bug tracking system is not a
> mechanism for requesting support, and we are not able to  guarantee the
> timeliness or suitability of a resolution.
> 
> If this issue is critical or in any way time sensitive, please raise a
> ticket through your regular Red Hat support channels to make certain  it
> receives the proper attention and prioritization to assure a timely
> resolution.
> 
> For information on how to contact the Red Hat production support team,
> please visit: https://www.redhat.com/support/process/production/#howto

Eduardo,

He should configure Windows Time Server (plenty of literature available from Microsoft).

If it still fails with Windows Time Server, then the problem should be debugged.
Comment 4 Marcelo Tosatti 2012-10-09 17:05:24 UTC 
> > For information on how to contact the Red Hat production support team,
> > please visit: https://www.redhat.com/support/process/production/#howto
> 
> Eduardo,
> 
> He should configure Windows Time Server (plenty of literature available from
> Microsoft).
> 
> If it still fails with Windows Time Server, then the problem should be
> debugged.

Should expand on the meaning of "Windows Time Server" does not work.
Comment 5 Marcelo Tosatti 2012-10-16 14:31:45 UTC 
Eduardo, closing the bug as insufficient data. If you can configure Windows Time Server, and still the synchronization fails, please reopen the bug.
Comment 6 Eduardo Elias Ferreira 2012-10-16 15:26:14 UTC 
Marcelo, the user got his Windows Time Server working. It was not and I have no idea why. (Long story)

Since he does not replied if with Windows Time Server worked for him yet, I am ok with the bug close.

Cheers.
Note You need to log in before you can comment on or make changes to this bug.