Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

vsphere: virt-v2v transfers disks sequentially #926

Merged
merged 1 commit into from
Jun 10, 2024
Merged

vsphere: virt-v2v transfers disks sequentially #926

merged 1 commit into from
Jun 10, 2024

Commits on Jun 9, 2024

  1. vsphere: virt-v2v transfers disks sequentially 

    when scheduling migrations to accommodate the controller_max_vm_inflight
setting for vSphere, we didn't take into account that disks are
transferred sequentially by virt-v2v (as opposed to CDI that transfers
them in parallel by different pods). This lead to performance
degregeration since could have triggered more migrations, in case of
migrations of multi-disk VMs, simultaneously without exceeding the value
of controller_max_vm_inflight. This is fixed by setting the cost of each
VM for which the disks are transferred by virt-v2v to 1.

Signed-off-by: Arik Hadas <[email protected]>
    @ahadas
    ahadas committed Jun 9, 2024
    Configuration menu
    Copy the full SHA
    62d9b09 View commit details
    Browse the repository at this point in the history