[Bug] VM migration has lost cloudinit drive (not a CD/DVD Drive)

S

Shlee

Member
Apr 3, 2023
20
1
8
I "successfully" migrated from node 1 to node 2.. but the cloudinit has turned into a disk.. so I cannot migrate it back to node 1.
1750735842251.png
1750736106753.png

Expected Cloudinit Drive.
1750735882725.png

I'd imagine there is a file I can edit... but as this is a bug.
1) how do I investigate this?
2) how do I change the disk device back into a cloudinit drive?
 
Last edited:
Update for devs.
I've found the vm 116 has duped all of the disks... so I figure a previously failed migration didn't clean itself up

and the next migration didn't overwrite the existing files but just renamed them (which might be a nice safety feature.. but I'd rather get a prompt to request to "keep existing file or overwrite existing file").

root cause: the cloudinit just got renamed to disk-3

1750739624518.png
 

Attachments

  • 1750739602346.png
    1750739602346.png
    74.2 KB · Views: 3
Last edited:
Hi,
please share the full migration task log from both migrations (you can find it in the source node's Task History in the UI) and the output of pveversion -v from source and target node.
 
1750779711190.png

This is likely the original cause. I guess this didn't get cleaned up?
2025-06-23 13:30:12 use dedicated network address for sending migration traffic (192.168.1.2)
2025-06-23 13:30:12 starting migration of VM 116 to node 'unit0' (192.168.1.2)
2025-06-23 13:30:12 found generated disk 'INTELSSD:vm-116-cloudinit' (in current VM config)
2025-06-23 13:30:12 found local disk 'INTELSSD:vm-116-disk-0' (attached)
2025-06-23 13:30:12 found generated disk 'INTELSSD:vm-116-disk-1' (in current VM config)
2025-06-23 13:30:12 found local disk 'INTELSSD:vm-116-disk-2' (attached)
2025-06-23 13:30:12 copying local disk images
2025-06-23 13:30:13 full send of INTELSSD/vm-116-cloudinit@__migration__ estimated size is 65.3K
2025-06-23 13:30:13 total estimated size is 65.3K
2025-06-23 13:30:13 TIME SENT SNAPSHOT INTELSSD/vm-116-cloudinit@__migration__
2025-06-23 13:30:14 successfully imported 'SSD:vm-116-cloudinit'
2025-06-23 13:30:14 volume 'INTELSSD:vm-116-cloudinit' is 'SSD:vm-116-cloudinit' on the target
2025-06-23 13:30:15 full send of INTELSSD/vm-116-disk-1@__migration__ estimated size is 45.0K
2025-06-23 13:30:15 total estimated size is 45.0K
2025-06-23 13:30:15 TIME SENT SNAPSHOT INTELSSD/vm-116-disk-1@__migration__
2025-06-23 13:30:16 successfully imported 'SSD:vm-116-disk-1'
2025-06-23 13:30:17 volume 'INTELSSD:vm-116-disk-1' is 'SSD:vm-116-disk-1' on the target
2025-06-23 13:30:17 starting VM 116 on remote node 'unit0'
2025-06-23 13:30:21 volume 'INTELSSD:vm-116-disk-0' is 'SSD:vm-116-disk-0' on the target
2025-06-23 13:30:21 volume 'INTELSSD:vm-116-disk-2' is 'SSD:vm-116-disk-2' on the target
2025-06-23 13:30:21 start remote tunnel
2025-06-23 13:30:23 ssh tunnel ver 1
2025-06-23 13:30:23 starting storage migration
2025-06-23 13:30:23 efidisk0: start migration to nbd:unix:/run/qemu-server/116_nbd.migrate:exportname=drive-efidisk0
drive mirror is starting for drive-efidisk0
drive-efidisk0: transferred 0.0 B of 528.0 KiB (0.00%) in 0s
drive-efidisk0: transferred 528.0 KiB of 528.0 KiB (100.00%) in 1s, ready
all 'mirror' jobs are ready
2025-06-23 13:30:24 virtio0: start migration to nbd:unix:/run/qemu-server/116_nbd.migrate:exportname=drive-virtio0
drive mirror is starting for drive-virtio0
drive-efidisk0: Cancelling block job
drive-virtio0: Cancelling block job
WARN: drive-efidisk0: Input/output error (io-status: ok)
WARN: drive-virtio0: Input/output error (io-status: ok)
drive-efidisk0: Done.
drive-virtio0: Done.
2025-06-23 13:30:26 ERROR: online migrate failure - block job (mirror) error: interrupted by signal
2025-06-23 13:30:26 aborting phase 2 - cleanup resources
2025-06-23 13:30:26 migrate_cancel
Click to expand...

and versions (they're both updated at the same time)
root@unit1:~# pveversion -v
proxmox-ve: 8.4.0 (running kernel: 6.14.5-1-bpo12-pve)
pve-manager: 8.4.1 (running version: 8.4.1/2a5fa54a8503f96d)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.14.5-1-bpo12-pve-signed: 6.14.5-1~bpo12+1
proxmox-kernel-6.14: 6.14.5-1~bpo12+1
proxmox-kernel-6.8.12-11-pve-signed: 6.8.12-11
proxmox-kernel-6.8: 6.8.12-11
proxmox-kernel-6.8.12-10-pve-signed: 6.8.12-10
proxmox-kernel-6.8.12-9-pve-signed: 6.8.12-9
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
amd64-microcode: 3.20240820.1~deb12u1
ceph-fuse: 17.2.8-pve2
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
dnsmasq: 2.90-4~deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.0
libpve-cluster-perl: 8.1.0
libpve-common-perl: 8.3.1
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.6
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.1-1
proxmox-backup-file-restore: 3.4.1-1
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.2
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.11
pve-cluster: 8.1.0
pve-container: 5.2.6
pve-docs: 8.4.0
pve-edk2-firmware: 4.2025.02-3
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.1
pve-firmware: 3.15-4
pve-ha-manager: 4.0.7
pve-i18n: 3.4.4
pve-qemu-kvm: 9.2.0-5
pve-xtermjs: 5.5.0-2
qemu-server: 8.3.12
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve2
Click to expand...


root@unit0:~# pveversion -v
proxmox-ve: 8.4.0 (running kernel: 6.14.5-1-bpo12-pve)
pve-manager: 8.4.1 (running version: 8.4.1/2a5fa54a8503f96d)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.14.5-1-bpo12-pve-signed: 6.14.5-1~bpo12+1
proxmox-kernel-6.14: 6.14.5-1~bpo12+1
proxmox-kernel-6.8.12-11-pve-signed: 6.8.12-11
proxmox-kernel-6.8: 6.8.12-11
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
amd64-microcode: 3.20240820.1~deb12u1
ceph-fuse: 17.2.8-pve2
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
dnsmasq: 2.90-4~deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.0
libpve-cluster-perl: 8.1.0
libpve-common-perl: 8.3.1
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.6
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.1-1
proxmox-backup-file-restore: 3.4.1-1
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.2
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.11
pve-cluster: 8.1.0
pve-container: 5.2.6
pve-docs: 8.4.0
pve-edk2-firmware: 4.2025.02-3
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.1
pve-firmware: 3.15-4
pve-ha-manager: 4.0.7
pve-i18n: 3.4.4
pve-qemu-kvm: 9.2.0-5
pve-xtermjs: 5.5.0-2
qemu-server: 8.3.12
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve2
Click to expand...
 
You must log in or register to reply here.
Top Bottom