similar to: P2V conversion failed with "/run/lvm/lvmetad.socket: connect failed: No such file or directory"

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

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

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

On Sun, Nov 01, 2015 at 09:23:28AM +0530, Tejas Gadaria 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. We're going to need a bit more information about the hardware in the physical server, like what 'RAID 0' means - hardware RAID? What precise RAID controller

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.

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 >

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 at 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:

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

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

Minor Correction, Yes, we are using Hardware RAID-0, which uses HP Smart Array P220i Controller. Thanks, Tejas On Mon, Nov 2, 2015 at 3:48 AM, SHREE DUTH Awasthi < shreeduth.awasthi@gmail.com> wrote: > Hello Richard, > > Thanks a lot for your time and response. Please find the requested details > attached. > > RAID-0 is the software raid level which we have configured

Hello Richard, Thanks a lot for your time and response. Please find the requested details attached. RAID-0 is the software raid level which we have configured on the HP BL Gen8 server. (While creating 1 Logical drive out of 2 physical drives ) Best, Shree. On Sun, Nov 1, 2015 at 12:49 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Sun, Nov 01, 2015 at 09:23:28AM +0530, Tejas

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:

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

Hi Richard, We have generated .iso on Physical server and tried booting same with "livecd-p2v-*.iso", and we are getting "unexpected end of file waiting for password prompt" error. Also we are not able to execute "/sbin/ifconfig" or "ip a" binaries on Physical server after booting from livecd. We have attached "p2v.ks" file and

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

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

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

When the daemon starts up it creates a fresh (empty) LVM configuration and starts up lvmetad (which depends on the LVM configuration). However this appears to cause problems: Some types of PV seem to require lvmetad and don't work without it (https://bugzilla.redhat.com/show_bug.cgi?id=1581810). If we don't start lvmetad earlier, the device nodes are not created. Therefore move the

Hi, I'm trying to resize a 15GB LVM root partition on a fedora20 server with a fedora20 guest and I'm having a problem. Is this supported on fedora20? I recall having a similar problem (maybe even exact same problem) all the way back in fedora16 or fedora17, but hoped/thought it would be fixed by now? # virt-df -h test1-011015.img Filesystem Size Used

Currently lvmetad is started in init, and thus using the system (= appliance) configuration of lvm. Later on, in the daemon, a local copy of the lvm configuration is setup, and set it for use using the LVM_SYSTEM_DIR environment variable: this means only the programmes executed by the daemon will use the local lvm configuration, and not lvmetad. Thus manually start lvmetad from the daemon, right