Bug 2080155 - [RFE] Provide the progress of VM migration in the source virt launcher pod
Summary: [RFE] Provide the progress of VM migration in the source virt launcher pod
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 4.10.0
Hardware: All
OS: Linux
high
high
Target Milestone: ---
: 4.11.0
Assignee: Jed Lejosne
QA Contact: Denys Shchedrivyi
URL:
Whiteboard:
: 2080208 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-29 07:04 UTC by nijin ashok
Modified: 2022-10-31 10:49 UTC (History)
7 users (show)

Fixed In Version: virt-launcher-v4.11.0-92
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-14 19:31:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt kubevirt pull 7729 0 None open migration: log progress in source virt-launcher logs 2022-05-11 18:14:35 UTC
Red Hat Issue Tracker CNV-17896 0 None None None 2022-10-31 10:49:06 UTC
Red Hat Product Errata RHSA-2022:6526 0 None None None 2022-09-14 19:31:34 UTC

Description nijin ashok 2022-04-29 07:04:18 UTC
Description of problem:

libvirt/qemu provides information like below to understand the progress of the migration and troubleshoot the migration problem:

~~~
virsh -r domjobinfo vm-name
setlocale: No such file or directory
Job type:         Unbounded   
Operation:        Outgoing migration
Time elapsed:     22361        ms
Data processed:   1.163 GiB
Data remaining:   14.742 GiB
Data total:       16.071 GiB
Memory processed: 1.163 GiB
Memory remaining: 14.742 GiB
Memory total:     16.071 GiB
Memory bandwidth: 62.015 MiB/s
Dirty rate:       0            pages/s
Page size:        4096         bytes
Iteration:        1           
Postcopy requests: 0           
Constant pages:   44254       
Normal pages:     304141      
Normal data:      1.160 GiB
Expected downtime: 100          ms
Setup time:       8            ms
~~~

Log this info in the logs periodically during migration so that the user can troubleshoot the issue if the migration stalls or fails.



Version-Release number of selected component (if applicable):

OpenShift Virtualization   4.10.0

Additional info:

For reference, the same is logged in RHV during migration  https://github.com/oVirt/vdsm/blob/master/lib/vdsm/virt/migration.py#L1024

Comment 1 Fabian Deutsch 2022-04-29 09:08:56 UTC
*** Bug 2080208 has been marked as a duplicate of this bug. ***

Comment 3 Antonio Cardace 2022-06-15 09:39:16 UTC
Moving back to post as this is not yet merged downstream.

Comment 4 Denys Shchedrivyi 2022-07-05 15:46:05 UTC
Verified on CNV v4.11.0-544 (virt-launcher-v4.11.0-100)

In virt-launcher logs I see these messages during migration:

{"component":"virt-launcher","kind":"","level":"info","msg":"Migration info for e0815b02-44a4-4b0e-9e62-459bb7ebb8b7: TimeElapsed:125588ms DataProcessed:132410987B DataRemaining:961081344B DataTotal:1120083968B MemoryProcessed:103444075B MemoryRemaining:961081344B MemoryTotal:1091117056B MemoryBandwidth:1067220B/s DirtyRate:57344B/s Iteration:2 PostcopyRequests:251 ConstantPages:7648 NormalPages:25187 NormalData:103165952B ExpectedDowntime:931097ms DiskBps:0","name":"vm-label","namespace":"default","pos":"live-migration-source.go:894","timestamp":"2022-07-05T15:30:15.391509Z","uid":"5babb1c0-f3a4-4238-9bdc-541d43f06bc9"}

Comment 7 errata-xmlrpc 2022-09-14 19:31:19 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Virtualization 4.11.0 Images security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:6526

Comment 8 Kedar Bidarkar 2022-10-31 10:22:09 UTC
Added automation in patch https://code.engineering.redhat.com/gerrit/c/cnv-tests/+/420905 and so we covered qe_test_coverage as part of above patch.


Note You need to log in before you can comment on or make changes to this bug.