> Denis Kanchev hat am 28.05.2025 08:13 CEST
> geschrieben:
>
>
> Here is the task log
> 2025-04-11 03:45:42 starting migration of VM 2282 to node 'telpr01pve05'
> (10.10.17.5)
> 2025-04-11 03:45:42 starting VM 2282 on remote node 'telpr01pve05'
> 2025-04-11 03:45:45 [telpr01pve05] Warning:
--- Begin Message ---
Here is the task log
2025-04-11 03:45:42 starting migration of VM 2282 to node 'telpr01pve05'
(10.10.17.5)
2025-04-11 03:45:42 starting VM 2282 on remote node 'telpr01pve05'
2025-04-11 03:45:45 [telpr01pve05] Warning: sch_htb: quantum of class 10001
is big. Consider r2q change
> Denis Kanchev hat am 22.05.2025 08:55 CEST
> geschrieben:
>
>
> The parent of the storage migration process gets killed.
>
> It seems that this is the desired behavior and as far i understand it
> correctly - the child worker is detached from the parent and it has
> nothing to do with it
--- Begin Message ---
The parent of the storage migration process gets killed.
It seems that this is the desired behavior and as far i understand it
correctly - the child worker is detached from the parent and it has
nothing to do with it after spawning.
Thanks for the information, it was ver
> Denis Kanchev via pve-devel hat am 21.05.2025
> 15:13 CEST geschrieben:
> Hello,
>
> We had an issue with a customer migrating a VM between nodes using our
> shared storage solution.
>
> On the target host the OOM killer killed the main migration process, but
> the child process (which act
