This repository has been archived by the owner on Sep 22, 2020. It is now read-only.
doc: warn if VirtualBox loaded kernel extensions #19
Conversation
This file contains 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
Due to machyve/xhyve#9, following the README verbatim can (and just did, in my case), fault the system into a hard reboot. Since there isn't a lot of willingness upstream to address this in xhyve, the best we can do is warn here before a user stumbles into data loss (like I just did).
|
The warning should be in |
|
@jedsmith Do you think this is necessary to have with virtualbox 5.0 resolving the issues, and the warning in our README? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Due to machyve/xhyve#9, following the README verbatim can (and just did,
in my case), fault the system into a hard reboot. Since there isn't a
lot of willingness upstream to address this in xhyve, the best we can do
is warn here before a user stumbles into data loss (like I just did).