[pve-devel] [PATCH common] fix #1938: /proc/mounts too long

2018-10-02 Thread David Limbeck
Signed-off-by: David Limbeck --- Would a bigger filesize (1M or more) be more approriate? src/PVE/ProcFSTools.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/PVE/ProcFSTools.pm b/src/PVE/ProcFSTools.pm index 80c0425..1b98b1e 100644 --- a/src/PVE/ProcFSTools.pm +++

[pve-devel] [PATCH v2 container 0/2] feature flags

2018-10-02 Thread Wolfgang Bumiller
This series adds a 'features' config option adding support for nesting, mounting and some quirks the user should know about when dealing with these settings. This makes use of the new apparmor profile generation & namespacing feature in lxc. This is updated with Thomas' feedback: - Dropped the

[pve-devel] [PATCH v2 container 2/2] add feature flags using apparmor profile generation

2018-10-02 Thread Wolfgang Bumiller
Signed-off-by: Wolfgang Bumiller --- Changes to v1: * In the start code now $unprivileged now means just that, regardless of whether the $conf->{unprivileged} option or a custom id map is set. $custom_idmap is now only used where required. * Access to 'features' is now limited to

[pve-devel] [PATCH v2 container 1/2] config: whitelist new apparmor related config keys

2018-10-02 Thread Wolfgang Bumiller
Signed-off-by: Wolfgang Bumiller --- No changes in this patch src/PVE/LXC/Config.pm | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/PVE/LXC/Config.pm b/src/PVE/LXC/Config.pm index ac0859a..c21b69e 100644 --- a/src/PVE/LXC/Config.pm +++ b/src/PVE/LXC/Config.pm @@ -414,6 +414,8 @@ my

[pve-devel] [PATCH v4 pve-manager] API2 : Network : add network config reload

2018-10-02 Thread Alexandre Derumier
This add a new api to online reload networking configuration with ifupdown2. This work with native ifupdown2 modules, as ifupdown2 have interface dependency relationships. Some specific interfaces options can't be reloaded online (because kernel don't implement it), it this case, we ifdown/ifup

Re: [pve-devel] Using rEFInd with Proxmox VE

2018-10-02 Thread Andreas Steinel
On Mon, Oct 1, 2018 at 7:40 PM Fabian Grünbichler wrote: > we just recently discussed this again internally, and we will come up > with some kind of solution in time for PVE 6.x (one way or another, we > still need to test all the possible ways to tackle this before deciding > which way to go).

Re: [pve-devel] [RFC/PATCH installer 0/4] don't create swap on ZFS as default

2018-10-02 Thread Andreas Steinel
On Tue, Oct 2, 2018 at 8:10 AM Dietmar Maurer wrote: > > I thought we all agreed that swap does not make sense on > high memory system? Very true. I'd still suggest - as I did for many years on the forums - to install zram. This can be done automatically and then you have some swap, compressed

Re: [pve-devel] [RFC/PATCH installer 0/4] don't create swap on ZFS as default

2018-10-02 Thread Dietmar Maurer
I thought we all agreed that swap does not make sense on high memory system? > On Mon, Oct 01, 2018 at 07:43:41PM +0200, Fabian Grünbichler wrote: > > > > wouldn't it make more sense to create a swap partition on all boot vdevs > > instead? if you need swap, this is very cumbersome to do after >