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

Greetings Richard,

Thanks for the pointer. It was helpful. (Note: We have 2 physical machines,
one is p2v machine & the other is conversion server. Both the machines have
been updated with  "*yum install qemu libvirt-client virt-manager
virt-viewer guestfish libguestfs-tools virt-top*")

We have couple of questions for the exact functioning of virt-p2v:

   1. We are unable to locate the following command for injecting the ssh
   private key of p2v machine:

   *virt-p2v-make-kickstart p2v.ks --inject-ssh-identity id_rsa*

   *virt-p2v-make-kickstart: unrecognized option
'--inject-ssh-identity'*

   *virt-p2v-make-kickstart: problem parsing the command line arguments*
   2. *Further we are also unable to find any executable "virt-p2v" on
the
   p2v machine*
   3. *We are able to view the virt-p2v in GUI mode, only after booting the
   hardware using the ISO image, generated on p2v machine (The hardware used
   for booting is the same physical p2v machine). Is this the right way? We
   are observing the following error:*


*Would you be able to provide us with exact steps required to implement the
virt-p2v? *

On Mon, Nov 2, 2015 at 2:18 PM, Richard W.M. Jones <rjones@redhat.com>
wrote:
> On Mon, Nov 02, 2015 at 12:06:41AM +0530, Ravi Chaudhary wrote:
> > Greetings Richard,
> >
> > To add to the above information, we are following the understated
steps:
> >
> >    1. We have 2 BL460c (Gen8) with Fedora 21 installed. Both the
> >    machines(BL1 & BL2) have been updated with virt-v2v packages
> >    2. On BL1, we execute the following commands:
> >    1. virt-p2v-make-kickstart fedora
> >       2. livecd-creator p2v.ks
> >    3. After creating the "livecd-p2v-2xxxxxx.iso" file, we
launch the
> >    'virt-manager', from BL1
>
> So hang on, you're running virt-p2v in a VM?
>
> While we do sometimes run virt-p2v in a VM do operational testing of
> P2V, this isn't the way to convert a physical machine.  You have to
> burn the ISO to a CD and boot the physical machine using it.
>
> (Alternatives exist: use livecd-iso-to-pxeboot; or possibly your blade
> hardware will let you use the ISO directly as a virtual CD-ROM)
>
> Anyway, running virt-p2v in a VM isn't going to work ...
>
> Rich.
>
> >    4. Create a new virtual machine using the 'File' option
> >    5. Click on 'Begin Installation' after step 4
> >    6. User is shown the 'Conversion Server' GUI login screen
> >    7. Enter the credentials & click on 'Test Connection with
Conversion
> >    Server'
> >    8. 'Next' button is enabled
> >    9. Click on 'Create p2v' and after sometime, the process is
exited
> with
> >    status "-1"
> >    10. The earlier attached log file is generated in BL2 (conversion
> >    server) under /tmp/virt-XXXX directory
> >
> > Hope it helps to solve the issue.
> >
> >
> > Regards,
> >
> > Ravi Chaudhary
> >
> > On Sun, Nov 1, 2015 at 9:23 AM, Tejas Gadaria
<refond.gmrt@gmail.com>
> wrote:
> >
> > > Hi Richard,
> > >
> > > Thanks for your replay,
> > >
> > > We are using Fedora 21 with SAS drive and RAID 0 config on both
> Physical
> > > and conversion server.
> > >
> > >
> > > Thanks,
> > > Tejas
> > >
> > > On Sat, Oct 31, 2015 at 11:50 PM, Richard W.M. Jones <
> rjones@redhat.com>
> > > wrote:
> > >
> > >> On Sat, Oct 31, 2015 at 06:11:05PM +0000, Richard W.M. Jones
wrote:
> > >> >
> > >> > On Sat, Oct 31, 2015 at 10:14:32PM +0530, Tejas Gadaria
wrote:
> > >> > > Hi,
> > >> > >
> > >> > > We are trying to do P2V conversion with virt-p2v.
> > >> > >
> > >> > > we have conversion server (virt-p2v) and physical
server
> (virt-p2v)
> > >> server
> > >> > > configured as per below documentation.
> > >> > >
> > >> > >
> > >>
> http://libguestfs.org/virt-p2v.1.html#kernel-command-line-configuration
> > >> > >
> > >> > > After "Start Conversion" from GUI
interface, we are conversion
> fails
> > >> with
> > >> > > "/run/lvm/lvmetad.socket: connect failed: No
such file or
> directory"
> > >> Error.
> > >> > >
> > >> > > Logs are attached for more details. Also FYI, we
are using BL460c
> Gen8
> > >> > > server.
> > >> >
> > >> > The actual error is:
> > >> >
> > >> > > virt-v2v: error: no root device found in this
operating system
> image.
> > >> >
> > >> > What operating system / distro / version are you trying
to convert?
> > >>
> > >> Looking a bit more closely, virt-v2v seems to have trouble
seeing
> > >> anything at all on the source disk.  So something may have
gone badly
> > >> wrong.  Tell me about what OS you expect the source
(physical) machine
> > >> to have, and also something about what hardware it is using
for its
> > >> disks (SCSI? RAID? etc).
> > >>
> > >> 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
> > >>
> > >
> > >
>
> --
> 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/
>

Sorry, attached herein is the screenshot

On Mon, Nov 2, 2015 at 6:50 PM, Ravi Chaudhary <rc.chaudhary@gmail.com>
wrote:
> Greetings Richard,
>
> Thanks for the pointer. It was helpful. (Note: We have 2 physical
> machines, one is p2v machine & the other is conversion server. Both the
> machines have been updated with  "*yum install qemu libvirt-client
> virt-manager   virt-viewer guestfish libguestfs-tools virt-top*")
>
> We have couple of questions for the exact functioning of virt-p2v:
>
>    1. We are unable to locate the following command for injecting the ssh
>    private key of p2v machine:
>
>    *virt-p2v-make-kickstart p2v.ks --inject-ssh-identity id_rsa*
>
>    *virt-p2v-make-kickstart: unrecognized option
'--inject-ssh-identity'*
>
>    *virt-p2v-make-kickstart: problem parsing the command line arguments*
>    2. *Further we are also unable to find any executable
"virt-p2v" on
>    the p2v machine*
>    3. *We are able to view the virt-p2v in GUI mode, only after booting
>    the hardware using the ISO image, generated on p2v machine (The hardware
>    used for booting is the same physical p2v machine). Is this the right
way?
>    We are observing the following error:*
>
>
> *Would you be able to provide us with exact steps required to implement
> the virt-p2v? *
>
> On Mon, Nov 2, 2015 at 2:18 PM, Richard W.M. Jones
<rjones@redhat.com>
> wrote:
>
>> On Mon, Nov 02, 2015 at 12:06:41AM +0530, Ravi Chaudhary wrote:
>> > Greetings Richard,
>> >
>> > To add to the above information, we are following the understated
steps:
>> >
>> >    1. We have 2 BL460c (Gen8) with Fedora 21 installed. Both the
>> >    machines(BL1 & BL2) have been updated with virt-v2v
packages
>> >    2. On BL1, we execute the following commands:
>> >    1. virt-p2v-make-kickstart fedora
>> >       2. livecd-creator p2v.ks
>> >    3. After creating the "livecd-p2v-2xxxxxx.iso" file,
we launch the
>> >    'virt-manager', from BL1
>>
>> So hang on, you're running virt-p2v in a VM?
>>
>> While we do sometimes run virt-p2v in a VM do operational testing of
>> P2V, this isn't the way to convert a physical machine.  You have to
>> burn the ISO to a CD and boot the physical machine using it.
>>
>> (Alternatives exist: use livecd-iso-to-pxeboot; or possibly your blade
>> hardware will let you use the ISO directly as a virtual CD-ROM)
>>
>> Anyway, running virt-p2v in a VM isn't going to work ...
>>
>> Rich.
>>
>> >    4. Create a new virtual machine using the 'File' option
>> >    5. Click on 'Begin Installation' after step 4
>> >    6. User is shown the 'Conversion Server' GUI login
screen
>> >    7. Enter the credentials & click on 'Test Connection
with Conversion
>> >    Server'
>> >    8. 'Next' button is enabled
>> >    9. Click on 'Create p2v' and after sometime, the
process is exited
>> with
>> >    status "-1"
>> >    10. The earlier attached log file is generated in BL2
(conversion
>> >    server) under /tmp/virt-XXXX directory
>> >
>> > Hope it helps to solve the issue.
>> >
>> >
>> > Regards,
>> >
>> > Ravi Chaudhary
>> >
>> > On Sun, Nov 1, 2015 at 9:23 AM, Tejas Gadaria
<refond.gmrt@gmail.com>
>> wrote:
>> >
>> > > Hi Richard,
>> > >
>> > > Thanks for your replay,
>> > >
>> > > We are using Fedora 21 with SAS drive and RAID 0 config on
both
>> Physical
>> > > and conversion server.
>> > >
>> > >
>> > > Thanks,
>> > > Tejas
>> > >
>> > > On Sat, Oct 31, 2015 at 11:50 PM, Richard W.M. Jones <
>> rjones@redhat.com>
>> > > wrote:
>> > >
>> > >> On Sat, Oct 31, 2015 at 06:11:05PM +0000, Richard W.M.
Jones wrote:
>> > >> >
>> > >> > On Sat, Oct 31, 2015 at 10:14:32PM +0530, Tejas
Gadaria wrote:
>> > >> > > Hi,
>> > >> > >
>> > >> > > We are trying to do P2V conversion with
virt-p2v.
>> > >> > >
>> > >> > > we have conversion server (virt-p2v) and
physical server
>> (virt-p2v)
>> > >> server
>> > >> > > configured as per below documentation.
>> > >> > >
>> > >> > >
>> > >>
>> http://libguestfs.org/virt-p2v.1.html#kernel-command-line-configuration
>> > >> > >
>> > >> > > After "Start Conversion" from GUI
interface, we are conversion
>> fails
>> > >> with
>> > >> > > "/run/lvm/lvmetad.socket: connect failed:
No such file or
>> directory"
>> > >> Error.
>> > >> > >
>> > >> > > Logs are attached for more details. Also FYI,
we are using
>> BL460c Gen8
>> > >> > > server.
>> > >> >
>> > >> > The actual error is:
>> > >> >
>> > >> > > virt-v2v: error: no root device found in this
operating system
>> image.
>> > >> >
>> > >> > What operating system / distro / version are you
trying to convert?
>> > >>
>> > >> Looking a bit more closely, virt-v2v seems to have
trouble seeing
>> > >> anything at all on the source disk.  So something may
have gone badly
>> > >> wrong.  Tell me about what OS you expect the source
(physical)
>> machine
>> > >> to have, and also something about what hardware it is
using for its
>> > >> disks (SCSI? RAID? etc).
>> > >>
>> > >> 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
>> > >>
>> > >
>> > >
>>
>> --
>> 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/
>>
>
>

On Mon, Nov 02, 2015 at 06:50:00PM +0530, Ravi Chaudhary
wrote:
> Greetings Richard,
> 
> Thanks for the pointer. It was helpful. (Note: We have 2 physical machines,
> one is p2v machine & the other is conversion server. Both the machines
have
> been updated with  "*yum install qemu libvirt-client virt-manager
> virt-viewer guestfish libguestfs-tools virt-top*")
> 
> We have couple of questions for the exact functioning of virt-p2v:
> 
>    1. We are unable to locate the following command for injecting the ssh
>    private key of p2v machine:
> 
>    *virt-p2v-make-kickstart p2v.ks --inject-ssh-identity id_rsa*
>    *virt-p2v-make-kickstart: unrecognized option
'--inject-ssh-identity'*
This is a new (and useful) feature, but I'm afraid it's not available
until RHEL 7.3 or Fedora >= 24.
>    2. *Further we are also unable to find any executable
"virt-p2v" on the
>    p2v machine*
You shouldn't run virt-p2v directly.  You have to boot the ISO on the
physical machine.
>    3. *We are able to view the virt-p2v in GUI mode, only after booting the
>    hardware using the ISO image, generated on p2v machine (The hardware
used
>    for booting is the same physical p2v machine). Is this the right way? We
>    are observing the following error:*
I'm not clear what this paragraph means.
> *Would you be able to provide us with exact steps required to implement the
> virt-p2v? *
It's all described here:

http://libguestfs.org/virt-p2v.1.html

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org

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).

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