Hi, I think this is more a "is it time to rethink the default fs.aio-max-nr than a qemu problem. In general pick any limit and you will be able to create a testcase breaking it. Are all these bugs ... do we need to set all limits to unlimited - I'm sure you agree not to.
Anyway I agree to Viktor that "I would also suggest that the system default setting is increased" as this could be hit by many other aio workload. But that also means it has to be a broader discussion. Kernel default: fs/aio.c:194:unsigned long aio_max_nr = 0x10000; /* system wide maximum number of aio requests */ Options: 1. minor kernel patch as ubuntu delta 2. a file in /etc/sysctl.d/ in package procps 3. a file in /etc/sysctl.d/ in another package 4. deny As it is a kernel limit and a kernel default value I'll add a kernel and a procps task for discussion with kernel and foundations Team. They also might have experience on those "limit raising" cases and how they were handled. Related docs: https://www.kernel.org/doc/Documentation/sysctl/fs.txt http://man7.org/linux/man-pages/man2/io_setup.2.html ** Also affects: procps (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717224 Title: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1717224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
