Bug 861427
Summary: | Windows Guest clock slower than Linux host | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Eduardo Elias Ferreira <edusf> | ||||
Component: | qemu-kvm | Assignee: | Marcelo Tosatti <mtosatti> | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.3 | CC: | acathrow, areis, bsarathy, dyasny, juzhang, mkenneth, virt-maint | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-10-16 14:31:45 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
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 (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. > > 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.
Eduardo, closing the bug as insufficient data. If you can configure Windows Time Server, and still the synchronization fails, please reopen the bug. 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. |
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.