Skip to content

chore: Add CHANGELOG entry for serialization of full KVM MSR range #5817

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zulinx86 merged 1 commit into from
Apr 7, 2026
Merged

chore: Add CHANGELOG entry for serialization of full KVM MSR range #5817

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,11 @@ and this project adheres to
since the snapshot was taken. Users using `kvm-clock` that want to explicitly
advance the clock with `KVM_CLOCK_REALTIME` can opt back in using the new
`clock_realtime` flag in `LoadSnapshot` API.
- [#5738](https://github.com/firecracker-microvm/firecracker/pull/5738): Fixed
x86_64 snapshot serialization to cover the full KVM custom MSR range
(0x4b564d00-0x4b564dff) instead of a small subset. Previously, some KVM MSRs
such as MSR_KVM_ASYNC_PF_INT and MSR_KVM_ASYNC_PF_ACK were missing from
snapshots, which could cause issues on restore.

## [1.15.0]

Expand Down
Loading