Unable to start a migrated vm (windows server 2025 ) from vmware to KVM using virt-v2v

[kiranchavala]

problem

Unable to start a migrated vm (windows server 2025 ) from vmware to KVM using virt-v2v

versions

ACS 4.22

The steps to reproduce the bug

1. A windows server 2025 vm is running on a external vcenter

2. Using Cloudstack vmware to kvm (Import-Export Instances)

3. Windows server 2025 disk converted to qcow2 successfully

4. Start the vm from Cloudstack

5. Vm unable to start , The following error is displayed

Tried changing the root disk to ide, scsi , still the same issue

...

What to do about it?

Windows server 2025 should get started successfully from cloudstack after migration

[andrijapanicsb]

Recommended design for Windows Server 2025:

CloudStack 4.22+
KVM hosts: EL9 or Ubuntu 24.04
machine type: pc-q35-
boot: UEFI
root disk controller: virtio-scsi / scsi
NIC: virtio
CPU: host-passthrough or host-model
optional: vTPM + Secure Boot

Machine type must not be old i440fx but instead a new one q35 - there is a VM setting "kvm.guest.os.machine.type"

[andrijapanicsb]

If it was migrated - did virt-v2v injevt virtio-win drivers or not (KVM host agent logs will show)