Sudden Migration failures?

S

Shlee

Member
Apr 3, 2023
36
2
13
2026-06-10 12:06:22 use dedicated network address for sending migration traffic (192.168.1.2)
2026-06-10 12:06:22 starting migration of VM 123 to node 'unit0' (192.168.1.2)
2026-06-10 12:06:22 starting VM 123 on remote node 'unit0'
2026-06-10 12:06:26 [unit0] Task finished with 1 warning(s)!
2026-06-10 12:06:27 start remote tunnel
2026-06-10 12:06:28 ssh tunnel ver 1
2026-06-10 12:06:28 starting online/live migration on unix:/run/qemu-server/123.migrate
2026-06-10 12:06:28 set migration capabilities
2026-06-10 12:06:28 migration downtime limit: 100 ms
2026-06-10 12:06:28 migration cachesize: 256.0 MiB
2026-06-10 12:06:28 set migration parameters
2026-06-10 12:06:28 start migrate command to unix:/run/qemu-server/123.migrate
2026-06-10 12:06:29 migration active, transferred 608.6 MiB of 2.0 GiB VM-state, 632.3 MiB/s
2026-06-10 12:06:29 xbzrle: send updates to 1 pages in 0.0 B encoded memory, cache-miss 1.89%
2026-06-10 12:06:30 migration active, transferred 1.2 GiB of 2.0 GiB VM-state, 597.2 MiB/s
2026-06-10 12:06:30 xbzrle: send updates to 1 pages in 0.0 B encoded memory, cache-miss 1.89%
2026-06-10 12:06:31 migration status error: failed - Unable to write to socket: Broken pipe
2026-06-10 12:06:31 ERROR: online migrate failure - aborting
2026-06-10 12:06:31 aborting phase 2 - cleanup resources
2026-06-10 12:06:31 migrate_cancel
2026-06-10 12:06:33 ERROR: migration finished with problems (duration 00:00:11)
TASK ERROR: migration problems
Click to expand...
I've recently patched and rebooted to the latest kernel with community license.
 
Hi,
was there anything in the system logs/journal of the target node around the time of the issue? Please share the VM configuration qm config ID with the numerical ID and the output of pveversion -v from both nodes.
 
You must log in or register to reply here.
Top Bottom
Back