Hi,
If I use "template: 1" during vm creation the vm will be a template but the disk will be "-rw-r--r-- 1 root root vm-101-disk-0.qcow2" a vm disk.
(I know there is no different between the vm and the base disk.)
If I create a vm and after that I convert it to template there will be get an empty response but a task will be started in the background.
It is not easy to know the end of the process without task id.
Is there a solution to import an existing disk image via API interface like the qm importdisk?
I overwrite the existing vm disk after vm creation. But it is not the best solution.
If I use "template: 1" during vm creation the vm will be a template but the disk will be "-rw-r--r-- 1 root root vm-101-disk-0.qcow2" a vm disk.
(I know there is no different between the vm and the base disk.)
If I create a vm and after that I convert it to template there will be get an empty response but a task will be started in the background.
It is not easy to know the end of the process without task id.
Is there a solution to import an existing disk image via API interface like the qm importdisk?
I overwrite the existing vm disk after vm creation. But it is not the best solution.