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 620698 - v2v detects remote libvirt volume as 0 size
Summary: v2v detects remote libvirt volume as 0 size
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-v2v
Version: 6.0
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Matthew Booth
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 621116
TreeView+ depends on / blocked
 
Reported: 2010-08-03 09:49 UTC by Rita Wu
Modified: 2013-07-03 01:41 UTC (History)
6 users (show)

Fixed In Version: virt-v2v-0.6.2-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 621116 (view as bug list)
Environment:
Last Closed: 2010-11-10 21:54:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
log from virt-inspect (329.55 KB, text/plain)
2010-08-03 09:49 UTC, Rita Wu
no flags Details

Description Rita Wu 2010-08-03 09:49:10 UTC
Created attachment 436229 [details]
log from virt-inspect

Description of problem:
# virsh -c xen+ssh://10.66.93.xxx list --all
root.93.xxx's password: 
 Id Name                 State
----------------------------------
  0 Domain-0             running
  - lvm_xenhvm_rhel55-64_rwu shut off
  - lvm_xenhvm_rwu       shut off
  - RHEL5.4-64bit        shut off

In 10.66.93.xxx host:
# lvs
  LV                       VG         Attr   LSize   Origin    Snap%  Move Log Copy%  Convert                      
  lvm_xenhvm_rhel55-64_rwu VolGroup00 -wi-a-   5.00G                                         
  lvm_xenhvm_rwu           VolGroup00 -wi-a-   5.00G         

Version-Release number of selected component (if applicable):
virt-v2v-0.6.1-2.el6.x86_64
libguestfs-1.2.7-1.21.el6.x86_64

How reproducible:
always

Steps to Reproduce:

#LIBGUESTFS_TRACE=1 virt-v2v -ic xen+ssh://10.66.93.xxx-o rhev -osd
 10.66.90.115:/vol/v2vwulinglu/wulingluv2v/fcp_export lvm_xenhvm_rhel55-64_rwu  2>&1 > lvm_xenhvm_rhel55-64_rwu.log
root.93.xxx's password: 
root.93.xxx's password: 
virt-v2v: Didn't write full volume. Expected 0
bytes, wrote 5368709120 bytes.
virt-v2v: Failed to unmount
10.66.90.115:/vol/v2vwulinglu/wulingluv2v/fcp_export. Command exited with
status 16. Output was: umount.nfs: /tmp/S0gBSMNJlz: device is busy
umount.nfs: /tmp/S0gBSMNJlz: device is busy

 virt-v2v: Failed to remove mount directory /tmp/S0gBSMNJlz: Device or
  resource busy



  
Actual results:
as steps mentioned

Expected results:
v2v can convert a LVM based guest

Additional info:
# virsh -c xen+ssh://10.66.93.xxx dumpxml lvm_xenhvm_rhel55-64_rwu
root.93.xxx's password: 
<domain type='xen'>
  <name>lvm_xenhvm_rhel55-64_rwu</name>
  <uuid>ebb0b973-548c-810e-6571-0fa68270f729</uuid>
  <memory>524288</memory>
  <currentMemory>524288</currentMemory>
  <vcpu>1</vcpu>
  <os>
    <type arch='x86_64' machine='xenfv'>hvm</type>
    <loader>/usr/lib/xen/boot/hvmloader</loader>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
    <disk type='block' device='disk'>
      <driver name='phy'/>
      <source dev='/dev/mapper/VolGroup00-lvm_xenhvm_rhel55--64_rwu'/>
      <target dev='hda' bus='ide'/>
    </disk>
    <interface type='bridge'>
      <mac address='00:16:36:49:5f:2f'/>
      <source bridge='xenbr0'/>
      <script path='vif-bridge'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target port='0'/>
    </console>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
  </devices>
</domain>

Comment 2 Gunther Schlegel 2010-08-03 10:00:10 UTC
This also affects RHEV 2.2.

Comment 3 RHEL Program Management 2010-08-03 10:07:55 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 4 Matthew Booth 2010-08-03 10:39:42 UTC
I think this might be a libvirt problem. Could you please provide the output of the following command:

virsh -c xen+ssh://10.66.93.xxx vol-info /dev/mapper/VolGroup00-lvm_xenhvm_rhel55--64_rwu

Obviously replace .xxx with the real IP.

Comment 5 Gunther Schlegel 2010-08-03 19:49:24 UTC
[root@island tmp]$ virt-v2v -o rhev -ic xen+ssh://root.de -osd lie2.mb.riege.local:/export/RHEV/images --network XYZ XYZ.riege.com_64
virt-v2v: Didn't write full volume. Expected 58
 bytes, wrote 42949672960 bytes.
virt-v2v: Failed to unmount lie2.mb.riege.local:/export/RHEV/images. Command exited with status 1. Output was: umount: /tmp/U6JRfF8Kz2: device is busy
umount: /tmp/U6JRfF8Kz2: device is busy

virt-v2v: Failed to remove mount directory /tmp/U6JRfF8Kz2: Device or resource busy
[root@island tmp]$ Write failed: Broken pipe


[root@island ~]$ virsh -c xen+ssh://hilton.riege.de vol-info /dev/mapper/SataVirtualHostsVG-XYZ.riege.com_xvda
error: failed to get vol '/dev/mapper/SataVirtualHostsVG-XYZ.riege.com_xvda'
error: invalid storage volume pointer in no storage vol with matching path


[root@hilton xen]$ cat /etc/xen/XYZ.riege.com_64 
name = "XYZ.riege.com_64"
uuid = "1e62f0b3-7695-0424-851a-3ac41cfd4b76"
maxmem = 4096
memory = 512
vcpus = 2
maxcpus = 4
bootloader = "/usr/bin/pygrub"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
vfb = [ "type=vnc,vncunused=1,keymap=de" ]
disk = [ "phy:/dev/SataVirtualHostsVG/XYZ.riege.com_xvda,xvda,w" ]
vif = [ "mac=00:16:3e:18:4c:0c,bridge=br17" ]


[root@hilton xen]$ rpm -q libvirt
libvirt-0.6.3-33.el5

Comment 6 Rita Wu 2010-08-04 09:15:16 UTC
Thanks Gunther, and I got the same result:
# rpm -qa|grep libvirt
libvirt-0.8.1-21.el6.x86_64
libvirt-cim-0.5.8-3.el6.x86_64
fence-virtd-libvirt-0.2.1-4.el6.x86_64
libvirt-python-0.8.1-21.el6.x86_64
libvirt-java-0.4.5-2.el6.noarch
libvirt-client-0.8.1-21.el6.x86_64
libvirt-qpid-0.2.22-2.el6.x86_64


# virsh -c xen+ssh://10.66.93.217 vol-info lvm_xenhvm_rhel55-64_rwu
root.93.217's password: 
error: failed to get vol 'lvm_xenhvm_rhel55-64_rwu'
error: invalid storage volume pointer in no storage vol with matching path

Comment 7 Rita Wu 2010-08-04 09:53:06 UTC
Hello Matt,

As we talked in IRC, I'll leave this bug to you to handle: stay as blocker in 6.0 or move the flag to 6.1.

Thanks,
Linglu

Comment 8 Matthew Booth 2010-08-04 15:16:47 UTC
So this didn't have anything to do with libvirt after all. I was relying on the output of stat to detect volume size, which doesn't work for block devices. Fix posted here:

http://www.redhat.com/archives/libguestfs/2010-August/msg00014.html

Comment 9 Matthew Booth 2010-08-10 13:54:50 UTC
Fixed in virt-v2v-0.6.2-1.el6.

Comment 10 Rita Wu 2010-08-11 10:42:23 UTC
Verify version:
virt-v2v-0.6.2-1.el6.x86_64
libguestfs-1.2.7-1.23.el6.x86_64
libvirt-0.8.1-21.el6.x86_64
augeas-0.7.2-2.el6.x86_64

Now it can successfully detect remote libvirt volume and convert it successfully.
#virt-v2v -ic xen+ssh://10.66.93.217  -o rhev -osd 10.66.90.115:/vol/v2vwulinglu/wulingluv2v/iscsi_export lvm_xenhvm_rhel55-64_rwu 
root.93.217's password: 
root.93.217's password: 
virt-v2v: lvm_xenhvm_rhel55-64_rwu configured with virtio drivers

Comment 11 releng-rhel@redhat.com 2010-11-10 21:54:36 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.