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 1146832 - virt-v2v fail to convert guest with disk type volume
Summary: virt-v2v fail to convert guest with disk type volume
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.1
Hardware: Unspecified
OS: Unspecified
high
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-09-26 08:04 UTC by tingting zheng
Modified: 2015-11-19 06:57 UTC (History)
6 users (show)

Fixed In Version: libguestfs-1.28.1-1.26.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 06:57:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Detailed log file for converting guest with disk type volume (52.99 KB, text/plain)
2014-09-26 08:04 UTC, tingting zheng 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2183 0 normal SHIPPED_LIVE libguestfs bug fix and enhancement update 2015-11-19 08:18:42 UTC

Description tingting zheng 2014-09-26 08:04:54 UTC 
Created attachment 941426 [details]
Detailed log file for converting guest with disk type volume

Description
virt-v2v fail to convert guest with disk type volume

Version:
virt-v2v-1.27.53-1.1.el7.x86_64
libvirt-1.2.8-3.el7.x86_64
libguestfs-1.27.53-1.1.el7.x86_64


How reproducible:
100%

Steps to Reproduce:
1.On rhel7,libvirt/qemu-kvm have support for disk type volume,prepare a guest with disk type volume.
# virsh dumpxml rhel6.6-tzheng
    <disk type='volume' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source pool='default' volume='rhel6.6.img'/>
      <backingStore/>
      <target dev='vda' bus='virtio'/>
      <alias name='virtio-disk0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </disk>

2.Use virt-v2v to convert the guest.
# virt-v2v -o rhev -os 10.66.6.8:/var/v2v_export --network rhevm rhel6.6-tzheng
[   0.0] Opening the source -i libvirt rhel6.6-tzheng
virt-v2v: warning: <disk type='volume'> was ignored
[   0.0] Creating an overlay to protect the source from being modified
[   0.0] Opening the overlay
[   5.0] Initializing the target -o rhev -os 10.66.6.8:/var/v2v_export
virt-v2v: warning: cannot write files to the NFS server as 36:36, even 
though we appear to be running as root. This probably means the NFS client 
or idmapd is not configured properly.

You will have to chown the files that virt-v2v creates after the run, 
otherwise RHEV-M will not be able to import the VM.
[   5.0] Inspecting the overlay
virt-v2v: error: no root device found in this operating system image.

If reporting bugs, run virt-v2v with debugging enabled and include the 
complete output:

  virt-v2v -v -x [...]

Actual results：
warning info shows:virt-v2v: warning: <disk type='volume'> was ignored
virt-v2v fail to convert guest with disk type volume.

Expected results:
virt-v2v can convert guest with disk type volume.

Additional info:
Comment 2 Richard W.M. Jones 2014-09-26 08:09:44 UTC 
As this is a new feature, not supported by old virt-v2v, I am
moving this bug to a future version of RHEL 7.
Comment 3 Pino Toscano 2015-04-15 07:58:55 UTC 
Initial support for importing guests with disks stored as volumes has been recently added upstream:
https://github.com/libguestfs/libguestfs/commit/9001f61a402dc1820fd4c441e5cc78197c39b73b
https://github.com/libguestfs/libguestfs/commit/5da2ed95c11af6be6bee27f5b3dce8a6f3a29d74
https://github.com/libguestfs/libguestfs/commit/f7529522ab74d824c550d62953f0b8ecf1e61466
https://github.com/libguestfs/libguestfs/commit/08b1ba35cfaa526982911fe9f355ed9c168d942d
Comment 5 tingting zheng 2015-04-27 07:46:06 UTC 
Tested with:
libguestfs-1.28.1-1.29.el7.x86_64
virt-v2v-1.28.1-1.29.el7.x86_64

Steps:
1.Prepare a guest with disk type volume:
# virsh dumpxml rhel7
    <disk type='volume' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source pool='default' volume='rhel7.0.qcow2'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>


2.Use virt-v2v to convert the above guest.
[root@localhost ~]# virt-v2v -o rhev -os 10.66.90.115:/vol/v2v_auto/auto_export -n rhevm rhel7 -on disk-type-test-bytzheng
[   0.0] Opening the source -i libvirt rhel7
[   0.0] Creating an overlay to protect the source from being modified
[   1.0] Opening the overlay
[   9.0] Initializing the target -o rhev -os 10.66.90.115:/vol/v2v_auto/auto_export
virt-v2v: warning: cannot write files to the NFS server as 36:36, even 
though we appear to be running as root. This probably means the NFS client 
or idmapd is not configured properly.

You will have to chown the files that virt-v2v creates after the run, 
otherwise RHEV-M will not be able to import the VM.
[   9.0] Inspecting the overlay
[  25.0] Checking for sufficient free disk space in the guest
[  25.0] Estimating space required on target for each disk
[  25.0] Converting Red Hat Enterprise Linux Server release 7.1 Beta (Maipo) to run on KVM
virt-v2v: This guest has virtio drivers installed.
[ 111.0] Mapping filesystem data to avoid copying unused and blank areas
[ 112.0] Closing the overlay
[ 112.0] Copying disk 1/1 to /tmp/v2v.4kA0Mx/f7eca9dd-8763-4e32-acb6-50a07c439e6a/images/7093e759-e224-4cf7-af41-54939073507d/333c3627-e228-4a37-a2d8-a351f771cecb (qcow2)
    (100.00/100%)
[ 218.0] Creating output metadata
[ 218.0] Finishing off

3.After conversion,guest can be imported and booted successfully on rhev.

Refer to the above comments,move the bug to VERIFIED.
Comment 7 errata-xmlrpc 2015-11-19 06:57:38 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-2183.html
Note You need to log in before you can comment on or make changes to this bug.