[PVE-User] KVM restore via API..

Dietmar Maurer dietmar at proxmox.com
Wed Jun 6 12:47:08 CEST 2012


OK, i can reproduce that bug. As workaround, try to pass a real storage identifier instead of the filesystem path

# pvesm list local

local:backup/vzdump-qemu-999-2011_11_22-11_03_21.tar
local:backup/vzdump-qemu-105-2012_02_10-07_41_11.tar.lzo


For eamply use: -d "vmid=10010&archive=local:backup/vzdump-qemu-999-2011_11_22-11_03_21.tar "

Does that help?


From: pve-user-bounces at pve.proxmox.com [mailto:pve-user-bounces at pve.proxmox.com] On Behalf Of Guy
Sent: Mittwoch, 06. Juni 2012 11:21
To: pve-user at pve.proxmox.com
Subject: [PVE-User] KVM restore via API..

Hi All,

I'm issuing this command to start a restore of an image..

curl -s -k -XPOST -H 'CSRFPreventionToken:$CSRFPreventionToken' '$host/api2/json/nodes/$PVEName/qemu/' -b 'PVEAuthCookie=$key' -d 'vmid=10010&archive=/felabimages/winXPPro.tar'

this seems to start the process however the output from the restore returns this:

TASK ERROR: Insecure dependency in piped open while running with -T switch at /usr/share/perl5/PVE/QemuServer.pm line 3072.

And the restore does not complete.

Did I pass something wrong here?

Cheers,
---Guy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pve.proxmox.com/pipermail/pve-user/attachments/20120606/dd13a1d6/attachment-0014.html>


More information about the pve-user mailing list