On Mon, 4 Jun 2012, Asias He wrote: > The queue size for virtio_blk is 256 and AIO_MAX is 32, we might be > short of available aio events if guest issues > 32 requests > simultaneously. Following error is observed when guest running stressed > I/O workload. > > Info: disk_image__read error: total=-11 > > To fix this, let's increase the aio events limit. > > Signed-off-by: Asias He <[email protected]> > --- > tools/kvm/disk/core.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tools/kvm/disk/core.c b/tools/kvm/disk/core.c > index ed338e7..d1d2d59 100644 > --- a/tools/kvm/disk/core.c > +++ b/tools/kvm/disk/core.c > @@ -6,7 +6,7 @@ > #include <sys/eventfd.h> > #include <sys/poll.h> > > -#define AIO_MAX 32 > +#define AIO_MAX 256 > > int debug_iodelay;
Is there any downside to bumping up the limit? Ingo? -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
