Why did proxmox stop cloning VMs?

Question

linux

There are plenty of places in the pool for virtual machines. That is, the matter is definitely not in the finished place.

Today I decided to make a VM clone, climbs out

mistake

create full clone of drive scsi0 (local:108/vm-108-disk-0.qcow2)
Formatting '/var/lib/vz/images/105/vm-105-disk-0.qcow2', fmt=qcow2 size=0 cluster_size=65536 preallocation=metadata lazy_refcounts=off refcount_bits=16
drive mirror is starting for drive-scsi0
drive-scsi0: Cancelling block job
drive-scsi0: Done.
TASK ERROR: clone failed: mirroring error: drive-scsi0: mirroring has been cancelled

Well, I think I'll try to clone an unstarted VM, you never know what.

And there is the same story:

story

create full clone of drive scsi0 (local:104/vm-104-disk-0.qcow2)
Formatting '/var/lib/vz/images/105/vm-105-disk-0.qcow2', fmt=qcow2 size=0 cluster_size=65536 preallocation=metadata lazy_refcounts=off refcount_bits=16
transferred: 0 bytes remaining: 0 bytes total: 0 bytes progression: 0.00 %
qemu-img: output file is smaller than input file
TASK ERROR: clone failed: copy failed: command '/usr/bin/qemu-img convert -p -n -f qcow2 -O qcow2 /var/lib/vz/images/104/vm-104-disk-0.qcow2 zeroinit:/var/lib/vz/images/105/vm-105-disk-0.qcow2' failed: exit code 1

And then I noticed that before, when the cloning was always successful, the output was

so

create full clone of drive scsi0 (local:104/vm-104-disk-0.qcow2)
Formatting '/var/lib/vz/images/114/vm-114-disk-0.qcow2', fmt=qcow2 size=34359738368 cluster_size=65536 preallocation=metadata lazy_refcounts=off refcount_bits=16
drive mirror is starting for drive-scsi0
drive-scsi0: transferred: 2936012800 bytes remaining: 31424053248 bytes total: 34360066048 bytes progression: 8.54 % busy: 0 ready: 0
drive-scsi0: transferred: 6291456000 bytes remaining: 28069003264 bytes total: 34360459264 bytes progression: 18.31 % busy: 0 ready: 0
drive-scsi0: transferred: 9848225792 bytes remaining: 24513609728 bytes total: 34361835520 bytes progression: 28.66 % busy: 0 ready: 0
drive-scsi0: transferred: 16592666624 bytes remaining: 17771462656 bytes total: 34364129280 bytes progression: 48.28 % busy: 0 ready: 0
drive-scsi0: transferred: 19948109824 bytes remaining: 14416019456 bytes total: 34364129280 bytes progression: 58.05 % busy: 0 ready: 0
drive-scsi0: transferred: 23353884672 bytes remaining: 11011424256 bytes total: 34365308928 bytes progression: 67.96 % busy: 0 ready: 0
drive-scsi0: transferred: 27833401344 bytes remaining: 6532235264 bytes total: 34365636608 bytes progression: 80.99 % busy: 0 ready: 0
drive-scsi0: transferred: 31071404032 bytes remaining: 3294494720 bytes total: 34365898752 bytes progression: 90.41 % busy: 0 ready: 0
drive-scsi0: transferred: 34366160896 bytes remaining: 0 bytes total: 34366160896 bytes progression: 100.00 % busy: 1 ready: 0
drive-scsi0: transferred: 34373697536 bytes remaining: 0 bytes total: 34373697536 bytes progression: 100.00 % busy: 0 ready: 1
all mirroring jobs are ready
Qemu Guest Agent is not running - VM 104 qmp command 'guest-ping' failed - got timeout
suspend vm
trying to acquire lock...
drive-scsi0: Cancelling block job
drive-scsi0: Done.
resume vm
trying to acquire lock...
TASK OK

That is, now proxmox from some kind of horseradish indicates when creating a VM image SIZE = 0 instead of the normal size, after which, of course, the qemu-img convert command answers that they say "where will I clone if there is a 0 byte size?".

The last thing that was done on proxmox, according to the logs, was that it updated the package database. He updates this database to Useru every day 10 times.

I just tried to create a VM myself before cloning an existing one there. Everything works if you specify the normal size. But that's why proxmox stopped showing the size?

Answer 1

update proxmox to 6.2 and check disk space