Bug 1524412
| Summary: | KVM clocks must not count time while host is suspended | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alan Jenkins <alan.christopher.jenkins> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 27 | CC: | airlied, alan.christopher.jenkins, bskeggs, ewk, fedora-kernel-kvm, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, labbott, linville, mchehab, mikhail.zabaluev, mjg59, steved |
| Target Milestone: | --- | Flags: | jforbes:
needinfo?
|
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-08-29 15:23:43 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: | |||
|
Description
Alan Jenkins
2017-12-11 12:52:43 UTC
Sorry, wrong version. 4.13.16-302.fc27.x86_64 was the kernel used on the guest 4.14.3-300.fc27.x86_64 is the kernel used on the host, which I would say is more culpable. qemu-kvm-2.10.1-1.fc27.x86_64 is also used on the host. It is also possible to test "sleep 30". In my test this returns immediately after resume (assuming the sleep lasted >30s), mirroring the timeouts shown in the logs. strace shows that sleep is using nanosleep(), which refers to CLOCK_MONOTONIC on linux. Fedora isn't really doing anything special here so this is best tracked as a feature request/bug with the upstream KVM project. That makes sense :). Thanks for triage. I wanted to write this up, but I don't think I have time right now, to reduce this report to the qemu level and install upstream qemu etc. (It's annoying even to set "init=/bin/bash". For some reason, running qemu-kvm specifying `-m` and `-drive`, I can boot the system but the GRUB menu doesn't accept keyboard input. Linux is fine once it's booted. qemu-kvm is version 2.10.1-1.fc27.x86_64). CPU is Intel i5-5300U. We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.15.3-300.f27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. Bugzilla really wants me to confirm. So yes, as late as yesterday I'm still getting expired watchdog timers when suspending the host, and my kernel is: 4.15.9-300.fc27.x86_64 I observe this in a Fedora 28 Atomic guest VM with ptp_kvm configured as a clock source for chronyd: refclock PHC /dev/ptp0 poll 3 dpoll -2 offset 0 The host is also Fedora 28 running chronyd. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.17.7-100.fc27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 28, and are still experiencing this issue, please change the version to Fedora 28. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. |