Migrate VM from node v5 to node v6 failed

Nov 30, 2020
29
2
23
44
Hello there !
I'm running into a small problem : before cluster migration v5 to v6, I migrated all my vm on one node. Now all nodes are upgraded, I'd like to move back vms on node v6.
But I got an error :
Code:
qemu-img: /dev/stdout: error while converting raw: Could not resize file: Invalid argument
command 'qemu-img convert -f qcow2 -O raw /var/lib/vz/images/160/vm-160-disk-1.qcow2 /dev/stdout' failed: exit code 1
cannot import format raw+size into a file of format qcow2
The vm config :
Code:
agent: 1
boot: cdn
bootdisk: virtio0
cores: 1
description: Debian 10%0AServeur LAMP%3A%0A - apache 2.4.38%0A - php 7.3.x%0A - MariaDB 10.3.15%0A - adminer%0A - fail2ban
ide2: none,media=cdrom
memory: 1536
name: oracle
net0: virtio=02:00:00:e2:78:59,bridge=vmbr1,firewall=1
numa: 0
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=d89b22f7-cbca-4b65-9184-13d0e4bcd328
sockets: 1
virtio0: datastore:160/vm-160-disk-0.raw,format=raw,size=64G
vmgenid: 14a838dd-d8b3-48b7-81ef-5fad2f5dcb3a
What am I doing wrong ? Thank you !
 
Hi,
seems like you have an orphaned disk /var/lib/vz/images/160/vm-160-disk-1.qcow2 that's not present in the VM configuration. You should check its timestamp/contents and see if you can safely remove it (maybe it's just some leftover of an earlier operation). If you're in a hurry you can also simply rename it, so that it doesn't include the VM ID anymore, and check later.
 
  • Like
Reactions: itseliev

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!