[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Libguestfs] P2V conversion failed with "/run/lvm/lvmetad.socket: connect failed: No such file or directory"



Greetings Richard,
Thanks a ton for the pointers. We have finally accomplished the conversion, after upgrading the Conversion server to FC 22.
Appreciate your support.

Regards,
Ravi C

On Wed, Nov 4, 2015 at 9:35 PM, Richard W.M. Jones <rjones redhat com> wrote:
On Wed, Nov 04, 2015 at 06:08:16AM -0800, Tejas Gadaria wrote:
> After starting conversation, at the time of decompressing kernel, after
> loading modules by iso we are getting below error,
>
> *file -zb
> /sysroot/lib/modules/3.17.4-301.fc21.x86_64/kernel/arch/x86/crypto/blowfish-x86_64.ko.xz*
> *libguestfs: trace: file = "XZ compressed data"*
> *libguestfs: trace: file_architecture = NULL (error)*
> *virt-v2v: error: libguestfs error: file_architecture: unknown
> architecture: *
> */lib/modules/3.17.4-301.fc21.x86_64/kernel/arch/x86/crypto/blowfish-x86_64.ko.xz*

This was fixed upstream:

https://github.com/libguestfs/libguestfs/commit/7291b226d1b08c762ae2f2715a2ac9ed7b8d5d14

With a more recent virt-v2v it will work fine, as in this example:

$ virt-builder fedora-22

$ guestfish --ro -a fedora-22.img -i find /lib/modules | grep xz | head
/4.0.4-301.fc22.x86_64/kernel/arch/x86/crypto/blowfish-x86_64.ko.xz
/4.0.4-301.fc22.x86_64/kernel/arch/x86/crypto/camellia-aesni-avx-x86_64.ko.xz
/4.0.4-301.fc22.x86_64/kernel/arch/x86/crypto/camellia-aesni-avx2.ko.xz
/4.0.4-301.fc22.x86_64/kernel/arch/x86/crypto/camellia-x86_64.ko.xz
/4.0.4-301.fc22.x86_64/kernel/arch/x86/crypto/cast5-avx-x86_64.ko.xz
/4.0.4-301.fc22.x86_64/kernel/arch/x86/crypto/cast6-avx-x86_64.ko.xz
/4.0.4-301.fc22.x86_64/kernel/arch/x86/crypto/crc32-pclmul.ko.xz
/4.0.4-301.fc22.x86_64/kernel/arch/x86/crypto/crc32c-intel.ko.xz
/4.0.4-301.fc22.x86_64/kernel/arch/x86/crypto/crct10dif-pclmul.ko.xz
/4.0.4-301.fc22.x86_64/kernel/arch/x86/crypto/des3_ede-x86_64.ko.xz

$ virt-v2v -i disk fedora-22.img -o null
[   0.0] Opening the source -i disk fedora-22.img
[   0.1] Creating an overlay to protect the source from being modified
[   0.6] Initializing the target -o null
[   0.6] Opening the overlay
[  17.0] Inspecting the overlay
[  19.7] Checking for sufficient free disk space in the guest
[  19.7] Estimating space required on target for each disk
[  19.7] Converting Fedora 22 (Twenty Two) to run on KVM
virt-v2v: warning: /files/boot/grub2/device.map/hd0 references unknown
device "vda".  You may have to fix this entry manually after conversion.
virt-v2v: This guest has virtio drivers installed.
[  37.3] Mapping filesystem data to avoid copying unused and blank areas
[  38.2] Closing the overlay
[  38.4] Checking if the guest needs BIOS or UEFI to boot
[  38.4] Assigning disks to buses
[  38.4] Copying disk 1/1 to /var/tmp/null.5APlFC/sda (raw)
    (100.00/100%)
[  39.5] Creating output metadata
[  39.5] Finishing off

Rich.

--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]