Re: [pve-devel] [PVE-User] Thank you!

>> Not only that, they manage to solve the zfs 7.7 issue. I think that deserves a big congratulation. Keep up the good work guys. Who is gonna pay the beer?? =) --- Gilberto Nunes Ferreira (47) 3025-5907 (47) 99676-7530 - Whatsapp / Telegram Skype: gilberto.nunes36 2018-04-13 10:58

[pve-devel] applied: [RFC PATCH] collect device list for nested pci-bridges

applied On Thu, Apr 12, 2018 at 05:04:56PM +0200, Dominik Csapak wrote: > when using q35 as machine type, there are nested pci-bridges, > but we only checked the first layer > > this resulted in not being able to hotplug scsi devices, > because scsihw0 was deeper in the pci-bridge construct, we

[pve-devel] [PATCH v4 storage 1/2] Fix #1542: show storage utilization per pool

- get storage utilization per pool - use librados2-perl for pool status - add librados2-perl as build-depends and depends in debian/control Signed-off-by: Alwin Antreich --- PVE/Storage.pm | 3 +- PVE/Storage/RBDPlugin.pm | 72

[pve-devel] [PATCH v4 storage 2/2] Refactor of method build_cmd and path

Method build_cmd and path use similar code to generate the ceph command line or qemu config parameters. They now use the private method ceph_connect_option for parameter generation. Signed-off-by: Alwin Antreich --- PVE/Storage/RBDPlugin.pm | 113

[pve-devel] [PATCH v4 storage 0/2] show storage utilization per pool

After some off-list discussions, I removed the calculations and use the used, free to stay with the old output. This removes the introduction of a new key and keeps the per pool values. It has the slight disadvantage not to show the same values as ceph during recovery, but otherwise shows the

[pve-devel] [PATCH qemu-server] readd nbd_stop

we accidentally moved nbd_stop to CloudInit.pm in commit 0c9a7596f6b686ead232927851200554c997fa44 and removed it in commit 3db6e4ab708b29e9e59572efd8e44558c84bad6d without realizing that live local storage migration still depends on it readd it Signed-off-by: Dominik Csapak

[pve-devel] applied: [PATCH v2/RESEND corosync-pve 0/3] fix CVE-2018-1084

applied On Fri, Apr 13, 2018 at 11:10:30AM +0200, Fabian Grünbichler wrote: > Fabian Grünbichler (3): > fix CVE-2018-1084: DoS via malformed packet > reformat old patches > bump version to 2.4.2-pve4 > > changelog.Debian | 6 +++ > Makefile

Re: [pve-devel] [RFC manager 4/5] add ACME certificate API endpoints

On Wed, Apr 11, 2018 at 10:08:50AM +0200, Fabian Grünbichler wrote: > for creating/ordering a new certificate and renewing respectively > revoking an existing one. > > Signed-off-by: Fabian Grünbichler > --- > PVE/API2/Makefile | 1 + > PVE/API2/ACME.pm | 319 >

Re: [pve-devel] [RFC manager 1/5] add CertHelpers utility

On Wed, Apr 11, 2018 at 10:08:47AM +0200, Fabian Grünbichler wrote: > PVE-specific certificate helper functions > > Signed-off-by: Fabian Grünbichler > --- > PVE/Makefile | 1 + > PVE/CertHelpers.pm | 104 >

Re: [pve-devel] [RFC manager 2/5] add node configuration file and API

On Wed, Apr 11, 2018 at 10:08:48AM +0200, Fabian Grünbichler wrote: > this currently only contains a description and the node-specific ACME > configuration, but I am sure we can find other goodies to put there. > > Signed-off-by: Fabian Grünbichler > --- >

[pve-devel] [Patch V3 guest-common] fix #1694: make failure of snapshot removal non-fatal

In certain high-load scenarios ANY ZFS operation can block, including registering an (async) destroy. Since ZFS operations are implemented via ioctl's, killing the user space process does not affect the waiting kernel thread processing the ioctl. Once "zfs destroy" has been called, killing it

[pve-devel] [PATCH qemu-server] fix #1697: only check machine type for pxe

it is not necessary to check the romfile of the running vm for .pxe machine types, since the machine type itself is not hot-pluggable Signed-off-by: Dominik Csapak --- PVE/QemuServer.pm | 9 ++--- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git

[pve-devel] [PATCH corosync-pve 1/2] fix CVE-2018-1084: DoS via malformed packet

Signed-off-by: Fabian Grünbichler --- debian/patches/cve-2018-1084.patch | 53 ++ debian/patches/series | 1 + 2 files changed, 54 insertions(+) create mode 100644 debian/patches/cve-2018-1084.patch diff --git

[pve-devel] [PATCH stable-4 corosync-pve 0/2] fix CVE-2018-1084

Fabian Grünbichler (2): fix CVE-2018-1084: DoS via malformed packet bump version to 2.4.2-2~pve4+2 Makefile | 2 +- debian/patches/cve-2018-1084.patch | 53 ++ debian/changelog | 6 + debian/patches/series

[pve-devel] [PATCH corosync-pve 2/2] bump version to 2.4.2-2~pve4+2

Signed-off-by: Fabian Grünbichler --- Makefile | 2 +- debian/changelog | 6 ++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 7308f90..a80e9dd 100644 --- a/Makefile +++ b/Makefile @@ -3,7 +3,7 @@ RELEASE=4.2 #

[pve-devel] [PATCH v2 corosync-pve 3/3] bump version to 2.4.2-pve4

Signed-off-by: Fabian Grünbichler --- changelog.Debian | 6 ++ Makefile | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/changelog.Debian b/changelog.Debian index beefe52..974c533 100644 --- a/changelog.Debian +++ b/changelog.Debian @@

[pve-devel] [PATCH v2 corosync-pve 2/3] reformat old patches

to reduce future patch churn Signed-off-by: Fabian Grünbichler --- patches/0001-add-Provides-Replaces-corosync-pve.patch | 8 patches/0002-don-t-install-default-corosync.conf.patch | 10 +-

[pve-devel] [PATCH v2 corosync-pve 1/3] fix CVE-2018-1084: DoS via malformed packet

Signed-off-by: Fabian Grünbichler --- ...09-totemcrypto-Check-length-of-the-packet.patch | 53 ++ patches/series | 1 + 2 files changed, 54 insertions(+) create mode 100644

[pve-devel] [PATCH v2/RESEND corosync-pve 0/3] fix CVE-2018-1084

Fabian Grünbichler (3): fix CVE-2018-1084: DoS via malformed packet reformat old patches bump version to 2.4.2-pve4 changelog.Debian | 6 +++ Makefile | 2 +- .../0001-add-Provides-Replaces-corosync-pve.patch |

[pve-devel] IGNORE: [PATCH corosync-pve 0/3] fix CVE-2018-1084

git-send-emailed wrong branch, will resend shortly ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH corosync-pve 2/3] reformat old patches

to reduce future patch churn Signed-off-by: Fabian Grünbichler --- patches/0001-add-Provides-Replaces-corosync-pve.patch | 8 patches/0002-don-t-install-default-corosync.conf.patch | 10 +-

[pve-devel] [PATCH corosync-pve 0/3] fix CVE-2018-1084

Fabian Grünbichler (3): cherry-pick CVE-2018-1084 fix reformat old patches bump version to 2.4.2-pve4 changelog.Debian | 6 + Makefile | 2 +- .../0001-add-Provides-Replaces-corosync-pve.patch | 8 +-

[pve-devel] [PATCH corosync-pve 1/3] cherry-pick CVE-2018-1084 fix

DoS via malformed packet. Signed-off-by: Fabian Grünbichler --- ...essary-and-problematic-corosync-qdevice.i.patch | 78 ...08-totemcrypto-Check-length-of-the-packet.patch | 53 ...-totemudp-Check-lenght-of-message-to-sent.patch | 125

[pve-devel] [PATCH corosync-pve 3/3] bump version to 2.4.2-pve4

Signed-off-by: Fabian Grünbichler --- changelog.Debian | 6 ++ Makefile | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/changelog.Debian b/changelog.Debian index beefe52..974c533 100644 --- a/changelog.Debian +++ b/changelog.Debian @@

Re: [pve-devel] avoiding VMID reuse

On Fri, Apr 13 2018 10:33:20 +0200, Wolfgang Bumiller wrote: > Code/style issues aside, in the current shape this is a > convenience-driven upstream API change for a specific use case / > personal preference. > > NAK. Fair enough. It was a simple hack of to solve the issue without large design

Re: [pve-devel] avoiding VMID reuse

On Wed, Apr 11, 2018 at 03:12:17PM +0300, Lauri Tirkkonen wrote: > On Tue, Mar 13 2018 11:15:23 +0200, Lauri Tirkkonen wrote: > > > Sorry if I misunderstood you but VMIDs are already _guaranteed_ to be > > > unique cluster wide, so also unique per node? > > > > I'll try to clarify: if I create a

Re: [pve-devel] [Patch V2 guest-common] fix #1694: Replication risks permanently losing sync in high loads due to timeout bug

> ;)) > > > +}; > > > > -die $err if $err; > > +# old snapshots will removed by next run from prepare_local_job. > > +warn $@ if $@; > > +$logfunc->("delete stale replication snapshot error: $@") if $@; > > again, is this double warn + log needed? (I ask because 2 out of 3

[pve-devel] [PATCH cluster 1/1] add 'xtermjs' to console types

so that we can have it as default in the webinterface Signed-off-by: Dominik Csapak --- data/PVE/Cluster.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/data/PVE/Cluster.pm b/data/PVE/Cluster.pm index ef7a541..ae9c85f 100644 ---

[pve-devel] [PATCH manager 2/4] remove the novnc panels for node/container

so that by default the users get xtermjs not for vms though, since most will still not use a serial terminal as the display Signed-off-by: Dominik Csapak --- www/manager6/lxc/Config.js | 9 - www/manager6/node/Config.js | 8 2 files changed, 17

[pve-devel] [PATCH manager 3/4] set the default console in the gui when setting the option

until now, we only set the default console once on page load, this enables to set it everytime the dc->options panel loads, so also after setting an option Signed-off-by: Dominik Csapak --- www/manager6/dc/OptionView.js | 13 + 1 file changed, 13 insertions(+)

[pve-devel] [PATCH cluster/manager] xtermjs webgui improvements

this series changes the embedded console to xterm.js for host/container (vms still need novnc) enables to set xtermjs as default in the datacenter.cfg (fallback is novnc, like spice) and adds xtermjs font settings to the gui pve-cluster Dominik Csapak (1): add 'xtermjs' to console types

[pve-devel] [PATCH manager 4/4] add xterm.js settings

this adds font-settings to the 'My Settings' window and makes that bigger Signed-off-by: Dominik Csapak --- www/manager6/window/Settings.js | 84 +++-- 1 file changed, 72 insertions(+), 12 deletions(-) diff --git

[pve-devel] applied: [PATCH cluster v3] pmxcfs: only exit parent when successfully started

applied On Thu, Apr 12, 2018 at 02:38:15PM +0200, Dominik Csapak wrote: > since systemd depends that parent exits only > when the service is actually started, we need to wait for the > child to get to the point where it starts the fuse loop > and signal the parent to now exit and write the pid

[pve-devel] applied: [PATCH xtermjs 0/4] upgrade to 3.2.0 and implement reconnect

applied with makefile fix like wolfgang suggested ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel