[pve-devel] applied: [PATCH manager] fix #1516: fix mouse-scrolling of overflowhandlers in firefox

___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] [PATCH manager] fix #1516: fix mouse-scrolling of overflowhandlers in firefox

On 10/04/2017 10:04 AM, Dominik Csapak wrote: > this is a workaround for scrolling in toolbars, etc. in firefox with the > mouse > > while the result is not very "pretty", it maintains the old behaviour > for all other browsers and makes it work in firefox > > we can drop this when we update to

Re: [pve-devel] [PATCH manager 1/3] ui: rename global 'Help' button to 'Documentation'

Or even better: man --- Gilberto Ferreira 2017-10-05 11:16 GMT-03:00 Gilberto Nunes : > Just use Docs for shortly. > > --- > Gilberto Ferreira > > > > > 2017-10-05 11:10 GMT-03:00 Dietmar Maurer : > >> -1 >> >> This uses too much space (very

Re: [pve-devel] [PATCH manager 1/3] ui: rename global 'Help' button to 'Documentation'

Just use Docs for shortly. --- Gilberto Ferreira 2017-10-05 11:10 GMT-03:00 Dietmar Maurer : > -1 > > This uses too much space (very bad for auto generated docu screenshots). > > > On October 5, 2017 at 3:05 PM Thomas Lamprecht > > wrote: > > >

Re: [pve-devel] [PATCH manager 1/3] ui: rename global 'Help' button to 'Documentation'

-1 This uses too much space (very bad for auto generated docu screenshots). > On October 5, 2017 at 3:05 PM Thomas Lamprecht > wrote: > > > To make it more clear that this will always end you on the > Documentation index. > > Also, multiple Help buittons which all

Re: [pve-devel] [PATCH manager v2 5/6] ui: merge CPUOptions into ProcessorEdit

On 10/05/2017 03:17 PM, Thomas Lamprecht wrote: > It seemed a bit weird that those options were in a seprate edit > window as they affect the same backend variable and may cause > confusion, an user may not be sure in what way they are related to > each other, if at all. > > This allows us to

[pve-devel] [PATCH manager v5 7/8] Update VM SCSI controller type after OS selection in Wizard

This was done previously without any kind of user visible feedback, so users would not know that they had a Virtio SCSI controller as default controller for Linux VMs. --- rebase after changes in 5/8 www/manager6/qemu/CreateWizard.js | 5 - www/manager6/qemu/OSDefaults.js | 2 +-

[pve-devel] [PATCH manager v5 6/8] Update VM SCSI type based on iothread value when inside the wizard

We keep the same logic as before: once the iothread option is selected, the SCSI controller is switched to virtio-scsi-single, until iothread is unselected again. --- rebase after 5/8 changed www/manager6/qemu/HDEdit.js | 21 + 1 file changed, 17 insertions(+), 4 deletions(-)

[pve-devel] [PATCH manager v5 5/8] Add a field to show which SCSI controller type we are currently using

We use the field label 'SCSI Controller'. 'Type' is redundant, otherwise we would have Network Card Type, Display Type, Network Card type, etc ... --- changes since v4: * rename the field label to SCSI Controller, and the associated component reference to scsiController.

[pve-devel] [PATCH manager v2 6/6] ui ProcessorEdit: remove redundancy, 'NUMA' is a checkbox

Signed-off-by: Thomas Lamprecht --- www/manager6/qemu/ProcessorEdit.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/www/manager6/qemu/ProcessorEdit.js b/www/manager6/qemu/ProcessorEdit.js index 04f1b90f..53602268 100644 ---

[pve-devel] [PATCH manager v2 2/6] ui CPUOptions: cpulimits is not dependend of VM cores

It makes no real sense to set the maximal allowed value to the total count of VM cores as this setting controls how much Host CPU time the whole KVM/QEMU instance can get. This instance does not only contains the VMs CPU threads but also threads for networking, block IO, migration, ... So it can

[pve-devel] [PATCH manager v2 5/6] ui: merge CPUOptions into ProcessorEdit

It seemed a bit weird that those options were in a seprate edit window as they affect the same backend variable and may cause confusion, an user may not be sure in what way they are related to each other, if at all. This allows us to share the help button, the docs must be updated so that the

[pve-devel] [PATCH manager v2 4/6] ui ProcessorEdit: remove total core count displayfield

Make space for merging CPUOptions into ProcessorEdit. Instead, make it clearer that the 'cores' option is really a 'cores per socket' option Signed-off-by: Thomas Lamprecht --- no changes www/manager6/qemu/ProcessorEdit.js | 10 +- 1 file changed, 1

[pve-devel] [PATCH manager v2 1/6] ui: refactor ProcessorInputPanel to declarative style

Signed-off-by: Thomas Lamprecht --- no change www/manager6/qemu/ProcessorEdit.js | 129 ++--- 1 file changed, 63 insertions(+), 66 deletions(-) diff --git a/www/manager6/qemu/ProcessorEdit.js b/www/manager6/qemu/ProcessorEdit.js index

[pve-devel] [PATCH manager v2 3/6] ui CPUOptions: fix cpu.shares (cpuunits) range and name

`These options take an integer value and control the "cpu.shares" control group attribute. The allowed range is 2 to 262144. Defaults to 1024.' - man systemd.resource-control Signed-off-by: Thomas Lamprecht --- no changes www/manager6/qemu/CPUOptions.js | 6 +++--- 1

Re: [pve-devel] [PATCH v3 container 3/5] use copy_volume for full clones

meta, and not related to this patch series (same probably applies to qemu-server as well) - shouldn't we lock the source config as well, and drop the flock before forking the worker? (note: if we ever extend our locking code, we could even support nested config locking for parallel clones of

[pve-devel] [PATCH manager 3/3] ui: add onlineHelpTitle to ConfigPanel childs

Lets add a onlineHelp title for the ConfigPanel lxc, qemu, node and pool (omitting only dc). As we fall back to the current ConfigPanels help link when a tab (or sub panel) has no own specific help defined this then can be shown so that the user sees which help will open before clicking the

[pve-devel] [PATCH manager 2/3] ConfigPanel: display help category in button

Signed-off-by: Thomas Lamprecht --- www/manager6/button/HelpButton.js | 12 +--- www/manager6/panel/ConfigPanel.js | 6 +- 2 files changed, 14 insertions(+), 4 deletions(-) diff --git a/www/manager6/button/HelpButton.js b/www/manager6/button/HelpButton.js

[pve-devel] [PATCH manager 1/3] ui: rename global 'Help' button to 'Documentation'

To make it more clear that this will always end you on the Documentation index. Also, multiple Help buittons which all may or may not do something diffrent are a bit weird/confusing - thus distiction is important IMO. Signed-off-by: Thomas Lamprecht ---

Re: [pve-devel] [PATCH v3 container 4/5] config: is_volume_in_use: ability to search only snapshots

On Tue, Sep 26, 2017 at 02:43:03PM +0200, Wolfgang Bumiller wrote: > --- > This patch is new. > > src/PVE/LXC/Config.pm | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/src/PVE/LXC/Config.pm b/src/PVE/LXC/Config.pm > index c45ce7e..0330d5e 100644 > ---

[pve-devel] [PATCH pve-http-server] remove trailing slash from URL path

Signed-off-by: Dietmar Maurer --- PVE/APIServer/AnyEvent.pm | 3 +++ 1 file changed, 3 insertions(+) diff --git a/PVE/APIServer/AnyEvent.pm b/PVE/APIServer/AnyEvent.pm index 703d25c..0eb574d 100755 --- a/PVE/APIServer/AnyEvent.pm +++ b/PVE/APIServer/AnyEvent.pm @@ -1131,6

Re: [pve-devel] [PATCH v3 container 5/5] add move_volume api call

On Tue, Sep 26, 2017 at 02:43:04PM +0200, Wolfgang Bumiller wrote: > --- > Changes: > * Instead of refusing moves when any snapshots exist, use the new >'is_volume_in_use' variant to check whether the volume is actually >used in a snapshot, in which case we simply don't allow the --delete

Re: [pve-devel] [PATCH manager v3 5/8] Add a field to show which SCSI controller type we are currently using

On 10/05/2017 11:25 AM, Thomas Lamprecht wrote: > On 09/28/2017 03:10 PM, Emmanuel Kasper wrote: >> On 09/27/2017 11:27 AM, Thomas Lamprecht wrote: >>> On 09/26/2017 02:17 PM, Emmanuel Kasper wrote: ---   www/manager6/qemu/HDEdit.js | 15 ---   1 file changed, 12

[pve-devel] [PATCH manager] ui: inline novnc: always focus console panel after render

Enforce focus on the Inline CT/VM/Host Console panel backed by noVNC. Else, if a Console is already active on VM A and we select VM B the console there does not gets the focus as its now in the three and regaining focus to the console is not fully intuitive - i.e. just clicking on the console

[pve-devel] [PATCH 1/1] dmeventd: ensure service gets stopped normally on shutdown

cherry-pick two patches which ensure that dmeventd gets always stopped when requested (i.e. if exiting is not ok at the moment it gets scheduled for the next possible moment and not thrown away) and which also ensures that it gets stopped more safely on shutdown. This addresses a issue where when

[pve-devel] [PATCH v2 0/1] dmeventd: ensure service can exit normally

My patch did not changed but got applied upstream [1], together with another fix both which implents our discussed idea[2][3] to never throw away a exit request but schedule it for the next possible time, if we cannot exit at the moment.[4] I cherry-picked both commits and added them to our LVM

[pve-devel] applied: [PATCH manager 1/3] doc: spice-example-sh: add quotes everywhere

all three patches ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] [PATCH manager v4 0/8] Display the SCSI controller type when adding a new disk

On 10/02/2017 10:37 AM, Emmanuel Kasper wrote: > Since we switched to the SCSI controller in the Wizard as the recommended > controller > for hard disks (using VirtIO scsi in the backend) it was not clear for users > that they were actually using a paravirtualized driver. > > An example of user

Re: [pve-devel] [PATCH manager v3 5/8] Add a field to show which SCSI controller type we are currently using

On 09/28/2017 03:10 PM, Emmanuel Kasper wrote: > On 09/27/2017 11:27 AM, Thomas Lamprecht wrote: >> On 09/26/2017 02:17 PM, Emmanuel Kasper wrote: >>> --- >>>   www/manager6/qemu/HDEdit.js | 15 --- >>>   1 file changed, 12 insertions(+), 3 deletions(-) >>> >>> diff --git

Re: [pve-devel] [PATCH manager v3 1/8] Do not use 'autoselect' as a boolean when preselecting a bus

On 09/28/2017 03:35 PM, Emmanuel Kasper wrote: > On 09/27/2017 10:47 AM, Thomas Lamprecht wrote: >> On 09/26/2017 02:17 PM, Emmanuel Kasper wrote: >>> The bus selector is displayed when we add a Hard Disk or CD Drive. >>> When it is displayed, we *always* preselect the next available >>> slot on

[pve-devel] AMD EPYC

Hi all, Since several times I read both on this list and on the forum that AMD based servers are rarely used for development / testing, I'd like to offer the following: I just ordered a dual socket EPYC system (Supermicro AS-1123US-TR4 with dual EPYC 7351) and if any of the core developers