Improve handling of TSC on snapshot/restore #1696

Activity

1. syntactically

   added

   lifecycle/confirmedBug is verified or proposal seems reasonableBug is verified or proposal seems reasonable

   area/APIRelated to the API or public interfaceRelated to the API or public interface

   on Jul 30, 2026
2. syntactically

   added the

   Enhancement

   issue type on Jul 30, 2026
3. jsturtevant commented on Aug 5, 2026

   

   jsturtevant

   on Aug 5, 2026

   Contributor

   More actions

   some disucssion here #991 (comment)
4. jsturtevant

   added a parent issue on Aug 5, 2026

   • Snapshot-First Sandbox Lifecycle #1268
5. github-project-automation

   added this to Hyperlight Roadmapon Aug 5, 2026
6. jsturtevant

   added this to the 1.0 milestone on Aug 5, 2026
7. ludfjig

   added a commit that references this issue on Nov 3, 2026

   Document guest TSC behavior across calls and restore

   ...

   9d8531c
8. ludfjig commented on Nov 3, 2026

   

   ludfjig

   on Nov 3, 2026

   Last edited by ludfjig

   Contributor

   More actions

   After restore, the guest TSC should equal its value in the snapshot on every backend. MSHV does this. KVM (#2014) and WHP hosts with TscAdjustSupport (#2021) don't.

   Other clocks, such as guest execution time, could be opt-in later.
9. ludfjig

   added sub-issues on Nov 3, 2026

   • Restore does not rewind the guest TSC on KVM #2014
   • Restore does not rewind the guest TSC on WHP #2021