Hi,
You can check the migration progress via "virsh domjobinfo" command on
the source host of the vm.
for example, the output of vm migration to another storage
$ date;virsh domjobinfo i-2-1338-VM
Thu Apr 18 19:19:06 UTC 2024
Job type: Unbounded
Operation:Outgoing migration
Time elapsed: 2740 ms
Data processed: 235.875 MiB
Data remaining: 71.938 MiB
Data total: 307.812 MiB
File processed: 235.875 MiB
File remaining: 71.938 MiB
File total: 307.812 MiB
Thu Apr 18 19:19:07 UTC 2024
Job type: Unbounded
Operation:Outgoing migration
Time elapsed: 3797 ms
Data processed: 552.908 MiB
Data remaining: 190.426 MiB
Data total: 824.633 MiB
Memory processed: 245.095 MiB
Memory remaining: 190.426 MiB
Memory total: 516.820 MiB
Memory bandwidth: 251.917 MiB/s
Dirty rate: 0pages/s
Page size:4096 bytes
Iteration:1
Postcopy requests: 0
File processed: 307.812 MiB
File remaining: 0.000 B
File total: 307.812 MiB
Constant pages: 20980
Normal pages: 62576
Normal data: 244.438 MiB
Expected downtime: 300 ms
Setup time: 11 ms
Compression cache: 64.000 MiB
Compressed data: 0.000 B
Compressed pages: 0
Compression cache misses: 0
Compression overflows: 0
-Wei
On Wed, Apr 17, 2024 at 11:36 PM Jimmy Huybrechts wrote:
>
> Hi,
>
> I was migration a pretty big VM between hosts (using local storage) and while
> in the end that works fine.
>
> Is there any way to see a kind of status? In the GUI I can see it starts and
> finishes which is nice but of little use in this case.
> I tried looking at some logs but now where does it give any status or
> progress.
>
> On the server it goes out off I can see in the log:
> INFO [resource.wrapper.LibvirtMigrateCommandWrapper]
> (agentRequest-Handler-5:) (logid:90c561c8) Waiting for migration of i-8-63-VM
> to complete, waited 1549000ms
>
> But that’s it.
>
> How does the migration look like?
>
> --
> Jimmy
