When use virt-v2v to convert vm from vmware to kvm, windows guest sometimes meet issue after start on kvm. For quite old windows os version, typically windows 2003, may meet following blue screen issue:
with code 0x0000007B.
So I write a hands-on blog to help fix this issue.
When search for this error on vmware kb or MSDN, we can find out that, wrong driver is the main reason cause this problem.
Usually, it’s recommanded to do following check for the v2v vm:
- Confirm the vm running well on original host, if its already error check configuration first.
- Check if virt-v2v failed to install virtio driver to guest during virt-v2v convert.
- Check kvm configuration, that root disk use ide to keep compitable.
- Check if windows disabled driver installatin by its group policy.
Besides those issues, if you migrate a windows 2003 with cd-rom you will also met this blue screen issue. Due to windows will change device order after v2v and root disk not work as expected.
So I write this practical blog to resolve device changed issue on windows 2003 v2v.
Uninstall vmware guest tools and drivers (avoid failed to install driver issue)
Change the disk controller to ide and reboot guest
Attach MergeIde.iso to guest
the iso contains a .reg and a .bat file. Run the .reg first and run the .bat. The device will be recorded and prepare for hypervisor change.
export ovf template or use virt-v2v to export the vm the kvm.
check the vm started without blue screen.
For windows, it seems that with cd-rom or disk order changed guest, after hypervisor migration, windows can not identify the original order of thoes devices due to hardware change. So record the device seems a easy solution for v2v case.
Note: this solution is also useful for Windows XP v2v
Download MergeIDE.iso from: https://www.virtualbox.org/wiki/Migrate_Windows
Refer to Microsoft commands: https://learn.microsoft.com/en-US/troubleshoot/windows-client/performance/stop-error-7b-or-inaccessible-boot-device-troubleshooting