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.

Description of problem:
Requested by email on the virt-docs list from Anand Nande <anande>, customer support:

On 12/14/2015 05:02 PM, Anand Nande wrote:
> Hi,
>
> It would be great to have a brief article/doc in RHEL-7.x that 
> explains $subject along-with
> * timeline of events when the hypervisor and guest clock change 
> (time-drift)
> * how can they be adjusted back? OR how are they currently adjusted 
> using RH recommended best-practices
>
> Something on the lines of :
>
> more like
>
> host-NTP -> host-date -> host-hwclock
>         |            `-> guest-hwclock -> guest-date (boot)
>         `~> boot_ns [?] -> guest-kvmclock ~> guest-date (runtime)
>
>
> I have not seen this state diagram defined anywhere in our docs or 
> upstream.
> We can take help of Marcelo Tosatti [mtosatti] in this.
>
> Regards
> --Anand




Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:

consider making this a standalone article as well.

Incorporating email from Anand Nande
====================

Something like : http://www.ovirt.org/images/3/3e/StorageLiveMigrationAPIDiagram3.png would be a great idea.

Also we will need to consider the state diagram when the following conditions occur:

    Timer Drift

    Rounding Errors

    Suspend / Resume

    Migration


======================