Bug 1194338

Summary: v2v conversion from vCenter to RHEV stalls and never completes
Product: Red Hat Enterprise Linux 7 Reporter: akotov
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: akotov, jbuchta, ptoscano
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-24 11:43:20 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:

Description akotov 2015-02-19 15:28:02 UTC
Description of problem:

[root@dhcp181-27 ~]# date

Thu Feb 19 09:53:07 EST 2015
[root@dhcp181-27 ~]# time virt-v2v -v -x -ic vpx://Administrator.1.1/LAB/RDU/esxhost.com?no_verify=1 -o rhev -os 1.1.1.1:/var/lib/exports/v2v --network rhevm rhel6_lvm




Version-Release number of selected component (if applicable):

libguestfs-1.28.1-1.18.el7.x86_64
libguestfs-tools-1.28.1-1.18.el7.noarch
libguestfs-tools-c-1.28.1-1.18.el7.x86_64
virt-v2v-1.28.1-1.18.el7.x86_64


How reproducible:


Steps to Reproduce:
1. Start conversion with above command

Actual results:

Process hangs at
--
[  101.817606] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel
  lvmetad is not active yet, using direct activation during sysinit
[  102.318493] bio: create slab <bio-1> at 1
  3 logical volume(s) in volume group "vg_data" now active

---

System is idle after that, nothing happens

Expected results:

V2V process goes on

Additional info:

sosreport gathered about an hour after conversion started is attached

Comment 3 Richard W.M. Jones 2015-02-19 15:49:52 UTC
According to the sosreport, you have
systemd-208-11.el7_0.6.x86_64 installed.  This version is not enough
to fix https://bugzilla.redhat.com/show_bug.cgi?id=1154778#c5 and
also indicates you didn't check that you have ALL of the updated
packages from http://people.redhat.com/~rjones/libguestfs-RHEL-7.1-preview/

Please now check that you have ALL the updated packages installed.

Comment 5 akotov 2015-02-20 10:00:27 UTC
Updated systemd, hangs at this point now

--
libguestfs: trace: aug_save = 0
libguestfs: trace: mv "/boot/initramfs-2.6.32-431.el6.x86_64.img" "/boot/initramfs-2.6.32-431.el6.x86_64.img.pre-v2v"
guestfsd: main_loop: proc 25 (aug_save) took 0.00 seconds
guestfsd: main_loop: new request, len 0x90
mv /sysroot/boot/initramfs-2.6.32-431.el6.x86_64.img /sysroot/boot/initramfs-2.6.32-431.el6.x86_64.img.pre-v2v
libguestfs: trace: mv = 0
libguestfs: trace: is_file "/sbin/dracut" "followsymlinks:true"
guestfsd: main_loop: proc 89 (mv) took 0.09 seconds
guestfsd: main_loop: new request, len 0x3c
libguestfs: trace: is_file = 1
libguestfs: trace: command "/sbin/dracut --add-drivers virtio virtio_ring virtio_blk virtio_net virtio_pci /boot/initramfs-2.6.32-431.el6.x86_64.img 2.6.32-431.el6.x86_64"
guestfsd: main_loop: proc 37 (is_file) took 0.00 seconds
guestfsd: main_loop: new request, len 0xd4
mount --bind /dev /sysroot/dev
mount --bind /dev/pts /sysroot/dev/pts
mount: mount point /sysroot/dev/pts does not exist
mount --bind /proc /sysroot/proc
mount --bind /sys/fs/selinux /sysroot/selinux
mount: special device /sys/fs/selinux does not exist
mount --bind /sys /sysroot/sys
mount --bind /sys/fs/selinux /sysroot/sys/fs/selinux
mount: mount point /sysroot/sys/fs/selinux does not exist
renaming /sysroot/etc/resolv.conf to /sysroot/etc/q08of7rr
cp /etc/resolv.conf /sysroot/etc/resolv.conf
/sbin/dracut --add-drivers virtio virtio_ring virtio_blk virtio_net virtio_pci /boot/initramfs-2.6.32-431.el6.x86_64.img 2.6.32-431.el6.x86_64



---

Comment 6 Richard W.M. Jones 2015-02-20 10:09:39 UTC
Please ensure you have updated ALL packages, not just systemd.

initramfs creation takes a long time -- that's expected.

To ensure things go as quickly as possible, read the requirements
section in the manual:
http://libguestfs.org/virt-v2v.1.html#resource-requirements

Comment 9 Richard W.M. Jones 2015-02-24 11:43:20 UTC
You really need to read the requirements here, particularly
as regard to network latency:
http://libguestfs.org/virt-v2v.1.html#resource-requirements

I'm marking this as a duplicate of bug 1146007, which is also
caused by there being too much latency between the virt-v2v
server and vCenter/ESX server.

*** This bug has been marked as a duplicate of bug 1146007 ***