On 05/24/2010 12:47 AM, Stefan Hajnoczi wrote:
> On Sun, May 23, 2010 at 5:18 PM, Antoine Martin <antoine@xxxxxxxxxxxxx> wrote:
>> Why does it work in a chroot for the other options (aio=native, if=ide, etc)
>> but not for aio!=native??
>> Looks like I am misunderstanding the semantics of chroot...
>
> It might not be the chroot() semantics but the environment inside that
> chroot, like the glibc. Have you compared strace inside and outside
> the chroot?
Reverting to a static build also fixes the issue: aio=threads works.
Definitely something fishy going on with glibc library loading.
(I've checked glibc, libaio were up to date in the chroot - nothing
blatant in the strace)
Can someone explain the aio options?
All I can find is this:
# qemu-system-x86_64 -h | grep -i aio
[,addr=A][,id=name][,aio=threads|native]
I assume it means the aio=threads emulates the kernel's aio with
separate threads? And is therefore likely to be slower, right?
Is there a reason why aio=native is not the default? Shouldn't
aio=threads be the fallback?
Cheers
Antoine
>
> Stefan
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
