> too late for me or something wrong on your side?
> git clone git://git.proxmox.com/git/libusb.git pve-wheezy.sources/libusb-1.0
> Cloning into 'pve-wheezy.sources/libusb-1.0'...
> fatal: The remote end hung up unexpectedly
fixed - please test again.
Am 06.12.2013 19:01, schrieb Dietmar Maurer:
i noticed that something like:
usb0: host=2-1.3
does not work anymore:
kvm: -device usb-host,hostbus=2,hostport=1.3: Parameter 'driver'
expects device type
ok this is due to the fact that qemu 1.7 checks for libusb at least
1.0.13 (pkg-config --atl
> > I just back ported the jessie packages to wheezy:
> >
> > https://git.proxmox.com/?p=libusb.git;a=summary
> >
> > https://git.proxmox.com/?p=pve-qemu-kvm.git;a=commitdiff;h=eefac8da9ac
> > fee621936f4162be711b7c7c211be
> >
> > Please can you test?
>
> do you already have the deb's somewhere?
Am 06.12.2013 19:01, schrieb Dietmar Maurer:
i noticed that something like:
usb0: host=2-1.3
does not work anymore:
kvm: -device usb-host,hostbus=2,hostport=1.3: Parameter 'driver'
expects device type
ok this is due to the fact that qemu 1.7 checks for libusb at least
1.0.13 (pkg-config --atl
Am 06.12.2013 15:46, schrieb Dietmar Maurer:
And do you get some speed improvements with that?
yes works great! Now my script takes 4s to execute instead of 32s.
Thanks!
Stefan
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmo
> > i noticed that something like:
> > usb0: host=2-1.3
> >
> > does not work anymore:
> > kvm: -device usb-host,hostbus=2,hostport=1.3: Parameter 'driver'
> > expects device type
>
> ok this is due to the fact that qemu 1.7 checks for libusb at least
> 1.0.13 (pkg-config --atleast-version=1.0.13
And do you get some speed improvements with that?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
---
PVE/API2/Nodes.pm | 54 +
1 file changed, 54 insertions(+)
diff --git a/PVE/API2/Nodes.pm b/PVE/API2/Nodes.pm
index 4cfcfd2..d349764 100644
--- a/PVE/API2/Nodes.pm
+++ b/PVE/API2/Nodes.pm
@@ -110,6 +110,7 @@ __PACKAGE__->register_method ({
> -Original Message-
> From: Dietmar Maurer
> Sent: Freitag, 06. Dezember 2013 12:38
> To: 'Stefan Priebe - Profihost AG'; pve-devel@pve.proxmox.com
> Subject: RE: [pve-devel] way to get all vm configs?
>
> > What is the correct way to call a path then and pass params to it?
> >
> > Do i
> What is the correct way to call a path then and pass params to it?
>
> Do i have to use this part out of pvesh? But which method to use?
You need to pass the method (additionally) with the command string.
___
pve-devel mailing list
pve-devel@pve.pro
Am 06.12.2013 11:26, schrieb Dietmar Maurer:
>>> yeah but still how do arrays and hashes be encoded? The key and values
>>> are url encoded - sure but how are values of type array encoded?
>>
>> Oh, I guess easiest way would be to add the ability to post 'JSON' data (use
>> application/json instead
> Where do you put the button to edit iolimit ? on the hdform ?
>
> Or do you want to put it on main interface near movedisk resizedisk ?
maybe a splitbutton for 'Edit', see Ext.button.Split - what do you think?
___
pve-devel mailing list
pve-devel@pve
> > yeah but still how do arrays and hashes be encoded? The key and values
> > are url encoded - sure but how are values of type array encoded?
>
> Oh, I guess easiest way would be to add the ability to post 'JSON' data (use
> application/json instead of application/x-www-form-urlencoded)
>
> see
> > I guess you should use PUT for the batch command (and encode the
> > method within the command parameters).
>
> yeah but still how do arrays and hashes be encoded? The key and values are url
> encoded - sure but how are values of type array encoded?
Oh, I guess easiest way would be to add the
Am 06.12.2013 10:31, schrieb Dietmar Maurer:
>> GET
>> https://cloud1-1203.de-nserver.de:8006/api2/json/nodes/cloud1-
>> 1203/execute?commands={JSON
>> ENCODED STUFF}
>>
>> sorry never used pve api with get and arrays.
>
>
> I guess you should use PUT for the batch command (and encode the
> meth
> GET
> https://cloud1-1203.de-nserver.de:8006/api2/json/nodes/cloud1-
> 1203/execute?commands={JSON
> ENCODED STUFF}
>
> sorry never used pve api with get and arrays.
I guess you should use PUT for the batch command (and encode the
method within the command parameters).
__
Am 06.12.2013 10:04, schrieb Stefan Priebe - Profihost AG:
>
> Am 06.12.2013 10:00, schrieb Dietmar Maurer:
>>> mind you help me:
>>>
>>> something like:
>>> pvesh get /nodes/cloud1-1203/execute -commands ["a","b"]
>>>
>>> results in:
>>> commands: type check ('array') failed
>>
>> You cannot exec
Am 06.12.2013 10:00, schrieb Dietmar Maurer:
>> mind you help me:
>>
>> something like:
>> pvesh get /nodes/cloud1-1203/execute -commands ["a","b"]
>>
>> results in:
>> commands: type check ('array') failed
>
> You cannot execute such command with pvesh (pvesh only handles string
> parameters)
>
> mind you help me:
>
> something like:
> pvesh get /nodes/cloud1-1203/execute -commands ["a","b"]
>
> results in:
> commands: type check ('array') failed
You cannot execute such command with pvesh (pvesh only handles string
parameters)
___
pve-devel
Am 06.12.2013 09:25, schrieb Dietmar Maurer:
>> Initiating the 250 connection took 2s. But EACH /qemu/123/config request took
>> 0.1s resulting in 25s. My client is most of the time waiting for an answer
>> of the
>> pveproxy server.
>
> OK, then the batch approach is maybe faster - feel free to
> Initiating the 250 connection took 2s. But EACH /qemu/123/config request took
> 0.1s resulting in 25s. My client is most of the time waiting for an answer of
> the
> pveproxy server.
OK, then the batch approach is maybe faster - feel free to test ;-)
___
Hi Dietmar,
Am 05.12.2013 17:47, schrieb Dietmar Maurer:
>>> I don't really like to add such API extensions, because that is just a speed
>> optimization?
>>
>> Yes. As creating and establishing SSL connections is really expensive.
>
> But you need to create the connection only once - then you
> Or do you want to put it on main interface near movedisk resizedisk ?
yes, between Edit and resizedisk.
We can try later to optimize that, maybe usinga a menu for Edit?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bi
>>A separate window. I do not thing one need to open hdform + hdlimitform at
>>the same time (why?)
Where do you put the button to edit iolimit ? on the hdform ?
Or do you want to put it on main interface near movedisk resizedisk ?
- Mail original -
De: "Dietmar Maurer"
À: "Alexa
24 matches
Mail list logo
