On 03/08/2010 04:25 PM, Dustin Kirkland wrote:
On Mon, Mar 8, 2010 at 3:48 AM, Avi Kivity<a...@redhat.com> wrote:
On 03/08/2010 11:48 AM, Bernhard Schmidt wrote:
On Mon, Mar 08, 2010 at 11:10:29AM +0200, Avi Kivity wrote:
Are there any potential pitfalls?
It won't work well unless running on a block device (partition or LVM).
What does "work well" mean in this context? Potential dataloss?
No, it becomes synchronous (=extra slow).
But for this to happen, the user would have had to consciously enter
into the situation by creating/using a non block device,
non-pre-allocated backing disk AND specify the aio=native option,
correct?
I thought there was some autodetection involved, but perhaps I just
imagined it.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
