Description of problem:
when convert RHEL-3.9 xen hvm image to rhev image, it will failed with error "All of your loopback devices are in use" at the step of mkinitrd. cat /proc/partitions before mkinird show none loop device has been used.
--- /usr/lib/perl5/vendor_perl/5.8.8/Sys/VirtV2V/GuestOS/RedHat.pm.orig 2010-04-19 10:28:15.000000000 -0400
+++ /usr/lib/perl5/vendor_perl/5.8.8/Sys/VirtV2V/GuestOS/RedHat.pm 2010-04-21 10:49:54.000000000 -0400
@@ -1114,6 +1114,8 @@
+ print STDERR $g->debug("sh", ["cat /proc/partitions 2>&1"]);
$g->command(["/sbin/mkinitrd", @preload_args, $initrd, $version]);
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a rhel-3.9 xen hvm guest, (on intel host in this case, both i386 and x86_64 guest are ok)
2. create a xml file as attached rhel-3.9-i386-xen-hvm.xml
3. modify /usr/share/doc/virt-v2v-0.4.10/virt-v2v.conf, see attachment
4. place the necessary packages in the directory /var/lib/virt-v2v/software which is specified in virt-v2v.conf
$ tree /var/lib/virt-v2v/software/rhel/3/
5. convert the images to a rhev storage
$ virt-v2v -f /usr/share/doc/virt-v2v-0.4.10/virt-v2v.conf -i libvirtxml -o rhev -osd X.X.X.X:/vol/v2v/export rhel-3.9-i386-hvm.xml
converting failed with error "All of your loopback devices are in use" at the step of mkinitrd, please refer to the attached log: no_loop_error.log
converting should pass.
Created attachment 408107 [details]
Created attachment 408111 [details]
Created attachment 408115 [details]
$ export LIBGUESTFS_TRACE=1
$ export LIBGUESTFS_DEBUG=1
$ virt-v2v -f /usr/share/doc/virt-v2v-0.4.10/virt-v2v.conf -i libvirtxml -o rhev -osd x.x.x.x:/export rhel-3.9-i386-hvm.xml
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Can you confirm that this bug is supposed to be against RHEL 6? I just hit this in RHEL 5 and have a fix for that. It's caused by the loop module not being loaded. It seems loop is compiled in to the Fedora kernel, so we never hit this. I'd expect it to be compiled in on RHEL 6 too.
(In reply to comment #6)
> Can you confirm that this bug is supposed to be against RHEL 6? I just hit this
> in RHEL 5 and have a fix for that. It's caused by the loop module not being
> loaded. It seems loop is compiled in to the Fedora kernel, so we never hit
> this. I'd expect it to be compiled in on RHEL 6 too.
We hit the problem with el5 rpm package, but I didn't find virt-v2v in RHEL 5 product, so it can make you confused. I'm moving it to Virt Tools product.
This is fixed upstream: