Bug 1146832
| Summary: | virt-v2v fail to convert guest with disk type volume | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | tingting zheng <tzheng> | ||||
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 7.1 | CC: | dyuan, juzhou, mbooth, mzhan, ptoscano, rjones | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | V2V | ||||||
| Fixed In Version: | libguestfs-1.28.1-1.26.el7 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-11-19 06:57:38 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: |
|
||||||
As this is a new feature, not supported by old virt-v2v, I am moving this bug to a future version of RHEL 7. 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 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.
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 |
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: