@xnox markig procps as wontfix since the kernel fix seems to be
sufficient.
** Changed in: procps (Ubuntu)
Status: New => Won't Fix
** Changed in: procps (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: procps (Ubuntu Artful)
Status: New => Won't Fix
--
You
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1717224
Title:
virsh start of virtual guest
Commit 2a8a98673c13 has been in Xenial and Artful for some time now.
Can you confirm this bug is now resolved with the latest updates.
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Released
** No longer affects: linux (Ubuntu Zesty)
** No longer affects: procps (Ubuntu Zesty)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1717224
Title:
virsh start of
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1717224
Title:
virsh start of virtual guest domain
Zesty is end of life.
** Changed in: procps (Ubuntu Zesty)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1717224
Title:
virsh start of
zesty is End Of Life
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1717224
Title:
virsh start
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1717224
Title:
virsh start of virtual guest domain fails
Commit 2a8a98673c13 has been in Xenial since Ubuntu-4.4.0-98.121. If
you can confirm the bug is now fixed since this kernel version, I'll
mark the bug as Fix Released.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps
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
Hi Scott,
the howto is mixed for Desktop users, Server users and selective upgrades.
For your case you only need the most simple case which would be:
Essentially you want to:
# Check - all other updates done (to clear the view)
$ apt list --upgradable
Listing... Done
# Enable proposed for z on
Commit 2a8a98673c13 is in Xenial -proposed, kernel version:
Ubuntu-4.4.0-98.121. It looks like you tested with version
4.4.0-62-generic. Can you try testing with the -proposed Xenial kernel:
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.
** Changed in: ubuntu-z-systems
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1717224
Title:
virsh start of virtual guest domain
Actually, Artful already has commit 2a8a98673c13. It was pulled in for
bug 1718397. It looks like Xenial and Zesty will also get that commit
via that bug.
Can you test Artful and/or X/Y -proposed to see if this bug is resolved
with that commit?
** Also affects: procps (Ubuntu Xenial)
I'll build an Artful test kernel with commit 2a8a98673c13 and post it
shortly.
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury
Thanks for checking cborntra!
The referred patch is in 4.14-rc1.
I'm not so sure on backports of this, but at least for the Artful and HWE
kernel of 4.13 this would be good to have.
@Kernel Team - could you take a look and consider 2a8a9867 for our 4.13
kernels?
@Xnox - changing the global
Yeah, such a change needs some reasoning and since (at least to me) it
is not yet clear how such few guests consume so much aio resources we
need to check that.
If you can provide:
1. the increase per guest spawned
2. are all your guests having more or less the same xml or do some have more
Any updates? Have you been able to monitor fs.aio-nr exhaustion?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1717224
Title:
virsh start of virtual guest domain fails
** Changed in: ubuntu-z-systems
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1717224
Title:
virsh start of virtual guest domain fails
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
OTOH I wonder to some extend how you exceded the 65k with "just" 18 guests.
Not strictly required, but it might be very interesting before your system
becomes unavailable to track:
$ sysctl fs.aio-nr
while starting the guests. How much get added per guest, would the settle down
after the guest
21 matches
Mail list logo
