Issue

Use this article to troubleshoot V2V migration and stalled Windows startup issues.

Environment

• Product: ZCF
• Component: Cloud
• Affected object: V2V/Windows startup
• Versions: 4.x, 5.x
• Scenario: V2V migration/Windows startup stall

Symptoms

• A VM fails to start, restarts repeatedly, cannot enter the operating system, or reports a libvirt/qemu error.

Possible causes

• Image boot mode, disk chain, backing file, RBD watchers, volume path, drivers, or post-migration system compatibility is abnormal.

Resolution

1. Record the VM UUID, root-volume/data-volume UUID, hostUuid, original error message, and task time.
2. Check management-server, kvmagent, and libvirt/qemu logs.
3. Verify the image boot mode, disk chain, primary-storage state, and the existence of volume files.

Key command

virsh list --all
grep -a -nE "<vmUuid>|libvirt|qemu|backing|watchers|Could not open|not a bootable" /usr/local/zstack/apache-tomcat/logs/management-server.log* /var/log/libvirt/qemu/*.log 2>/dev/null

Remediation

• Based on the troubleshooting result, repair the affected component, configuration, data state, or connection path.
• If databases, underlying storage, snapshot chains, VM disks, GPU passthrough, or management-service restarts are involved, first confirm backups, scope of impact, and rollback paths.

Verification

• Confirm that the symptom described in this article no longer occurs.
• UI, API, management-node logs, and underlying command output corroborate one another.
• Observe at least one related task or alarm cycle to confirm that the issue does not recur.

Risks and rollback

• Before remediation in production, confirm customer service impact, the change window, and the rollback plan.
• For data deletion, database modifications, snapshot-chain repairs, underlying file operations, or hardware operations, ZStack recommends contacting technical support for confirmation.

Notes

• For VM startup, migration, HA, Unknown status, or forced stop operations, first confirm the actual VM running location to prevent split-brain operation, dual writes, or unintended service interruption.
• If database modifications, underlying file operations, lock release, service restarts, driver or firmware upgrades, or bulk resource changes are required, contact ZStack technical support before proceeding.