Raise BLOCKIF_IOV_MAX to 128 #178
Open
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
this fixes a crash on windows and its based on the same upstream fix: https://reviews.freebsd.org/D10581 Signed-off-by: mike-pt <[email protected]>
|
Any chance we can merge this? Can't boot windows guests without this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 fixes a crash on windows and its based on the same upstream fix.
Windows uses at least 67 and qemu alsosupports 128 hence why we need to raise this.
Fix on bhyve:
https://reviews.freebsd.org/D10581
Signed-off-by: mike-pt [email protected]