Random Errors During Remote Migration from PVE 7.4 to 8.3

S

shahin352

Member
Aug 21, 2023
7
0
6
Hello everyone,

I've been encountering a recurring issue during remote migrations from Proxmox VE 7.4 to version 8.3. After transferring the disk and RAM, I occasionally get the following error for some VMs. However, migrations from version 7.4 to 7.4 work without any issues

Code: 
qm remote-migrate 100 200 apitoken='Authorization: PVEAPIToken=root@pam!hotmigrate=<token>',host=<ip>,fingerprint=<fingerprint> --target-bridge vmbr0 --target-storage local --online --bwlimit 80000

Code: 
2025-04-14 06:14:49 migration active, transferred 1.4 GiB of 2.0 GiB VM-state, 28.1 MiB/s

tunnel: done handling forwarded connection from '/run/qemu-server/100.migrate'

2025-04-14 06:14:49 average migration speed: 39.0 MiB/s - downtime 28 ms

2025-04-14 06:14:49 migration status: completed

all 'mirror' jobs are ready

drive-virtio0: Completing block job_id...

drive-virtio0: Completed successfully.

tunnel: done handling forwarded connection from '/run/qemu-server/100_nbd.migrate'

drive-virtio0: mirror-job finished

2025-04-14 06:14:50 stopping NBD storage migration server on target.

tunnel: -> sending command "nbdstop" to remote

tunnel: <- got reply

2025-04-14 06:14:50 ERROR: error - tunnel command '{"cmd":"nbdstop"}' failed - failed to handle 'nbdstop' command - VM 100 not running

2025-04-14 06:14:50 ERROR: migration finished with problems (duration 00:08:07)


Source Proxmox VE Version:

Code: 
proxmox-ve: 7.4-1 (running kernel: 5.15.143-1-pve)

pve-manager: 7.4-17 (running version: 7.4-17/513c62be)


Target Proxmox VE Version:

Code: 
proxmox-ve: 8.3.0 (running kernel: 6.8.12-9-pve)

pve-manager: 8.3.5 (running version: 8.3.5/dac3aa88bac3f300)


/etc/pve/qemu-server/100.conf
Code: 
agent: 1

boot: c

bootdisk: virtio0

cores: 1

cpu: host

memory: 2048

meta: creation-qemu=7.2.0,ctime=1728833753

name: test

net0: virtio=02:01:4B:38:B0:52,bridge=vmbr0

onboot: 0

ostype: other

serial0: socket

virtio0: local:100/vm-100-disk-0.qcow2,size=25G



Has anyone else experienced this issue or have ideas about what might be causing these random errors? I appreciate any guidance or suggestions you can provide.

Thank you!
 
fiona said:
Hi,
please check the system logs on the migration target.

Note that with CPU type host you will need the exact same physical CPU model on source and target for live migration to work properly: https://pve.proxmox.com/pve-docs/chapter-qm.html#_cpu_type
Click to expand...
Thank you for your response.

It's true that the CPU types are different, but in version 7.4, I was able to perform a large number of migrations with these models without any issues.

I checked the syslog on the destination server, and these logs are recorded before the migration error. Here are two examples:

- QEMU137202: kvm: Putting registers after init: Failed to set XCRs: Invalid argument
- QEMU197358: kvm: Putting registers after init: Failed to set XSAVE: Invalid argument
 
Last edited:
shahin352 said:
It's true that the CPU types are different, but in version 7.4, I was able to perform a large number of migrations with these models without any issues.
Click to expand...
then you were lucky. this is not supported for precisely this reason - it's not guaranteed to work reliably at all.
 
  • Like
Reactions: shahin352
You must log in or register to reply here.
Top Bottom