similar to: Trying to get started with virt-p2v

Save the content of the environment on the conversion server, so it is one additional help when debugging failed conversions. --- p2v/conversion.c | 5 +++++ p2v/virt-p2v.pod | 6 ++++++ 2 files changed, 11 insertions(+) diff --git a/p2v/conversion.c b/p2v/conversion.c index 3c379cb..b8bab34 100644 --- a/p2v/conversion.c +++ b/p2v/conversion.c @@ -1061,6 +1061,11 @@ generate_wrapper_script

I have continued on with my attempts to get p2v working will little success. I have changed my server to Fedora 16 and finally got an XP with a single SATA disk (sda) to work. I think that this means that the current virt-p2v.iso just doesn't work with the packages that are available on Centos 6 at the moment. However, the machines that I currently need to actually migrate all have

Hi, I'm trying to do a physical-to-virtual migration for a Windows 2003 Server to RHEV 3.0 and I'm getting errors in the conversion. I created a Virt-P2V.iso using Fedora 16 (i686) using virt-v2v-0.8.7 and virt-p2v-image-builder-0.8.7 instead of the 0.8.5 version available in the repos. The conversion server is the same server where I created the ISO. I edited the /etc/virt-v2v.conf

Hello, Answers below : Le 13/11/2014 16:06, Richard W.M. Jones a écrit : >>>> This is the last thing it does before unwinding: >>>> >>>> libguestfs: trace: cp "/transferxdTiHj/windows/rhev-apt.exe" "/Program >>>> Files/RedHat/V2V Firstboot" >>>> libguestfs: trace: cp = 0 >>>> >>>> So, maybe

Le 17/11/2014 20:31, Richard W.M. Jones a écrit : > On Mon, Nov 17, 2014 at 07:45:12PM +0100, Nicolas Ecarnot wrote: >> But I would be enthusiastic to install a dedicated P2V server, on >> RH7, with the very last libguestfs, if that helps me to insure our >> future P2V will succeed. >> But according to what I understood so far, I'm not sure one can >> install

Ensure the control connection exits with the same status code as virt-v2v, and return an error from start_conversion if virt-v2v failed. --- p2v/conversion.c | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/p2v/conversion.c b/p2v/conversion.c index 9f5a3ad..4ff7ecc 100644 --- a/p2v/conversion.c +++ b/p2v/conversion.c @@ -100,6 +100,7 @@ start_conversion

virt-v2v is definitely used by the functional tests that run virt-p2v, so check for it, and require it for running those tests. Reported by Rich. --- m4/p2v-tests.m4 | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/m4/p2v-tests.m4 b/m4/p2v-tests.m4 index f679bc4..7de356d 100644 --- a/m4/p2v-tests.m4 +++ b/m4/p2v-tests.m4 @@ -25,11 +25,12 @@ AC_ARG_ENABLE([gnulib-tests],

v1 was here: https://www.redhat.com/archives/libguestfs/2018-June/msg00047.html v1 -> v2: - Add a regular expression in the virt-v2v modules code too. - - - I was planning a much more ambitious second version of this patch (half written too) which had: virt-v2v --describe-modules that listed a big chunk of XML which virt-p2v would parse. These would include the names of the

These are the current steps we followed to set up and run Windows P2V migrations. Note that development is proceeding rapidly and the versions of all pieces below will likely be obsolete soon. ************************************************************* Windows RHEV P2V Cookbook 2011-1122 1. Install 32 bit Fedora 14 as a virtual machine or physical host. You will use this system to build

This is a user case if users build virt-v2v on x86_64 platform and only want to try V2V section then they must see P2V rpm build error, it's not necessary for V2V users. In addition, if some automation scripts call autobuild.sh on x86_64 platform then the programming also will exit due to the buiding error. Signed-off-by: Alex Jia <ajia at redhat.com> --- autobuild.sh | 15

Thanks a lot for your awesome support Richard. "test connection" worked after we configured the necessary IP details but the "Conversion" ends with status as 1 with the below error message: (PFA of the complete logs stored on conversion server under "/tmp/virt-v2v-***" directory) /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to

On 10/11/14 16:01, Richard W.M. Jones wrote: > On Mon, Nov 10, 2014 at 04:12:35PM +0100, Nicolas Ecarnot wrote: >> Hi, >> >> In a oVirt 3.4.4 environnement, and using a >> virt-p2v-0.9.1-2.20130730.1.el6.centos, I'm trying to convert a >> windows 2003 server 32 bits into an oVirt KVM image. >> >> I already succeed doing that many times, but now,

Run sudo with -n (non-interactive), so it will fail right away when not configured to not require a password. This will avoid the connection to time out. --- p2v/ssh.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/p2v/ssh.c b/p2v/ssh.c index b432cbd..c6bf306 100644 --- a/p2v/ssh.c +++ b/p2v/ssh.c @@ -490,7 +490,7 @@ test_connection (struct config *config) */ if

Le 10/11/2014 20:09, Richard W.M. Jones a écrit : >>> Matt - any ideas? >>> >>> There is also the new version of p2v/v2v available, although it >>> requires recent Fedora or RHEL/Centos 7.0. >> >> This is the last thing it does before unwinding: >> >> libguestfs: trace: cp "/transferxdTiHj/windows/rhev-apt.exe" "/Program

Add a minimal release note text for the first standalone version, virt-p2v 1.41.0; in addition, add the first items for the future 1.42.0. --- docs/p2v-release-notes.pod | 32 ++++++++++++++++++++++++++------ 1 file changed, 26 insertions(+), 6 deletions(-) diff --git a/docs/p2v-release-notes.pod b/docs/p2v-release-notes.pod index ee0dd98..21d736d 100644 --- a/docs/p2v-release-notes.pod +++

On Wed, Aug 31, 2011 at 12:56:50PM -0500, Greg Scott wrote: > OK, thanks. I just did a yum install virt-v2v on a Fedora 14 VM - but > the man pages don't have anything about how to do physical machines. I > already have a p2v CD built with virt-p2v-image-builder a while ago. I > boot my source server from that CD - what do I do on the Fedora 14 > conversion VM? How do I

Le 19/11/2014 16:33, Richard W.M. Jones a écrit : > You need to post the complete debug log. It's in /tmp on the > conversion server. Ah nice, I ignored that. Here it is: virt-v2v: libguestfs 1.28.1 (x86_64) [ 0.0] Opening the source -i libvirtxml /tmp/virt-p2v-20141119-z1eg0fua/physical.xml libvirt xml is: <?xml version="1.0"?> <!-- NOTE! This libvirt XML is

On Tue, Jun 12, 2018 at 12:13:32PM +0200, Pino Toscano wrote: > On Tuesday, 12 June 2018 11:27:56 CEST Richard W.M. Jones wrote: > > The new ‘-o rhv-upload’ output mode contains a '-' character in the > > name, but the regular expression which matched the output of the > > virt-v2v command did not recognize '-' as a valid character. It ended > > up

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

The new ‘-o rhv-upload’ output mode contains a '-' character in the name, but the regular expression which matched the output of the virt-v2v command did not recognize '-' as a valid character. It ended up mapping this to just "rhv" meaning two "rhv" entries would appear in the list of output drivers. Thanks: Ming Xie. --- p2v/ssh.c | 4 ++-- 1 file changed,