If you're like me, you've spend the last year wondering why your KVM based virtualization is horribly slow when doing IO. You've tried twiddling every available option in your BIOS, you've mucked about with hdparm and libvirt/qemu settings, and you've run more timed installs of RHEL 5 than you care to admit.
If you're also like me, you tried using ext4 instead of BTRFS to store your guest images today, and found that this resolved your issue.
The relevant bz appears to be here.
The lesson I learned today is to blame experimental or newer features before anything else (though its doubtful I'll remember this next time).
Subscribe to:
Post Comments (Atom)
Actually, I first found this in F13. I haven't used BTRFS since then because of this. I think this really sucks that even in F15, it still isn't fixed, and they keep talking about pushing BTRFS out as the default file system soon in Fedora?
ReplyDeleteHave you seen this article about slow IO?
ReplyDeletehttp://www.ilsistemista.net/index.php/virtualization/11-kvm-io-slowness-on-rhel-6.html
@Anonymous: I have! I was running though a lot of benchmarking like that, too, assuming that could be my issue as well. but it turned out to be BTRFS. Its possible I could tune things further by adjusting the cache, but I'm happy enough where it is now.
ReplyDeleteDoom: http://fedoraproject.org/wiki/Features/F17BtrfsDefaultFs
ReplyDelete