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.

Created attachment 1414306 [details]
Fast Startup

Description of problem:
When trying to migrate Windows 2016 Server using v2v, the migration fails.  Error in the debug output indicates a filesystem corruption for the VM disks.  CentOS VM migration in the same environment works without issue.

Version-Release number of selected component (if applicable):
RHV 4.2.2 using the v2v-wrapper
ManageIQ nightly using v2v migration tooling
virt-v2v-1.36.10-6.el7.x86_64

How reproducible:
Every time.


Steps to Reproduce:
1. Using ManageIQ, create a infrastructure mapping and migration plan for the Windows 2016 Server VM
2. Initiate the migration
3. Review /var/log/vdsm/import/<associated_log_file> for errors. 

Actual results:
VM fails to migrate.

Expected results:
VM to complete migration.

Additional info:
This is migrating from vSphere 6.5 to RHV 4.2 using the v2v bits in ManageIQ.
Also verified fast startup is disabled in the registry.

Location of full virt-v2v debug:  http://file.rdu.redhat.com/bthurber/logs/v2v-import-20180327T232031-11618.log

Verified Windows 2008 Server in same environment migrates from VMware to RHV.

I'll test 2012 server and report back results.

I was able to get migrations of Windows 2008, 2012, 2016 from VMware to RHV.  In order for this to work I had to gracefully power off each VM prior to migration.  

Every time the VM was powered on, it failed to migrate regardless of Windows OS version.  The error was always related to NTFS being in an inconsistent state.

Since the root cause is likely to be the same, let's put all
these reports into the single bug.

*** This bug has been marked as a duplicate of bug 1561828 ***