if you run into timeouts when allocating an image on a network storage, it's recommended to useProxMox users, developers, et alia:
I am seeing this issue when I try to create a 500GB HD via NFS. Is there a way to see the actual qemu-img command that ProxMox is trying to issue to build the qcow2 file?
Presuming I had the precise command being run and then wanted to run it, how would I then scan and add that device to the appropriate virtual machine?
Stuart
pvesm set <storage ID>
--preallocation off
. This disables the default preallocation of metadata, thus speeding up the image allocation a lot. For such images, QEMU will then allocate the metadata as needed.I am having the same issue as OP, when I try "pvesm set <storage ID> --preallocation off", i get failed: unexprected property preallocation. Any suggestions?Hi,
if you run into timeouts when allocating an image on a network storage, it's recommended to usepvesm set <storage ID> --preallocation off
. This disables the default preallocation of metadata, thus speeding up the image allocation a lot. For such images, QEMU will then allocate the metadata as needed.
After a few hours of conducting tests trying to identify the error and how I could fix it, I managed to do so today.Meu caso foi testar um servidor proxmox 8.0.3 criando vms.
Em uma unidade compartilhada com Cifs e ocorreu o seguinte erro
TASK ERROR: incapaz de criar VM 110 - incapaz de criar imagem: comando 'storage-Data'-locked expirou - abortando Não
encontrei nenhuma evidência do que poderia estar acontecendo .
Após o erro ao criar o vm. nenhum outro criado no mesmo armazenamento funcionou.
Fui olhar o host físico e vi o seguinte erro que está no anexo.