-
Notifications
You must be signed in to change notification settings - Fork 134
-
Notifications
You must be signed in to change notification settings - Fork 134
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
Fast reboot not blocked on change of garded resources #199
Comments
I'm not really sure how we're supposed to fix this since we don't really parse the guard partition at all in skiboot. Suppose we could force a full re-IPL if the host does any flash writes? Seems a bit heavyweight. |
oohal <notifications@github.com> writes:
I'm not really sure how we're supposed to fix this since we don't
really parse the guard partition at all in skiboot. Suppose we could
force a full re-IPL if the host does any flash writes? Seems a bit
heavyweight.
Maybe any flash writes to the GUARD partition?
I don't have a good answer unfortunately, probably why it's sat as a
github issue unaddressed for so long :)
…--
Stewart Smith
OPAL Architect, IBM.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If we clear gard records, we still do a fast-reboot - which may not get the garded hardware back.
The text was updated successfully, but these errors were encountered: