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 1153730 - Booting windows 2008 R2 if=virtio gets BSOD
Summary: Booting windows 2008 R2 if=virtio gets BSOD
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.1
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard: V2V
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-16 16:20 UTC by Richard Smith
Modified: 2015-11-16 01:26 UTC (History)
10 users (show)

Fixed In Version: libguestfs-1.27.64-1.1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 13:46:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
output from virt-v2v and the qemu-kvm script that boots the image (457.74 KB, text/plain)
2014-10-16 16:20 UTC, Richard Smith 		no flags Details
BSOD screen capture (17.69 KB, image/png)
2014-10-16 16:21 UTC, Richard Smith 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0303 0 normal SHIPPED_LIVE libguestfs bug fix and enhancement update 2015-03-05 17:34:44 UTC

Description Richard Smith 2014-10-16 16:20:49 UTC 
Created attachment 947672 [details]
output from virt-v2v and the qemu-kvm script that boots the image

Description of problem:
We use virt-v2v on a Windows 2008 R2 boot image (qcow2) to produce an image with virtio support for booting in KVM.  The kvm image boots to a BSOD, unless we change the if=virtio to if=ide.


Version-Release number of selected component (if applicable):
libguestfs-1.27.63-1.1.el7.x86_64
virt-v2v-1.27.63-1.1.el7.x86_64

How reproducible:
100% reproducible

Steps to Reproduce:
1. use virt-v2v to convert windows 2008 image to libvirt image

virt-v2v -x -v -i disk /mnt/migmu -os /tmp --network default2_Medium/RHET_2K8R2EESP1_2_Medium-sdb -o qe
 
2. modify the resulting script to allow vnc access

3. run the qemu-kvm script produced in #1 and observe the console output from a vncviewer



Actual results:
converted qcow2 image boots momentarily and suffers a BSOD


Expected results:
converted qcow2 image boots to a login screen.


Additional info:
Image comes from vmware image where it worked properly.
Comment 1 Richard Smith 2014-10-16 16:21:44 UTC 
Created attachment 947673 [details]
BSOD screen capture
Comment 3 Richard W.M. Jones 2014-10-16 18:07:32 UTC 
The error is 0x0000007B which just indicates that NT couldn't get
past the boot loader.  I already checked with Richard that he has
seabios 1.7.5 installed.
Comment 4 tingting zheng 2014-10-17 02:27:11 UTC 
Right now,most of windows guests will BSOD after conversion,see bug 1145916.
Comment 5 Richard W.M. Jones 2014-10-17 07:25:01 UTC 
I've added blocker to bug 1145916.  I wasn't aware that there were
still problems with Windows guests, but we can't ship v2v if so.
(FWIW I can't reproduce these).

I'm going to look at this one today.
Comment 6 Richard W.M. Jones 2014-10-17 11:15:11 UTC 
(In reply to Richard Smith from comment #0)
> Steps to Reproduce:
> 1. use virt-v2v to convert windows 2008 image to libvirt image
> 
> virt-v2v -x -v -i disk /mnt/migmu -os /tmp --network
> default2_Medium/RHET_2K8R2EESP1_2_Medium-sdb -o qe

I think the copy and paste chewed this up.  The command typed
here seems to have been:

virt-v2v -x -v -i disk /mnt/migrate/convert/RHET_2K8R2EESP1_2_Medium/RHET_2K8R2EESP1_2_Medium-sdb -o qemu -os /t
mp --network default

I'm going to assume that the disk named ('sdb') is really the
boot disk.  Of course this command won't work if the data disk
is converted, since it doesn't have an OS.  However I would
expect to have seen a different error message (from virt-v2v) if
it was the data disk.

But could you check this?  (Also if it's something like a guest
with the Windows systemroot on D:\ then it's well outside our
experience).

Also did the guest have VMware tools installed before conversion?
Comment 7 Richard W.M. Jones 2014-10-17 16:20:39 UTC 
I believe the following two commits will fix this (and hopefully
won't break anything else).

https://github.com/libguestfs/libguestfs/commit/4f6033c3f4428f2c0033dfc256e71f05db17c3c2
https://github.com/libguestfs/libguestfs/commit/97c96ed6702cb7b4dfcc5acd08a29cb6f2b70b54

This will be added to >= 1.27.64.
Comment 9 tingting zheng 2014-10-20 10:11:25 UTC 
Tested with:
libguestfs-1.28.1-1.1.el7.x86_64
libguestfs-winsupport-7.1-4.el7.x86_64
virt-v2v-1.28.1-1.1.el7.x86_64
virtio-win-1.7.2-1.el7.noarch

Use virt-v2v to convert win2008R2 guests to rhev and kvm,guests can be booted with virtio disks successfully on both rhev and kvm,so move the bug to VERIFIED.
Comment 13 errata-xmlrpc 2015-03-05 13:46:31 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0303.html
Note You need to log in before you can comment on or make changes to this bug.