On 07.07.20 10:20, Fabian Ebner wrote: > In config_to_command, '-loadstate' will be added whenever there is a > vmstate in the config. But in vm_start_nolock, the resume parameter > is used to calculate the appropriate timeout and to remove the vmstate > after the start. The resume parameter was only set if there is a > 'suspended' lock, but apparently [0] we cannot rely on the lock to be > set if and only if there is a vmstate. > > [0]: https://forum.proxmox.com/threads/task-error-start-failed.72450 > > Signed-off-by: Fabian Ebner <[email protected]> > --- > PVE/QemuServer.pm | 6 ++++-- > 1 file changed, 4 insertions(+), 2 deletions(-) > >
Was initially a bit unsure about this, but as the addition of "loadstate" happens since quite a bit this makes it at least work (again), so applied, thanks! _______________________________________________ pve-devel mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
