Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1561828

Summary: RHV tools not properly installed in migrated Windows VM's causing boot failure
Product: Red Hat Enterprise Linux 7 Reporter: Brett Thurber <bthurber>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.5CC: mxie, ptoscano, smallamp, tzheng, zili
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Windows   
Whiteboard: V2V
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-18 03:44:26 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
install rhv-tools none

Description Brett Thurber 2018-03-29 01:18:55 UTC
Description of problem:
When using ManageIQ nightly build, v2v tooling, Windows 2008,2012, 2016 VMs migrate however post migration fail to boot.  0x7b and failure to find boot device.

Version-Release number of selected component (if applicable):
RHV 4.2.2
ManageIQ nightly using v2v tooling
vSphere 6.5
Windows 2008, 2012, 2016

How reproducible:
Every time

Steps to Reproduce:
1. With the Windows VM powered off, initiate VM migration.
2. Post VM migration the OS fails to boot.
3.

Actual results:
Migrated Windows VMs fail to boot post migration with RHV tools properly installed.

Expected results:
Migrated Windows VMs successfully boot post migration.

Additional info:
Windows 2008 v2v-wrapper log - http://file.rdu.redhat.com/bthurber/logs/v2v-import-20180326T220446-9786.log
Windows 2016 v2v-wrapper log - http://file.rdu.redhat.com/bthurber/logs/v2v-import-20180328T205012-31581.log
Windows 2012 v2v-wrapper log - http://file.rdu.redhat.com/bthurber/logs/v2v-import-20180328T201459-26144.log

Comment 2 Richard W.M. Jones 2018-03-29 07:35:07 UTC
*** Bug 1561653 has been marked as a duplicate of this bug. ***

Comment 3 Richard W.M. Jones 2018-03-29 07:35:43 UTC
Which version of virtio-win and virt-v2v are you using?

I am trying W2K16 now.

Comment 4 Richard W.M. Jones 2018-03-29 07:38:39 UTC
OK I have the version of virt-v2v from the log:
virt-v2v 1.36.10rhel=7,release=6.el7,libvirt

Would still be useful to know which version of virtio-win is installed.

Comment 5 Richard W.M. Jones 2018-03-29 07:56:27 UTC
FWIW I was able to convert a W2K16 machine ("mincore") this
morning and it booted up with virtio-blk.  I'm going to try an
end-to-end VMware to oVirt 4.2 migration next.

Comment 7 Richard W.M. Jones 2018-03-29 12:09:04 UTC
There are two issues at the moment which are stopping me from making
any forward progress on this bug:

https://www.redhat.com/archives/libguestfs/2018-March/msg00202.html
https://www.redhat.com/archives/libguestfs/2018-March/msg00204.html

I'll have to come back to this.

Comment 8 Richard W.M. Jones 2018-04-23 08:40:02 UTC
Most likely fixed by:

(1) Changes to the OVF so it puts "Windows xxx" instead of "Other OS"
in the operating system field.  I believe the commit which fixed
that was 593a19cc86cfa8f24c66518c8ba21222550b066a.

(2) Tomas's patch here:

https://www.redhat.com/archives/libguestfs/2018-April/msg00161.html

I'll make a new rhvpreview build.

Comment 9 Richard W.M. Jones 2018-04-24 07:55:10 UTC
Fix included in libguestfs-1.36.10-6.8.rhvpreview.el7ev

Comment 10 liuzi 2019-10-18 03:44:26 UTC
Verify bug with builds:
virt-v2v-1.40.2-8.el7.x86_64
libguestfs-1.40.2-8.el7.x86_64
virtio-win-1.9.8-6.el7.noarch
nbdkit-1.8.0-2.el7.x86_64 
RHV-4.3.6.5-0.1.el7

1.Use virt-v2v to convert a windows guest from esx6.7
# virt-v2v  -ic vpx://root.73.141/data/10.73.75.219/?no_verify=1 esx6.7-win2016-x86_64 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=1F:97:34:5F:B6:C2:BA:66:46:CB:1A:71:76:7D:6B:50:1E:03:00:EA -o rhv-upload -os rhvh_data -oc https://ibm-x3250m5-03.rhts.eng.pek2.redhat.com/ovirt-engine/api -op /tmp/rhvpasswd -oo rhv-cafile=/home/ca.pem -oo rhv-cluster=rhvh -oo rhv-verifypeer -oo rhv-direct --password-file /tmp/passwd -b ovirtmgmt
[   0.6] Opening the source -i libvirt -ic vpx://root.73.141/data/10.73.75.219/?no_verify=1 esx6.7-win2016-x86_64 -it vddk  -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=1F:97:34:5F:B6:C2:BA:66:46:CB:1A:71:76:7D:6B:50:1E:03:00:EA
[   2.3] Creating an overlay to protect the source from being modified
[   3.5] Opening the overlay
[   8.1] Inspecting the overlay
[  12.4] Checking for sufficient free disk space in the guest
[  12.4] Estimating space required on target for each disk
[  12.4] Converting Windows Server 2016 Standard to run on KVM
virt-v2v: warning: /usr/share/virt-tools/pnp_wait.exe is missing.  
Firstboot scripts may conflict with PnP.
virt-v2v: warning: there is no QXL driver for this version of Windows (10.0 
x86_64).  virt-v2v looks for this driver in 
/usr/share/virtio-win/virtio-win.iso

The guest will be configured to use a basic VGA display driver.
virt-v2v: This guest has virtio drivers installed.
[  20.0] Mapping filesystem data to avoid copying unused and blank areas
[  21.5] Closing the overlay
[  21.8] Assigning disks to buses
[  21.8] Checking if the guest needs BIOS or UEFI to boot
[  21.8] Initializing the target -o rhv-upload -oc https://ibm-x3250m5-03.rhts.eng.pek2.redhat.com/ovirt-engine/api -op /tmp/rhvpasswd -os nfs_data
[  23.2] Copying disk 1/1 to qemu URI json:{ "file.driver": "nbd", "file.path": "/var/tmp/rhvupload.36taQ0/nbdkit0.sock", "file.export": "/" } (raw)
    (100.00/100%)
[1239.7] Creating output metadata
[1250.5] Finishing off
2.Conversion can be finished without error 

3.Log into the rhv GUI,the windows 2016 can boot normally and can pass all normal checkpoints(network,rhv-apt and etc)

4.Install rhv-tools to windows2016 ,pls refer to screenshot

5.After installing,the guest can be restarted normally.

Result:
Windows guest can boot normally after installing rhv-tools.

Comment 11 liuzi 2019-10-18 03:45:49 UTC
Created attachment 1627028 [details]
install rhv-tools