You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by "kiranchavala (via GitHub)" <gi...@apache.org> on 2026/05/26 07:47:12 UTC
[I] Unable to start a migrated vm (windows server 2025 ) from vmware to KVM using virt-v2v [cloudstack]
kiranchavala opened a new issue, #13241:
URL: https://github.com/apache/cloudstack/issues/13241
### 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
<img width="1601" height="580" alt="Image" src="https://github.com/user-attachments/assets/110f277b-75be-43ea-96fa-e347652f6955" />
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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Unable to start a migrated vm (windows server 2025 ) from vmware to KVM using virt-v2v [cloudstack]
Posted by "andrijapanicsb (via GitHub)" <gi...@apache.org>.
andrijapanicsb commented on issue #13241:
URL: https://github.com/apache/cloudstack/issues/13241#issuecomment-4568671271
<img width="1585" height="877" alt="Image" src="https://github.com/user-attachments/assets/2046edf8-4df7-4f7b-8683-043fbc8e3576" />
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Unable to start a migrated vm (windows server 2025 ) from vmware to KVM using virt-v2v [cloudstack]
Posted by "andrijapanicsb (via GitHub)" <gi...@apache.org>.
andrijapanicsb commented on issue #13241:
URL: https://github.com/apache/cloudstack/issues/13241#issuecomment-4542503674
Recommended design for Windows Server 2025:
CloudStack 4.22+
KVM hosts: EL9 or Ubuntu 24.04
machine type: pc-q35-<version>
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"
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Unable to start a migrated vm (windows server 2025 ) from vmware to KVM using virt-v2v [cloudstack]
Posted by "RosiKyu (via GitHub)" <gi...@apache.org>.
RosiKyu commented on issue #13241:
URL: https://github.com/apache/cloudstack/issues/13241#issuecomment-4787423107
I have tested this. With the flow described in the **Steps to reproduce** :
**The original bug (default import):**
- Real Windows Server 2025 (UEFI/GPT) -> CloudStack VMware -> KVM import -> conversion succeeds, disk is fine - but the VM is created BIOS + i440fx (boottype=None, machine='pc-i440fx-rhel7.6.0', SeaBIOS).
- Result: "No bootable device"
<img width="1525" height="861" alt="Image" src="https://github.com/user-attachments/assets/79215ff4-bf48-449b-9d60-fdbb3861ba32" />
**The workaround (verified booting):**
- Set the VM to UEFI=legacy (-> q35 + UEFI/OVMF) and host CPU to host-passthrough; virtio disk/NIC the import already set.
- Confirmed live config: machine='pc-q35-rhel9.2.0', OVMF loader+nvram, cpu mode='host-passthrough'.
- Result: VM boots
But: a **secondary reboot loop** appears after the workaround boots
- With the UEFI/q35 config the VM boots, but Windows reaches the logon screen and then restarts itself, repeatedly. UEFI reloads \EFI\Microsoft\Boot\bootmgfw.efi from the GPT partition each cycle - so firmware/disk are fine;
Root cause of the loop is a virtio-win driver signing issue, not the firmware
- virt-v2v installs a first-boot script (2000-0001-pnputil-install-drivers.bat) that pnputil-installs the bundled virtio drivers. It fails on smbus.inf, exits non-zero, and virt-v2v reboots to "retry on next boot" - which it did on every reboot (56 cycles observed before manual intervention), an effectively infinite loop:
```
Installing: smbus.inf.
Adding the driver package failed : A certificate chain processed, but terminated
in a root certificate which is not trusted by the trust provider.
Failed to install smbus.inf. .... exit code 249
Script failed, will retry on next boot
```
- Why only smbus: within the same virtio-win package the drivers are signed differently.
```
netkvm.cat (installs fine) -> subject = Microsoft Windows Hardware Compatibility Publisher [WHQL, trusted]
smbus.cat (fails) → subject = O=virtio-win, OU=Dev, CN=Red Hat Inc. [self-signed dev cert, NOT trusted]
```
=> Not a virtio-win version issue: checked both the latest (0.1.285) and the stable virtio-win - both ship smbus with the same self-signed dev cert, so switching versions does not fix it.
The dev-signed smbus driver is present in all builds. virt-v2v's first-boot path installs via pnputil without importing the virtio-win certificate (the virtio-win guest-tools MSI normally imports it into Trusted Publisher first), so the dev-signed driver fails - and virt-v2v retries forever on a single driver failure. Any Windows guest converted through this path can hit the same loop.
**Workaround and final state**
- Removed the looping first-boot driver script from the converted disk -> Windows then boots stably to SConfig.
- Migrated guest is functional: storage (offline-injected viostor) and network (virtio-net) work; only one non-essential device - the virtio serial controller (shown as PCI Simple Communications Controller, VEN_1AF4&DEV_1043) - is left without a driver.
<img width="1649" height="1212" alt="Image" src="https://github.com/user-attachments/assets/711d0f60-1e7f-4523-a7a3-406960db29d3" />
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Unable to start a migrated vm (windows server 2025 ) from vmware to KVM using virt-v2v [cloudstack]
Posted by "RosiKyu (via GitHub)" <gi...@apache.org>.
RosiKyu commented on issue #13241:
URL: https://github.com/apache/cloudstack/issues/13241#issuecomment-5102218340
Have tested this end-to-end and quite thoroughly. If anyone has an issue - please notify us.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Unable to start a migrated vm (windows server 2025 ) from vmware to KVM using virt-v2v [cloudstack]
Posted by "andrijapanicsb (via GitHub)" <gi...@apache.org>.
andrijapanicsb commented on issue #13241:
URL: https://github.com/apache/cloudstack/issues/13241#issuecomment-4542512131
If it was migrated - did virt-v2v injevt virtio-win drivers or not (KVM host agent logs will show)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Unable to start a migrated vm (windows server 2025 ) from vmware to KVM using virt-v2v [cloudstack]
Posted by "andrijapanicsb (via GitHub)" <gi...@apache.org>.
andrijapanicsb commented on issue #13241:
URL: https://github.com/apache/cloudstack/issues/13241#issuecomment-4568676970
UEFI/legacy ADN q35 AND cpu passthrough/host model are a must, irrelevan of drivers - tested end-to-end
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Unable to start a migrated vm (windows server 2025 ) from vmware to KVM using virt-v2v [cloudstack]
Posted by "RosiKyu (via GitHub)" <gi...@apache.org>.
RosiKyu commented on issue #13241:
URL: https://github.com/apache/cloudstack/issues/13241#issuecomment-5102264097
I think we could close this one @DaanHoogland ? Long time - no see by anayone participating in the discussion.
I guess and hope that if there's anybothy interested, the'd shout out. However, does not seem like it as of now. So we might close and re-open if needed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Unable to start a migrated vm (windows server 2025 ) from vmware to KVM using virt-v2v [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland closed issue #13241: Unable to start a migrated vm (windows server 2025 ) from vmware to KVM using virt-v2v
URL: https://github.com/apache/cloudstack/issues/13241
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org