You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
KVM: show live migration progress on the instance page and add transfer details to VM.MIGRATE events #14531
During a live migration the UI only shows the instance as Migrating, so admins have to run virsh domjobinfo on the source host to see how far along it is or whether it has stalled.
This proposes showing migration progress for KVM first. The API field is hypervisor-neutral, so VMware, XenServer and others can add it later from their own task progress.
PROPOSAL
KVM agent: new command that returns the libvirt domain job info (disk and memory processed / remaining / total).
Management server: poll the source host every few seconds while the migrate work job runs, and store the result on the job with updateAsyncJobStatus().
API: admin-only migrationprogress on the VM response while the state is Migrating, read from the pending vm_work_job. Percent is always set and the byte/rate figures are optional, since other hypervisors only report a percentage.
UI: progress bar under Status on the instance page with percentage, "x of y complete", estimated time remaining and transfer rate in MB/s. When volumes migrate with the VM, disks and memory get separate bars; libvirt already splits them in the same job info (file* / mem*). Mock-up attached.
Events: append a summary to the VM.MIGRATE Completed event description (data transferred, duration, average rate), and on Error - a record of how far it got and a short reason (e.g. timed out and not converging, destination unreachable). Sizes, rates and reason category only. I wouldn't include host or storage names, since the event can be visible to the VM owner.
Happy to work on a PR if this approach is acceptable.
Mock-up of the UI change below:
Progress in an instance:
threat detection engine error
The threat detection engine encountered an error and could not complete analysis. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
The request is to show live-migration progress for KVM instances in the UI and API, and to add transfer summaries to VM.MIGRATE events. Today the instance only shows Migrating, and admins have to run virsh domjobinfo on the source host. The proposal covers a new KVM agent command, job-status polling, an admin-only migrationprogress field, a UI progress bar, and event-description details. The author offered to send a PR.
📊 Assessment
Dimension
Value
Reasoning
Type
type:enhancement
Feature request with a concrete proposal
Component
component:kvm
Progress comes from libvirt domain job info on the KVM agent
Severity
n/a
Not a bug report
Labels
type:enhancement, component:kvm
Coding agent
Not suitable
Changes span the agent, management server, API and UI, and include a design choice on visibility to VM owners
🔗 Similar issues
None found in the similar-issue search.
💡 Notes and suggestions
The proposal keeps the API field hypervisor-neutral, with percent always set and byte or rate figures optional. Maintainers can confirm that approach before a PR.
The proposal says host and storage names should stay out of VM.MIGRATE events because VM owners can see them. Maintainers may want to confirm that.
Activity
github-actions commentedon Oct 30, 2026
Warning
threat detection engine error
The threat detection engine encountered an error and could not complete analysis. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
🎯 Triage report
The request is to show live-migration progress for KVM instances in the UI and API, and to add transfer summaries to
VM.MIGRATEevents. Today the instance only showsMigrating, and admins have to runvirsh domjobinfoon the source host. The proposal covers a new KVM agent command, job-status polling, an admin-onlymigrationprogressfield, a UI progress bar, and event-description details. The author offered to send a PR.📊 Assessment
🔗 Similar issues
💡 Notes and suggestions
VM.MIGRATEevents because VM owners can see them. Maintainers may want to confirm that.Add this agentic workflow to your repo
To install this agentic workflow, run