KVM: use cache=unsafe
authorAlexander Graf <agraf@suse.de>
Fri, 30 Sep 2011 09:49:14 +0000 (11:49 +0200)
committerAdrian Schröter <adrian@suse.de>
Sat, 1 Oct 2011 07:31:37 +0000 (09:31 +0200)
commit7aefa9ee8dae2991cee7214baf32ef78e886a8ff
tree56d97598403d0a083cdf38a3b8293b08dde0f14b
parentd674a366972b6346bf997e42fbd256f90a73fd15
KVM: use cache=unsafe

When running with raw image files, we're not passing in any cache= parameter,
making KVM use the default. Unfortunately, the default is horribly slow and
way too secure about data which doesn't matter for our build use case.

So instead, we should just use cache=unsafe, rendering flush requests from the
guest as nops, making builds faster by many times.

Signed-off-by: Alexander Graf <agraf@suse.de>
build