Re: [pve-devel] [PATCH v2 qemu-server 2/2] fix clone_disk failing for nonexistent cloudinit disk

2020-10-06 Thread Mira Limbeck
On 10/5/20 5:35 PM, Thomas Lamprecht wrote: On 28.09.20 10:36, Mira Limbeck wrote: After migration or a rollback the cloudinit disk might not be allocated, so volume_size_info() fails. As we override the value anyway for cloudinit and efi disks simply move the volume_size_info() call into the

Re: [pve-devel] [PATCH v2 qemu-server 2/2] fix clone_disk failing for nonexistent cloudinit disk

2020-10-06 Thread Mira Limbeck
On 10/6/20 10:56 AM, Mira Limbeck wrote: On 10/5/20 5:35 PM, Thomas Lamprecht wrote: On 28.09.20 10:36, Mira Limbeck wrote: After migration or a rollback the cloudinit disk might not be allocated, so volume_size_info() fails. As we override the value anyway for cloudinit and efi disks simply

[pve-devel] [PATCH pve-manager] pvestatd: stream host pressure counters

2020-10-06 Thread Alexandre Derumier
Signed-off-by: Alexandre Derumier --- PVE/Service/pvestatd.pm | 4 1 file changed, 4 insertions(+) diff --git a/PVE/Service/pvestatd.pm b/PVE/Service/pvestatd.pm index 5e533ca3..238c36ae 100755 --- a/PVE/Service/pvestatd.pm +++ b/PVE/Service/pvestatd.pm @@ -161,12 +161,16 @@ sub update_node

[pve-devel] [PATCH pve-common 0/1] ProcFSTools: add read_pressure

2020-10-06 Thread Alexandre Derumier
Hi, I'm currently working on vm load balancing scheduler. This patch add new pressure counters, very usefull to known if a node is overloaded, with more granularity than loadaverage. Alexandre Derumier (1): ProcFSTools: add read_pressure src/PVE/ProcFSTools.pm | 18 ++ 1 fil

[pve-devel] [PATCH pve-common 1/1] ProcFSTools: add read_pressure

2020-10-06 Thread Alexandre Derumier
read new /proc/pressure/(cpu,disk,io) introduced in kernel 4.20. This give more granular informations than loadaverage. Signed-off-by: Alexandre Derumier --- src/PVE/ProcFSTools.pm | 18 ++ 1 file changed, 18 insertions(+) diff --git a/src/PVE/ProcFSTools.pm b/src/PVE/ProcFSToo

Re: [pve-devel] [PVE-User] Proxmox Backup Server (beta)

2020-10-06 Thread Lee Lists
Hi, I'm trying to build proxmox backup server from source, but the build failed in compiling zstd lib bindings. Any clues ? Thanks, Jurgen Fresh pxar v0.6.1 (/root/pxar) Fresh proxmox-fuse v0.1.0 (/root/proxmox-fuse) Fresh hyper v0.13.8 Compiling proxmox v0.4.2 (/root/pr

[pve-devel] [PATCH v2 qemu-server 5/7] api: add handling for new boot order format

2020-10-06 Thread Stefan Reiter
The API is updated to handle the deprecation correctly, i.e. when updating the 'order' attribute, the old 'legacy' (default_key) values are removed (would now be ignored anyway). When removing a device that is in the bootorder list, it will be removed from the aforementioned. Note that non-existin

[pve-devel] [PATCH v2 qemu-server 1/7] fix indentation

2020-10-06 Thread Stefan Reiter
Signed-off-by: Stefan Reiter --- PVE/QemuServer.pm | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm index 2747c66..bd59616 100644 --- a/PVE/QemuServer.pm +++ b/PVE/QemuServer.pm @@ -3468,24 +3468,24 @@ sub config_to_c

[pve-devel] [PATCH v2 qemu-server 4/7] fix #3010: add 'bootorder' parameter for better control of boot devices

2020-10-06 Thread Stefan Reiter
(also fixes #3011) Deprecates the old-style 'boot' and 'bootdisk' options by adding a new 'order=' subproperty to 'boot'. This allows a user to specify more than one disk in the boot order, helping with newer versions of SeaBIOS/OVMF where disks without a bootindex won't be initialized at all (br

[pve-devel] [PATCH v2 qemu-server 3/7] add new 'boot' property format and introduce legacy conversion helpers

2020-10-06 Thread Stefan Reiter
The format is unused in this commit, but will replace the current string-based format of the 'boot' property. It is included since the parameter of bootorder_from_legacy follows it. Two helper methods are introduced: * bootorder_from_legacy: Parses the legacy format into a hash closer to what

[pve-devel] [PATCH v2 manager 7/7] ui: improve boot order editor

2020-10-06 Thread Stefan Reiter
The new boot order property can express many more scenarios than the old one. Update the editor so it can handle it. Features a grid with all supported boot devices which can be reordered using drag-and-drop, as well as toggled on and off with an inline checkbox. Support for configs still using t

[pve-devel] [PATCH v2 0/7] Improve boot device/order configuration

2020-10-06 Thread Stefan Reiter
The goal of the series is to modernize boot order selection by allowing the user to specify arbitrary VM disks and devices in any order. Fixes #3010 and #3011. First patch is a standalone cleanup. Tests are seperated into extra patches. v2: * split qemu-server changes into seperate patches (hence

[pve-devel] [PATCH v2 qemu-server 6/7] cfg2cmd: add tests for new boot order property

2020-10-06 Thread Stefan Reiter
Signed-off-by: Stefan Reiter --- test/cfg2cmd/bootorder-empty.conf | 16 +++ test/cfg2cmd/bootorder-empty.conf.cmd | 38 +++ test/cfg2cmd/bootorder.conf | 16 +++ test/cfg2cmd/bootorder.conf.cmd | 38 +++ 4 files

[pve-devel] [PATCH v2 qemu-server 2/7] cfg2cmd: add test for legacy-style bootorder

2020-10-06 Thread Stefan Reiter
Signed-off-by: Stefan Reiter --- test/cfg2cmd/bootorder-legacy.conf | 17 test/cfg2cmd/bootorder-legacy.conf.cmd | 38 ++ 2 files changed, 55 insertions(+) create mode 100644 test/cfg2cmd/bootorder-legacy.conf create mode 100644 test/cfg2cmd/bootorder-le

[pve-devel] [PATCH libspice-server] update spice to 0.14.3 and add patches for CVE-2020-14355

2020-10-06 Thread Oguz Bektas
the original email is in oss-security[0], patches are from upstream gitlab. (commits linked in the email) removed the already applied monitor patch. [0]: https://www.openwall.com/lists/oss-security/2020/10/06/10 Signed-off-by: Oguz Bektas --- Makefile | 10