Skip to content

1.6 cvm guest vsm: add logging around vtl protection violations via the g… #1547

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.

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

Conversation

sluck-msft
Copy link
Contributor

…uest memory object (#1544)

Adds some handling of page faults in the path of accessing memory via a guest memory object to detect certain access failure types, including VTL 1 protection violations for CVMs. For now, this change only logs the type of access failure for purposes of debugging and triage, but does not specifically try to handle these access failures.

Tested:
SNP +/- guest vsm boots
TVM + guest vsm boots

…uest memory object (microsoft#1544)

Adds some handling of page faults in the path of accessing memory via a
guest memory object to detect certain access failure types, including
VTL 1 protection violations for CVMs. For now, this change only logs the
type of access failure for purposes of debugging and triage, but does
not specifically try to handle these access failures.

Tested:
SNP +/- guest vsm boots
TVM + guest vsm boots
@sluck-msft sluck-msft requested a review from a team as a code owner June 19, 2025 18:11
@github-actions github-actions bot added the release_2505 Targets the release/2505 branch. label Jun 19, 2025
@sluck-msft sluck-msft changed the title cvm guest vsm: add logging around vtl protection violations via the g… 1.6 cvm guest vsm: add logging around vtl protection violations via the g… Jun 20, 2025
@sluck-msft sluck-msft merged commit e1dde6d into microsoft:release/2505 Jun 20, 2025
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_2505 Targets the release/2505 branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants