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 868073

Summary: Convert windows guest fail
Product: Red Hat Enterprise Linux 6 Reporter: yuping zhang <yupzhang>
Component: virt-v2vAssignee: Matthew Booth <mbooth>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.4CC: dyasny, lcui, mzhan, rjones, rwu, tzheng
Target Milestone: rcKeywords: TestBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: virt-v2v-0.8.9-2.el6 Doc Type: Bug Fix
Doc Text:
Documentation not required. This bug did not appear in RHEL.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-21 10:59:30 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
libguestfs debug and trace log none

Description yuping zhang 2012-10-19 03:06:56 UTC
Description of problem:
Use virt-v2v convert windows guest,it will fail with error
mkdir: mkdir: /Temp/V2V: No such file or directory at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 204.
 at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/Windows.pm line 476


Version-Release number of selected component (if applicable):
virt-v2v-0.8.9-1.el6.x86_64
libguestfs-1.16.32-2.el6.x86_64
libvirt-0.10.2-4.el6.x86_64
febootstrap-3.12-2.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1.# virt-v2v -ic qemu+ssh://10.66.72.24/system -os default kvm-win7-x86_64
root.72.24's password:
root.72.24's password:
kvm-win7-x86_64.img: 100% [==================================================================]D 0h03m37s
mkdir: mkdir: /Temp/V2V: No such file or directory at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 204.
 at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/Windows.pm line 476
 
Actual results:
As above

Expected results:
Convert windows guest should successfully.

Additional info:
1.Convert Linux guest successfully.

Comment 1 yuping zhang 2012-10-19 04:46:17 UTC
I think it maybe a libguestfs bug.
This issue still reproduce on virt-v2v-0.8.7-6.el6.x86_64 after upgrade libguestfs to libguestfs-1.16.32-2.el6.x86_64.
Set TestBlocker Keywords as it blocks all windows guests.

Comment 2 Matthew Booth 2012-10-19 08:31:51 UTC
The v2v code in question hasn't changed recently and looks correct, so at first glance I suspect a change in libguestfs. Could you please supply the output of the v2v run with LIBGUESTFS_DEBUG=1 and LIBGUESTFS_TRACE=1?

Comment 3 yuping zhang 2012-10-19 08:48:15 UTC
Created attachment 629875 [details]
libguestfs debug and trace log

# LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 virt-v2v -ic xen+ssh://10.66.72.23/ -os default xen-hvm-winxp-i386 > debug.log 2>&1
root.72.23's password: 
root.72.23's password: 

Attached the log.

Comment 4 Richard W.M. Jones 2012-10-19 08:50:32 UTC
(This is upstream, but I'll assume the code is
similar in RHEL).

In lib/Sys/VirtConvert/Converter/Windows.pm:

        eval { $path = $g->case_sensitive_path($path) };

        # case_sensitive_path will fail if the path doesn't exist
        if ($@) {
            $g->mkdir($path);
        }

The assumption there is not correct since we made the
following change in libguestfs to fix bug 840115:

https://github.com/libguestfs/libguestfs/commit/973581780d8a006f336684fef6762801402d775d

Small patch to follow ...

Comment 5 Richard W.M. Jones 2012-10-19 09:05:27 UTC
Patch posted:
https://www.redhat.com/archives/libguestfs/2012-October/msg00106.html

Comment 7 Matthew Booth 2012-10-19 12:45:46 UTC
I've tested the patch and it works fine.

Comment 9 yuping zhang 2012-10-25 03:41:30 UTC
Verified this issue with:
virt-v2v-0.8.9-2.el6.x86_64
libvirt-0.10.2-5.el6.x86_64
libguestfs-1.16.32-2.el6.x86_64

# virt-v2v -ic qemu+ssh://10.66.72.24/system -os default kvm-win7-x86_64
root.72.24's password: 
root.72.24's password: 
kvm-win7-x86_64.img: 100% [==========================================]D 0h03m49s
virt-v2v: WARNING: The connected hypervisor does not support feature pae.
virt-v2v: WARNING: No mapping found for bridge interface breth0 in config file. The converted guest may not start until its network interface is updated.
virt-v2v: kvm-win7-x86_64 configured with virtio drivers.

So change the bug status to verified.

Comment 11 errata-xmlrpc 2013-02-21 10:59:30 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.

http://rhn.redhat.com/errata/RHBA-2013-0477.html