Migrating VMs Not Working

[nekton]

I have a 2 node cluster using Proxmox 7.1-12 on each node. The machine hardware and disk sizes are identical to each other.

I am trying to migrate a Windows 11 Pro vm. When I do the migration I take the vm offline.

I have tried a few times to do the migration. Each time it gets this far and stops.

2022-04-09 12:36:37 starting migration of VM 113 to node 'pve1' (192.168.201.15)
2022-04-09 12:36:37 found local disk 'local-lvm:vm-113-disk-0' (in current VM config)
2022-04-09 12:36:37 found local disk 'local-lvm:vm-113-disk-1' (in current VM config)
2022-04-09 12:36:37 found generated disk 'local-lvm:vm-113-disk-2' (in current VM config)
2022-04-09 12:36:37 copying local disk images
2022-04-09 12:36:38 volume pve/vm-113-disk-0 already exists - importing with a different name
2022-04-09 12:36:38 Logical volume "vm-113-disk-4" created.

I have let it sit at this point for a half an hour or more but there is no further output until I cancel the migration.
What might be going on? What debug steps can I take to figure out how to migrate this vm?

 

[Moayad]

Hello,

Please post the output of VM config qm config 113 and the output of pveversion -v

What might be going on? What debug steps can I take to figure out how to migrate this vm?

1) run journalctl -f from the first shell
2) do the migration... in the journalctl you should see a hint if there is an issue.

 

[nekton]

root@pve:~# pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-6-pve) pve-manager: 7.1-12 (running version: 7.1-12/b3c09de3) pve-kernel-helper: 7.1-14 pve-kernel-5.13: 7.1-9 pve-kernel-5.13.19-6-pve: 5.13.19-15 pve-kernel-5.13.19-2-pve: 5.13.19-4 ceph-fuse: 15.2.15-pve1 corosync: 3.1.5-pve2 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.22-pve2 libproxmox-acme-perl: 1.4.1 libproxmox-backup-qemu0: 1.2.0-1 libpve-access-control: 7.1-7 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.1-5 libpve-guest-common-perl: 4.1-1 libpve-http-server-perl: 4.1-1 libpve-storage-perl: 7.1-1 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 4.0.11-1 lxcfs: 4.0.11-pve1 novnc-pve: 1.3.0-2 proxmox-backup-client: 2.1.5-1 proxmox-backup-file-restore: 2.1.5-1 proxmox-mini-journalreader: 1.3-1 proxmox-widget-toolkit: 3.4-7 pve-cluster: 7.1-3 pve-container: 4.1-4 pve-docs: 7.1-2 pve-edk2-firmware: 3.20210831-2 pve-firewall: 4.2-5 pve-firmware: 3.3-6 pve-ha-manager: 3.3-3 pve-i18n: 2.6-2 pve-qemu-kvm: 6.1.1-2 pve-xtermjs: 4.16.0-1 qemu-server: 7.1-4 smartmontools: 7.2-1 spiceterm: 3.2-2 swtpm: 0.7.1~bpo11+1 vncterm: 1.7-1 zfsutils-linux: 2.1.4-pve1

root@pve1:~# qm config 113 agent: 1 audio0: device=ich9-intel-hda,driver=spice bios: ovmf boot: order=virtio0;net0 cores: 4 cpu: kvm64 efidisk0: local-lvm:vm-113-disk-5,efitype=4m,pre-enrolled-keys=1,size=528K machine: pc-q35-6.1 memory: 8192 meta: creation-qemu=6.1.0,ctime=1648240349 name: DESKTOP-PPQUJJO net0: virtio=5A:D2:46:D8:4E:C1,bridge=vmbr0 numa: 0 ostype: win11 scsihw: virtio-scsi-pci smbios1: uuid=1c9bf5c7-4b95-43ee-a46e-ef4fa1677795 sockets: 1 tpmstate0: local-lvm:vm-113-disk-6,size=4M,version=v2.0 vga: qxl,memory=32 virtio0: local-lvm:vm-113-disk-4,size=64G vmgenid: 0865cf6c-a6ef-4003-8936-d067a6c14e50

The transfer did eventually take place but I ran it over night. I did not realize it would take that long. From videos I have watched the process looked like it would take 15-30 minutes. I saw no output other than the original I posted after a couple of hours after which I went to bed.

Do I have something misconfigured for it to take this long to migrate a VM?

 

[Moayad]

Hello,

Do I have something misconfigured for it to take this long to migrate a VM?

Did you set a bandwidth Limit for your node/cluster? you can check for the bandwidth limits under *PVE WebUI Datacenter>Options>Bandwidth Limits*

 

[nekton]

Hello,


Did you set a bandwidth Limit for your node/cluster? you can check for the bandwidth limits under *PVE WebUI Datacenter>Options>Bandwidth Limits*

Thanks for the tip. Bandwidth is set to "none".

 

[sg90]

Thanks for the tip. Bandwidth is set to "none".

During the migration it will show the progress at each stage and time taken e.t.c

You should be able to find the migration in the tasks at the bottom of the portal, if you scroll through it should give you a good idea of what part took a long time to complete, fact the VM is fairly small disk wise I imagine it shouldn't take too long over atleast 1Gbps connection.