Hi Heinz-Werner,
thanks for the ping.
I think we agreed back then that the config itself is a Ubuntu wide
thing - but I haven't seen any discussions on procps or in general to
lift it. But then as I outlined in comment #7 any limit can be too low.
I'll set the KVM task to won't fix to clearly mark it as "not a kvm
task".
The fix that you need thou is the kernel change to account correctly - so that
part of the question goes to the Kernel Team if the change that was proposed
back then was actually released.
@Joseph - we clearly passed the number, but was the change released with it?
** Changed in: kvm (Ubuntu)
Status: Confirmed => Won't Fix
** No longer affects: kvm (Ubuntu Xenial)
** No longer affects: kvm (Ubuntu Zesty)
** No longer affects: kvm (Ubuntu Artful)
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
