Am 19.12.2016 um 08:40 schrieb Fabian Grünbichler: > On Mon, Dec 19, 2016 at 07:23:35AM +0100, Stefan Priebe - Profihost AG wrote: >> Anything wrong or a bug? >> >> Greets, >> Stefan > > nothing wrong. unlocking a VM is possible with the special "qm unlock" > command (which is not exposed via the API IIRC) or by setting "skiplock" > when updating the VM configuration (which skips the lock check that > would otherwise prevent config modification). > > e.g.: pvesh set nodes/nora/qemu/100/config -delete lock -skiplock > > both methods are only available for root@pam
ah OK thanks. > >> Excuse my typo sent from my mobile phone. >> >>> Am 16.12.2016 um 22:19 schrieb Stefan Priebe - Profihost AG >>> <s.pri...@profihost.ag>: >>> >>> Hello, >>> >>> is there a way to unlock a VM through the API? >>> >>> I tried it this way but this does not work: >>> >>> pve:/nodes/testnode1/qemu/100> set config -delete lock >>> VM is locked (migrate) >>> >>> Greets, >>> Stefan >> _______________________________________________ >> pve-devel mailing list >> pve-devel@pve.proxmox.com >> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > > _______________________________________________ > pve-devel mailing list > pve-devel@pve.proxmox.com > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
