Bug 1100252

Summary: virt-v2v of VMware Windows 2008 R2 VM that has the Windows Recovery Console installed succeeds but is not bootable
Product: [Community] Virtualization Tools Reporter: Sokratis <sokratis123k>
Component: virt-v2vAssignee: Matthew Booth <mbooth>
Status: CLOSED NOTABUG QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-23 08:10:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
virt-inspector output
none
virt-filesystems output none

Description Sokratis 2014-05-22 11:24:13 UTC
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.

Comment 1 Sokratis 2014-05-22 11:24:43 UTC
Created attachment 898348 [details]
virt-filesystems output

Comment 2 Sokratis 2014-05-22 11:27:01 UTC
For your info, the disk used by virt-inspector and virt-filesystems commands is the converted one which is stored on the export domain.

Comment 3 Sokratis 2014-05-23 06:08:59 UTC
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!