Bug 1883750

Summary: [v2v][Doc] Windows VM cannot be imported if hibernation is enabled
Product: Container Native Virtualization (CNV) Reporter: Fabien Dupont <fdupont>
Component: DocumentationAssignee: Avital Pinnick <apinnick>
Status: CLOSED CURRENTRELEASE QA Contact: Md Nadeem <mnadeem>
Severity: high Docs Contact:
Priority: high    
Version: 2.4.1CC: bthurber, cnv-qe-bugs, ctomasko, mguetta, mnadeem
Target Milestone: ---   
Target Release: 2.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-03 09:59:08 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:

Description Fabien Dupont 2020-09-30 06:57:08 UTC
Document URL:

Section Number and Name: Importing a VMware virtual machine or template with the virtual machine wizard

Describe the issue: 
When hibernation is enabled in a Windows virtual machine, the import will fail because virt-v2v considers that the filesystem hasn't been cleanly closed. This is a limitation of ntfs-3g.

Suggestions for improvement: 
We could add a known issue or a warning somewhere else to tell customers that they need to temporarily disable hibernation. The text could be something like:

When importing a Windows virtual machine, hibernation must be disabled before the virtual machine is shutdown. If it is enabled, the import will fail because the operating system is not at rest and the VirtIO drivers installation would fail. Once the import is finished, hibernation can be re-enabled. The steps to disable or enable hibernation are detailed in https://docs.microsoft.com/en-us/troubleshoot/windows-client/deployment/disable-and-re-enable-hibernation.

Additional information:

Comment 2 Md Nadeem 2020-10-23 12:46:23 UTC

Comment 3 Avital Pinnick 2020-11-03 09:59:08 UTC
Changes merged.