Re: [pve-devel] [PATCH V2 pve-manager 3/3] add sdn icons

>>FYI: patch is corrupt above, a extra newline seems to got into here, >>breaking the long line such tha git cannot work with it anymore. >> >>Applies fine once the newline is deleted. maybe is it a bug with git-email encoding ? I can apply it fine locally. I have attached the patch into this

[pve-devel] [PATCH pve-manager] API2: Network: display vnets in any_bridge

Signed-off-by: Alexandre Derumier --- PVE/API2/Network.pm | 25 + 1 file changed, 25 insertions(+) diff --git a/PVE/API2/Network.pm b/PVE/API2/Network.pm index 4c691879..d727a2fc 100644 --- a/PVE/API2/Network.pm +++ b/PVE/API2/Network.pm @@ -18,6 +18,7 @@ use base qw(PVE:

Re: [pve-devel] [PATCH v3 qemu-server] vzdump: move include logic for volumes to method

On 17.03.20 15:34, Fabian Grünbichler wrote: On March 16, 2020 4:44 pm, Aaron Lauterer wrote: Move the logic which volumes are included in the backup job to its own method and adapt the VZDump code accordingly. This makes it possible to develop other features around backup jobs. Signed-off-by:

Re: [pve-devel] Ceph Octopus is out!

Hi, On 3/24/20 1:53 PM, Victor Hooi wrote: > Hi, > > So I just saw the release annoucement for Ceph Ocotpus: > > https://ceph.io/releases/v15-2-0-octopus-released/ > > YAY! =) > > So I'm going to ask the question - when will this be in Proxmox? =) (e.g. > in Ceph Testing). I'd guess we get so

[pve-devel] Ceph Octopus is out!

Hi, So I just saw the release annoucement for Ceph Ocotpus: https://ceph.io/releases/v15-2-0-octopus-released/ YAY! =) So I'm going to ask the question - when will this be in Proxmox? =) (e.g. in Ceph Testing). Thanks, Victor ___ pve-devel mailing li

Re: [pve-devel] Bug in Promox's OVMF implementation - resolution is garbled on MacOS, unless you reset machine on each boot?

Hi, I can confirm that yes - I do have a efidisk set up. The MacOS on Proxmox tutorial which I followed actually talks explicitly about setting up the efidisk. The graphical glitch does appear to be some bug betw

[pve-devel] [PATCH docs] pvecm.adoc: qdevice: Adapt, update and make it clearer

Naming the whole mechanism and one of the daemons the same makes it easy to mix up the two. This patch aims to make the whole understanding of the QDevice and it's parts easier by * describing use cases at the beginning * making the distinction between the QDevice mechanism and qdevice daemon clea

[pve-devel] [PATCH cluster] pvecm: qdevice setup: fix check for odd node count

With Perl 5.26 the behavior of `scalar(%hash)` changed [0] causing the check for odd numbers to never evaluate to true. Allowing odd sized clusters to set up a QDevice. The algorithm was not changed to LMS if forced to still create the QDevice. Instead of showing the bucket info of the referenced

Re: [pve-devel] [PATCH docs] pvecm.adoc: qdevice: Adapt, update and make it clearer

Well, as it turns out, the whole (N-1) section is valid and our QDevice setup code had a bug. Will send a v2 with that section integrated. On 3/24/20 3:52 PM, Aaron Lauterer wrote: Naming the whole mechanism and one of the daemons the same makes it easy to mix up the two. This patch aims to mak

[pve-devel] Kernel 5.6/5.7 in Proxmox (Or - what is the lead-time for kernels to ship in Proxmox).

Hi, I'm running Proxmox on a AMD Rome box - keen to do some testing on more recent kernel builds, due to the performance improvements and better power/temperature monitoring. Proxmox is currently on kernel 5.4 - curious when the 5.6 kernel (released) might land? And what sort of lead-time would