Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1190248

Summary: qemu-kvm: backport rtc-reset-reinjection command
Product: Red Hat Enterprise Linux 6 Reporter: Marcelo Tosatti <mtosatti>
Component: qemu-kvmAssignee: Marcelo Tosatti <mtosatti>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7CC: chayang, jen, juzhang, mazhang, mkenneth, mtosatti, qzhang, rbalakri, rpacheco, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-kvm-0.12.1.2-2.453.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-22 06:09:01 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:
Bug Depends On:    
Bug Blocks: 1115340    

Description Marcelo Tosatti 2015-02-06 19:03:53 UTC
libvirt requires rtc-reset-reinjection command, backport it to RHEL6.7.x.

Comment 3 Jeff Nelson 2015-02-18 17:54:03 UTC
Fix included in qemu-kvm-0.12.1.2-2.453.el6

Comment 5 Qunfang Zhang 2015-02-26 08:46:13 UTC
Hi, Marcelo

What kind of test should be arranged to verify this bug?  Are kvm acceptance test and timer device function test enough? 

Thanks,
Qunfang

Comment 8 mazhang 2015-03-20 08:06:21 UTC
Reproduce this bug.

Host:
qemu-kvm-0.12.1.2-2.452.el6.x86_64
gpxe-roms-qemu-0.9.7-6.13.el6.noarch
qemu-kvm-debuginfo-0.12.1.2-2.452.el6.x86_64
qemu-img-0.12.1.2-2.452.el6.x86_64
qemu-kvm-tools-0.12.1.2-2.452.el6.x86_64
2.6.32-544.el6.x86_64

Guest:
Win7-64

Steps:
1. Boot vm by libvirt.

2. Save domain.
# virsh save vm-win7 /home/vm-win7-st0

3. Wait about 10 minutes.

4. Resume guest.
# virsh restore /home/vm-win7-st0

Guest clock spent ~30s to catch up host.


Verify this bug on qemu-kvm-0.12.1.2-2.458.el6.x86_64.

Steps:
1. Boot vm by libvirt.

2. Save domain.
# virsh save vm-win7 /home/vm-win7-state0

3. Wait about 10 minutes.

4. Resume guest.
# virsh restore /home/vm-win7-state0

5. Execute "rtc-reset-reinjection".
# virsh qemu-monitor-command vm-win7 '{"execute":"rtc-reset-reinjection"}'
{"return":{},"id":"libvirt-9"}

Wait ~300s guest clock not be synchronized, stay behind 10 minutes.

Test result was expected, so this bug has been fixed.

Comment 10 errata-xmlrpc 2015-07-22 06:09:01 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1275.html