Re: [pve-devel] [PATCH pve-client] Use API definition for start/stop properties

2018-06-13 Thread Dietmar Maurer
> This works but currently 'qemu' is hard coded in the > "merge_api_definition_properties" path which > has the behavior that we ALWAYS get qemu "properties" where we want LXC > properties often. > > The only solution I can think of is to split those commands for Qemu/LXC > as in: >     >     $

Re: [pve-devel] [PATCH pve-client] Use API definition for start/stop properties

2018-06-13 Thread Dietmar Maurer
comments inline: > On June 13, 2018 at 2:17 PM René Jochum wrote: > > > --- > PVE/APIClient/Commands/GuestStatus.pm | 18 ++ > PVE/APIClient/Helpers.pm | 10 ++ > 2 files changed, 20 insertions(+), 8 deletions(-) > > diff --git

Re: [pve-devel] [PATCH pve-client] Use API definition for start/stop properties

2018-06-13 Thread René Jochum
This works but currently 'qemu' is hard coded in the "merge_api_definition_properties" path which has the behavior that we ALWAYS get qemu "properties" where we want LXC properties often. The only solution I can think of is to split those commands for Qemu/LXC as in:         $ pveclient qemu

[pve-devel] [PATCH pve-client] Use API definition for start/stop properties

2018-06-13 Thread René Jochum
--- PVE/APIClient/Commands/GuestStatus.pm | 18 ++ PVE/APIClient/Helpers.pm | 10 ++ 2 files changed, 20 insertions(+), 8 deletions(-) diff --git a/PVE/APIClient/Commands/GuestStatus.pm b/PVE/APIClient/Commands/GuestStatus.pm index 4a50164..7f90798 100644