Re: [pve-devel] [PATCH manager 0/4] add start/stop/migration filtering
> if someone has a good argument why this is a bad idea, please share it > (or any other suggestion for this) IMHO it is confusing to display all VMs ... ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH manager 0/4] add start/stop/migration filtering
On 01/05/2017 04:04 PM, Dietmar Maurer wrote: BulkStop: Why do we list already stopped guests? i wanted to preserve the old behaviour (which included all vms) this is interesting for one case: you open the bulk stop window -> someone starts a vm -> you click stop in the old (and current) state, we try to stop the just started vm if i would filter that out, we would not stop it (because we only load the store once) if someone has a good argument why this is a bad idea, please share it (or any other suggestion for this) ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH manager 0/4] add start/stop/migration filtering
BulkStop: Why do we list already stopped guests? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
