vmm: add info! message on graceful shutdown #7346
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This message makes it easier to confirm a successful shutdown when scanning logs during development and in production. If the message is missing and the last log entry is not an error, the most likely cause is a livelock (e.g. contention on a lock) introduced while developing new Cloud Hypervisor features. Signed-off-by: Philipp Schuster <[email protected]> On-behalf-of: SAP [email protected]
phip1611
force-pushed
the
upstream-chv-info-message-on-exit
branch
from
e939cc8 to
e6b1e51
Compare
rbradford
approved these changes
Sep 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This message makes it easier to confirm a successful shutdown when scanning logs during development as well as in production. If the message is missing and the last log entry is not an error, the most likely cause is a livelock (e.g. contention on a lock) introduced while developing new Cloud Hypervisor features.