Skip to content

hypervisor selection issue at VMware migration #11555

Closed

Description

@ingox

problem

I have two hypervisors in my environment (KVM1 and KVM2).
I prepared KVM1 with all the tools and packages needed for VMware to KVM migration including packages needed for Windows VMs. See here: https://www.shapeblue.com/cloudstack-vmware-to-kvm-migration-tool/
In the dialog for starting the conversion I select KVM1 for the conversion (just tick the box in front of second line - no change in the drop down field).

Image

Right after starting the conversion I'm getting the following error:

Image

Here you can see KVM2 was chosen.

Workaround to get it working:
I'm selecting KVM2 and then back KVM1. That makes the code to work with KVM1.

versions

4.20.1.0

The steps to reproduce the bug

  1. Setup two hypervisors in your env.
  2. Prepare the first HV with all the tools needed for conversion.
  3. Select a VM for conversion.
  4. Select option to use a specific hypervisor - don't change drop down field

...

What to do about it?

No response

Activity

  1. DaanHoogland commented on Sep 2, 2025

    @DaanHoogland
    Contributor

    Marking this as a UI issue as I think this is a problem of the form not copying the value from the dropdown when it has not changed yet. cc @shwstppr @nvazquez , makes sense?

  2. added this to the 4.20.2 milestone on Sep 2, 2025
  3. added theissue type on Sep 2, 2025
  4. sureshanaparti commented on Sep 2, 2025

    @sureshanaparti
    Contributor

    @ingox Can you select both conversion and import host as KVM1 and check? Conversion host does the actual conversion using virt-v2v (and virtio-win required for Windows). As the conversion host not selected (as shown in the screenshot in the description), it is picking one of available hosts, so better choose it from the UI.

  5. ingox commented on Sep 2, 2025

    @ingox
    CollaboratorAuthor

    That works directly.

    Image

    ################################################################

    Image
  6. modified the milestones: 4.20.2, 4.20.3 on Oct 23, 2025
  7. abh1sar commented on Jan 5, 2026

    @abh1sar
    Contributor

    @sureshanaparti does this need any work?

  8. sureshanaparti commented on Jan 5, 2026

    @sureshanaparti
    Contributor

    @abh1sar I think, no changes required as the conversion host is not selected before. Also, once virt-v2v is installed, agent needs to be restarted to populate the virt-v2v details in the host, with which the the right host with the tools installed is auto picked for the conversion if no host is selected.

  9. abh1sar commented on Jan 6, 2026

    @abh1sar
    Contributor

    Thanks @sureshanaparti
    converting this to discussion and marking your comment as answer.

  10. converted this issue into a discussion #12375 on Jan 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions