On Mon, 2015-03-02 at 14:22 +, Ian Campbell wrote:
On Fri, 2015-02-27 at 17:53 +, Andrew Cooper wrote:
XenServer's VM density testing uncovered a regression when moving from
sysvinit to systemd where the file descriptor limit dropped from 4096 to
1024. (XenServer had previously
On 02/03/15 14:22, Ian Campbell wrote:
On Fri, 2015-02-27 at 17:53 +, Andrew Cooper wrote:
XenServer's VM density testing uncovered a regression when moving from
sysvinit to systemd where the file descriptor limit dropped from 4096 to
1024. (XenServer had previously inserted a ulimit
On Fri, 2015-02-27 at 17:53 +, Andrew Cooper wrote:
XenServer's VM density testing uncovered a regression when moving from
sysvinit to systemd where the file descriptor limit dropped from 4096 to
1024. (XenServer had previously inserted a ulimit statement into its
initscripts.)
One
On Mon, 2015-03-02 at 14:24 +, Andrew Cooper wrote:
On 02/03/15 14:22, Ian Campbell wrote:
On Fri, 2015-02-27 at 17:53 +, Andrew Cooper wrote:
XenServer's VM density testing uncovered a regression when moving from
sysvinit to systemd where the file descriptor limit dropped from 4096
XenServer's VM density testing uncovered a regression when moving from
sysvinit to systemd where the file descriptor limit dropped from 4096 to
1024. (XenServer had previously inserted a ulimit statement into its
initscripts.)
One solution is to use LimitNOFILE=4096 in xenconsoled.service to
Andrew Cooper writes ([PATCH v5] tools/xenconsoled: Increase file descriptor
limit):
XenServer's VM density testing uncovered a regression when moving from
sysvinit to systemd where the file descriptor limit dropped from 4096 to
1024. (XenServer had previously inserted a ulimit statement into
