Re: [pve-devel] Proxmox Org on GitHub

2020-07-22 Thread Kamil Trzciński
The following users were invited. Please let me know when you got access. I also changed public e-mail and billing e-mail to `t.lamprecht`. Kamil On Tue, Jul 21, 2020 at 5:09 PM Martin Maurer wrote: > Hello Kamil, > > Thanks, here is the list of the requested GitHub accounts. > > https://gith

Re: [pve-devel] Proxmox Org on GitHub

2020-07-22 Thread Thomas Lamprecht
On 22.07.20 11:07, Kamil Trzciński wrote: > The following users were invited. > > Please let me know when you got access. Thanks, I got access and Fabian too. Wolfgang is on vacation this week, so we may not here from him until Monday. Thank you. > > I also changed public e-mail and billing e

[pve-devel] [PATCH docs 2/2] pvecm: Add output for delnode

2020-07-22 Thread Dominic Jäger
The output of "pvecm delnode someNode" is "Killing node X". Even though this only says something about an attempt and not about success, it is not "no output is returned". Signed-off-by: Dominic Jäger --- pvecm.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pvecm.

[pve-devel] [PATCH docs 1/2] pvecm: Add required -r to rm

2020-07-22 Thread Dominic Jäger
/etc/corosync/* includes the directory uidgid.d. Consequentlly, a correct rm call requires -r. Signed-off-by: Dominic Jäger --- pvecm.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pvecm.adoc b/pvecm.adoc index 4bf2f59..9207571 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @

Re: [pve-devel] [PATCH docs 1/2] pvecm: Add required -r to rm

2020-07-22 Thread Thomas Lamprecht
On 22.07.20 12:20, Dominic Jäger wrote: > /etc/corosync/* includes the directory uidgid.d. > Consequentlly, a correct rm call requires -r. Does leaving this directory left-over causes any issues? IIRC, I omit the "-r" explicitly as there can be also a directory from a qdevice or other ones, which

[pve-devel] applied: [PATCH docs v1] Add section with more infos about ZFS RAID levels

2020-07-22 Thread Thomas Lamprecht
On 21.07.20 14:58, Aaron Lauterer wrote: > This new section explains the performance and failure properties of > mirror and RAIDZ VDEVs as well as the "unexpected" higher space usage by > ZVOLs on a RAIDZ. > > Signed-off-by: Aaron Lauterer > --- > > draft->v1: > * incorporate Stoikos suggestions

[pve-devel] applied: [PATCH pve-docs] qm: IO Thread: fix typo and reword section

2020-07-22 Thread Thomas Lamprecht
On 21.07.20 09:21, Dylan Whyte wrote: > Fix typo 'isks' => 'disks' > Reword section for better readability. > > Signed-off-by: Dylan Whyte > --- > qm.adoc | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > applied, thanks! ___ pve-deve

[pve-devel] [PATCH lxc 1/2] update lxc to include fixes for cgroupv2 setups

2020-07-22 Thread Stoiko Ivanov
This commit fast-forwards 7 commits from upstream/master. The first commit (partially) fixes a missing apparmor rule for /proc/sys/kernel/random/boot_id) The last commit fixes running containers in pure cgroupv2 environments (by premounting cgroup2). It contains one other fix for a netlink bug, w

[pve-devel] [PATCH lxc 2/2] apparmor: add rule for allowing remount of boot_id

2020-07-22 Thread Stoiko Ivanov
commit 863845075d3f77d27c91bd9f47d2f8ddc4867bd5 in upstream only partially fixes the apparmor deny for mounting boot_id (used for example for identifying different boots with `journalctl`) inside the container. Tested by editing the profile and replacing it disregarding the cache: `apparmor_parser

[pve-devel] [PATCH lxc 0/2] fix apparmor rules and improve cgroupv2 experience

2020-07-22 Thread Stoiko Ivanov
This patchset addresses 2 minor inconveniences I ran into, while running my host with 'systemd.unified_cgroup_hierarchy=1': * apparmor mount denies for '/proc/sys/kernel/random/boot_id' (this happens irrespective of the cgroup-layout * having to add `lxc.init.cmd: /lib/systemd/systemd systemd.

Re: [pve-devel] [PATCH v2 qemu-server] Fix #2728: die/warn if target is not a replication target when live-migrating

2020-07-22 Thread Fabian Ebner
Ping for this patch Am 18.05.20 um 09:37 schrieb Fabian Ebner: Signed-off-by: Fabian Ebner --- Changes from v1: * die/warn depending on force (thanks to Thomas and Aaron for the suggestion) * don't die/warn if VM is not replicated at all PVE/API2/Qemu.pm | 13 + 1 fi

Re: [pve-devel] [PATCH lxc 2/2] apparmor: add rule for allowing remount of boot_id

2020-07-22 Thread Thomas Lamprecht
On 22.07.20 13:05, Stoiko Ivanov wrote: > commit 863845075d3f77d27c91bd9f47d2f8ddc4867bd5 in upstream only partially > fixes the apparmor deny for mounting boot_id (used for example for identifying > different boots with `journalctl`) inside the container. > > Tested by editing the profile and rep

Re: [pve-devel] [PATCH lxc 2/2] apparmor: add rule for allowing remount of boot_id

2020-07-22 Thread Stoiko Ivanov
On Wed, 22 Jul 2020 13:51:19 +0200 Thomas Lamprecht wrote: > On 22.07.20 13:05, Stoiko Ivanov wrote: > > commit 863845075d3f77d27c91bd9f47d2f8ddc4867bd5 in upstream only partially > > fixes the apparmor deny for mounting boot_id (used for example for > > identifying > > different boots with `jou

Re: [pve-devel] [PATCH lxc 2/2] apparmor: add rule for allowing remount of boot_id

2020-07-22 Thread Thomas Lamprecht
On 22.07.20 13:59, Stoiko Ivanov wrote: > On Wed, 22 Jul 2020 13:51:19 +0200 > Thomas Lamprecht wrote: > >> On 22.07.20 13:05, Stoiko Ivanov wrote: >>> commit 863845075d3f77d27c91bd9f47d2f8ddc4867bd5 in upstream only partially >>> fixes the apparmor deny for mounting boot_id (used for example for

Re: [pve-devel] [PATCH lxc 2/2] apparmor: add rule for allowing remount of boot_id

2020-07-22 Thread Stoiko Ivanov
On Wed, 22 Jul 2020 14:09:09 +0200 Thomas Lamprecht wrote: > On 22.07.20 13:59, Stoiko Ivanov wrote: > > On Wed, 22 Jul 2020 13:51:19 +0200 > > Thomas Lamprecht wrote: > > > >> On 22.07.20 13:05, Stoiko Ivanov wrote: > >>> commit 863845075d3f77d27c91bd9f47d2f8ddc4867bd5 in upstream only par