Created attachment 898347 [details] virt-inspector output Description of problem: virt-v2v of VMware Windows 2008 R2 VM with recovery console installed completes successfully: [root@ovirt-engine-01 Win2008]# time virt-v2v -ic esx://esxserver01/?no_verify=1 -o rhev -os 127.0.0.1:/ovirt_export_domain --network ovirtmgmt -of qcow2 -oa sparse cloud-ws-01 cloud-ws-01_cloud-ws-01: 100% [=======================================================================================================================================================================================]D 1h12m43s virt-v2v: cloud-ws-01 configured with virtio drivers. Version-Release number of selected component (if applicable): oVirt: 3.4.1 virt-v2v tool: virt-v2v-0.9.1-5.el6_5.x86_64 virtio drivers: virtio-win-0.1-74.iso (the iso was mounted and files for windows 2008 were copied to /usr/share/virtio-win/drivers/amd64/Win2008) Steps to Reproduce: 1. Perform v2v-virt2v 2. Import VM to oVirt 3. Start VM Actual results: VM boots into recovery console. If the VM is rebooted and "Launch Windows Normally" is selected then a BSOD is thrown and the VM is rebooted. Expected results: VM boots normally Additional info: Output of virt-inspector and virt-filesystems for the converted disk are attached.
Created attachment 898348 [details] virt-filesystems output
For your info, the disk used by virt-inspector and virt-filesystems commands is the converted one which is stored on the export domain.
Turns out that I was using the wrong virtio drivers. After loading the correct ones the v2v was completed successfully and I was able to boot the VM normally. Sorry for that :) You can close it. Thanks a lot!