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 1272119 - virt-v2v on W2K3 32-bit image fails
Summary: virt-v2v on W2K3 32-bit image fails
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard: v2v
Depends On:
Blocks: 1288337
TreeView+ depends on / blocked
 
Reported: 2015-10-15 14:20 UTC by François Cami
Modified: 2017-02-16 13:57 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-16 13:57:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
virt-v2v log (1.17 MB, text/plain)
2015-10-15 14:20 UTC, François Cami 		no flags Details
View All

Description François Cami 2015-10-15 14:20:10 UTC 
Created attachment 1083276 [details]
virt-v2v log

Description of problem:
After running virt-v2v on a W2K3 disk image, to a RHEV target, the resulting VM doesn't boot.
The error is:
"Error loading operating system"
right after "Booting from Hard Disk"
Comment 2 Richard W.M. Jones 2015-10-15 16:12:00 UTC 
We did a bit of investigation of this on IRC, and our best guess
so far is it's this issue with NTFS geometry:

https://forum.proxmox.com/threads/1629-P2V-with-Windows-2003-Server
Comment 3 Richard W.M. Jones 2015-10-15 16:17:45 UTC 
Reporter used the Hiren's Boot CD (an all-in-one rescue CD) to fix the MBR.

 ``the customer used "TestDisk" to do "Rewrite MBR to first sector" 
    and Advanced=>FS Utils=>"Rebuild BootSector"''
Comment 4 François Cami 2015-10-15 16:41:10 UTC 
From: http://www.netexpertise.eu/en/windows/hyper-v-error-loading-operating-system-after-running-disk2vhd.html

And: http://web.archive.org/web/20140831151616/http://www.xtralogic.com/testdisk_rebuild_bootsector.shtml

After virt-v2v and VM import in RHEV-M:

- Run Once VM on Hiren's boot cd
- Select "Dos Programs"
- Select "4. Recovery Tools..."
- Select "1. TestDisk"
- Select "No Log"
- Select Disk and "[Proceed ]"
- Select "[Intel ]"
- Select "[ MBR Code ]"
- Enter Y to "Write a new copy of MBR code to first sector?"
- Enter Y to "Write a new copy of MBR code, confirm?"
- Select "[Ok]"
- Select "[ Advanced ]"
- Select boot disk and "[ Boot ]"
- Select "[Rebuild BS]"
- Select "[ Write ]"
- Enter Y to "Write new NTFS boot sector, confirm?"
- Select "[ Quit ]", "[ Quit ]", "[ Quit ]", "[ Quit ]"
- Reboot the VM

After that, the VM boots.
Comment 5 François Cami 2015-10-15 16:42:22 UTC 
I forgot to add: the virt-v2v tools used were those from RHEL 7.2 Beta - in fact, the whole VM was running RHEL 7.2 Beta installed from scratch.
Comment 6 Richard W.M. Jones 2016-06-22 13:11:33 UTC 
Unclear to me what's going wrong here.  I'm fairly certain that
random rewriting the MBR isn't helping though.

Anyway, moving to RHEL 7.4.  This bug may not be solvable given
the lack of a way to reproduce it.
Comment 7 Richard W.M. Jones 2017-02-16 13:57:23 UTC 
Closing per discussion with the bug reporter.
Note You need to log in before you can comment on or make changes to this bug.