Tejas Gadaria
2015-Nov-04 14:08 UTC
Re: [Libguestfs] P2V conversion failed with "/run/lvm/lvmetad.socket: connect failed: No such file or directory"
Hi Richard, Thanks for your response, We have followed the steps mentioned in https://www.redhat.com/archives/libguestfs/2015-November/msg00015.html Now we are able to connect the V2V Conversion Server from Physical server after booting from livecd. Once ssh connection established, "Start Conversion" opens up another UI which has necessary info. of hardware (eg. CPU, RAM, HDD Capacity, No. of NICs etc..) 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* *If reporting bugs, run virt-v2v with debugging enabled and include the * *complete output:* * virt-v2v -v -x [...]* *libguestfs: trace: close* *libguestfs: closing guestfs handle 0xb7aea0 (state 2)* *libguestfs: trace: internal_autosync* It would be very helpful if you can provide some pointers on this. I have attached log file for reference. Thanks, Tejas On Tue, Nov 3, 2015 at 7:01 AM, Richard W.M. Jones <rjones@redhat.com> wrote:> On Tue, Nov 03, 2015 at 03:03:21PM +0530, Chengappa Changz wrote: > > Hello Rich, > > Greetings! > > > > It was great connecting with you and, I would like to thank you for your > > time and being patient on answering all our queries. > > > > However, referring to the link -> > > http://libguestfs.org/virt-p2v.1.html#how-virt-p2v-works we have a > > ambiguity -> i.e. under the section "GUI INTERACTIVE CONFIGURATION" we > have > > "When you start virt-p2v, you'll see a graphical configuration dialog > that > > walks you through connection to the conversion server," > > Have a look at what I wrote here: > > https://www.redhat.com/archives/libguestfs/2015-November/msg00015.html > > which will show you how you can diagnose the real problem. > > > As of now we are using *virt-manager* to get this GUI INTERACTIVE > > CONFIGURATION as we are not sure if this is the correct way of invoking > GUI, > > While you can use virt-manager for testing things, that's not the > correct way to run virt-p2v to convert a physical machine. > > Rich. > > > Attaching the screen shots of the process till where we were *successful > > using the virt-manger* > > > > It would be highly appreciated if you can let us know how we can invoke > > this interactive GUI with-out virt-manager so that we could proceed > further > > with the conversion. > > > > *Thanks & Regards,* > > > > *Chengappa M.R* > > > > Software Designer > > Network Function Virtualization | Communication Media Solutions > > > > cm-r@hp.com > > M +91 944 934 9647 > > Hewlett Packard Company > > Bangalore, > > India. > > > > > > Please print thoughtfully > > > > > > On 3 November 2015 at 04:45, Richard W.M. Jones <rjones@redhat.com> > wrote: > > > > > On Mon, Nov 02, 2015 at 10:59:35PM +0000, Richard W.M. Jones wrote: > > > > On Mon, Nov 02, 2015 at 06:51:20PM +0530, Ravi Chaudhary wrote: > > > > > Sorry, attached herein is the screenshot > > > > > > > > This error "unexpected end of file waiting for password prompt" is > > > > this bug: > > > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1167916#c4 > > > > > > > > Although it is a bug in virt-p2v -- it should print a clearer error > > > > message -- what it really means in this case is that you've got the > > > > wrong server name, user or password, or that virt-p2v is unable to > > > > contact the server (perhaps because of firewall or network problems). > > > > > > And by "server", of course I mean the virt-v2v conversion server. > > > > > > Rich. > > > > > > -- > > > Richard Jones, Virtualization Group, Red Hat > > > http://people.redhat.com/~rjones > > > Read my programming and virtualization blog: http://rwmj.wordpress.com > > > virt-df lists disk usage of guests without needing to install any > > > software inside the virtual machine. Supports Linux and Windows. > > > http://people.redhat.com/~rjones/virt-df/ > > > > > > > > > -- > Richard Jones, Virtualization Group, Red Hat > http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-p2v converts physical machines to virtual machines. Boot with a > live CD or over the network (PXE) and turn machines into KVM guests. > http://libguestfs.org/virt-v2v >
Richard W.M. Jones
2015-Nov-04 16:05 UTC
Re: [Libguestfs] P2V conversion failed with "/run/lvm/lvmetad.socket: connect failed: No such file or directory"
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
Ravi Chaudhary
2015-Nov-05 06:00 UTC
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 >
Seemingly Similar Threads
- Re: P2V conversion failed with "/run/lvm/lvmetad.socket: connect failed: No such file or directory"
- Re: P2V conversion failed with "/run/lvm/lvmetad.socket: connect failed: No such file or directory"
- FC22: virt-p2v-make-kickstart/livecd-creator doesn't build
- Re: FC22: virt-p2v-make-kickstart/livecd-creator doesn't build
- Re: P2V conversion failed with "/run/lvm/lvmetad.socket: connect failed: No such file or directory"