Skip to content
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

qemu: Use "unsafe" cache if direct IO is not supported #119

Merged
merged 1 commit into from
Oct 1, 2014
Merged

qemu: Use "unsafe" cache if direct IO is not supported #119

merged 1 commit into from
Oct 1, 2014

Conversation

penberg
Copy link
Contributor

@penberg penberg commented Sep 15, 2014

ZFS on Linux, for example, does not support direct I/O. Probe for DIO
support before starting a new QEMU instance and fall-back to "unsafe"
caching if it's not supported. Suggested by Tomek.

Fixes #118.

Signed-off-by: Pekka Enberg penberg@iki.fi

ZFS on Linux, for example, does not support direct I/O. Probe for DIO
support before starting a new QEMU instance and fall-back to "unsafe"
caching if it's not supported. Suggested by Tomek.

Fixes #118.

Signed-off-by: Pekka Enberg <penberg@iki.fi>
@acolyer
Copy link

acolyer commented Oct 1, 2014

I had the same launch failure due to use of ecryptfs, and confirm this patch fixes the problem for me.

penberg added a commit that referenced this pull request Oct 1, 2014
qemu: Use "unsafe" cache if direct IO is not supported
@penberg penberg merged commit 613eb6e into cloudius-systems:master Oct 1, 2014
@penberg penberg deleted the qemu/direct-io branch October 1, 2014 11:47
@penberg
Copy link
Contributor Author

penberg commented Oct 1, 2014

@acolyer Thank you for testing! 🍻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

capstan doesnt start qemu, invalid argument
2 participants