similar to: virt-v2v F18 guest on F18 failure

Hi! I'm trying to convert some Xen guests running Centos 5.8 to KVM on Centos 6.3. Hopefully this is the right place to ask this question, if not, let me know and I'll go there instead! :) My setup: Centos 5.8 Host running Xen with a Centos 5.8 guest, and I want to transfer this guest to a different Centos 6.3 host running KVM. I am able to tweak the target server all I want, but the

So I am getting this error on Fed18 virt-v2v trying to convert libvirtxml to Rhev 3.1 NFS Export domain: 'iface' parameter is not supported by the libvirt attach-method at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 96. Which is mentioned in this bug: https://bugzilla.redhat.com/show_bug.cgi?id=895898 and this one:

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

From: "Richard W.M. Jones" <rjones at redhat.com> This is the default since libguestfs 1.6. It does not need to be explicitly set. See also https://bugzilla.redhat.com/show_bug.cgi?id=799798#c6 --- lib/Sys/VirtConvert/GuestfsHandle.pm | 3 --- 1 files changed, 0 insertions(+), 3 deletions(-) diff --git a/lib/Sys/VirtConvert/GuestfsHandle.pm

Hello, I've trying to move a 32bit CentOS 6.4 on VirtualBox to oVirt on Fedora 19 64bit via virt-v2v. The command I'm currently using is: virt-v2v -i libvirtxml -of qcow2 -oa sparse -o rhev -osd xxx.xxx.xxx.xxx:/usr/local/ovirt/exports --network ovirtmgmt /usr1/home/williams/Downloads/OpenAthens/VMs/OpenAthensLARuntime2.2.xml The exciting bit of the XML is: <devices>

Mike, This is great. I have a couple of minor comments inline, but this looks good. I do have a major concern, though, which is this is basically a fork of RedHat.pm. There are well over 1,000 identical lines of code between the 2 modules. Many of the differences are relatively minor, and could be handled with additional cases. I've also fixed a couple of bits in RedHat.pm since you forked

In preparation for an upcoming patch which adds support for SUSE guest conversions, it makes sense to have an intermediate steps that changes the RedHat.pm converter into a more generic Linux converter. The SUSE changes will then be limited in scope to only what is required for SUSE support. This series of patches accomplishes the following: - Renames RedHat.pm to Linux.pm - Modifies Linux.pm

The iface:ide parameter (used in the libguestfs add_drive call) does not work with a libvirt backend. The error usually seen is: 'iface' parameter is not supported by the libvirt attach-method at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 96. This issue was previously mentioned in this thread:

I just now ran into some traceback messages and other errors running virt-p2v-image-builder 0.8.5.1. Anything to worry about? . . . Installing: passwd ##################### [305/307] Installing: syslinux ##################### [306/307] Installing: vim-minimal ##################### [307/307] Note: Forwarding request to

On Tue, Nov 22, 2011 at 08:03:15PM +0000, Wandell, Doug wrote: > Image is a prebuilt VMWare image from Layer7. Downloaded and converted under RHEL6 like this: > > virt-convert --arch=x86_64 SSG_64bit_VirtualAppliance_v6.1/ SSG_64bit_VirtualAppliance_v6.1.xml > qemu-img convert -O qcow2 SSG_64bit_VirtualAppliance_v6.1.raw SSG_64bit_VirtualAppliance_v6.1.qcow2 > > No problem. I

inspect_os() shouldn't do this, but ultimately it's heuristic. As we know what the transfer device is, we can double-check the output. --- v2v/virt-v2v.pl | 18 +++++++++++++++++- 1 files changed, 17 insertions(+), 1 deletions(-) diff --git a/v2v/virt-v2v.pl b/v2v/virt-v2v.pl index fe07ae9..6e73102 100755 --- a/v2v/virt-v2v.pl +++ b/v2v/virt-v2v.pl @@ -496,11 +496,18 @@ my $g = new

Trying to test virt-v2v using ESX. Running Fedora 16 and virt-v2v 0.8.5. Command invocation: virt-v2v -ic esx://testhostname/?no_verify=1 -os testpool --network default testvm Result: Invalid configuration of Net::HTTPS at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Transfer/ESX.pm line 68. Couldn't find a resolution to this issue on the net. Please assist.

Matt, On Fri, 2013-11-15 at 14:05 +0000, Matthew Booth wrote: > On Fri, 2013-11-15 at 10:47 +0000, Owen Williams wrote: > > Hello, > > I've trying to move a 32bit CentOS 6.4 on VirtualBox to oVirt on > > Fedora 19 64bit via virt-v2v. The command I'm currently using is: > > > > virt-v2v -i libvirtxml -of qcow2 -oa sparse -o rhev -osd > >

I should have this in my head by now... I tried migrating a physical Windows host last night using virt-p2v CD. It ran for 3 hours and then died. I'll get details later from the log but as I think about it, I'll bet it died because I never installed virtio-win in my Fedora migration server. The documentation says do "yum install virtio-win" - but this is RHEL

This is a new conversion module to convert SUSE Linux and openSUSE guests. The converter is based on the RedHat module, and should offer the same functionality on both SUSE and RedHat hosts. There are a few additional messages in this module, such as reporting of packages when installing through zypper or the local virt-v2v repo. These messages don't necessarily flow unless verbose switches

Hi, I am experiencing a failure running virt-v2v to convert a Linux guest on an ESX host to a RedHat KVM hypervisor. The output with the failure follows. Any help/guidance is appreciated. [root at storage-024 ~]# virt-v2v -ic esx://<ip address>/?no_verify=1 -op transferimages --bridge br0 dev-03 > /tmp/virt-v2v.output error from Term::ReadKey::GetTerminalSize(): Unable to get

This change is part of an ongoing effort to remove use of $desc and inspect the OS directly as required during conversion. --- lib/Sys/VirtConvert/Connection/LibVirtTarget.pm | 4 +- lib/Sys/VirtConvert/Connection/RHEVTarget.pm | 41 +++++++++--------- lib/Sys/VirtConvert/Converter.pm | 35 ++++++++++++---- lib/Sys/VirtConvert/Converter/RedHat.pm | 45

Just a note [possibly more of a warning] that I'm intending to switch the default backend in Fedora 18+ to libvirt this week. For more information about what this means, see: https://rwmj.wordpress.com/2012/07/23/new-in-libguestfs-use-libvirt-to-launch-the-appliance/#content Barring any bugs, the change ought to be transparent. The reasons why we're making this change in Fedora are:

On Friday, October 04, 2013 09:38:58 AM Matthew Booth wrote: > It's specifically an error if we're attempting to configure virtio, and > there's no detected virtio kernel. It shouldn't have been possible to > get here in that state, hence it's a programmer error. The code below > attempts to install *any* kernel in the case that we aren't configuring >

On Tuesday, October 08, 2013 10:05:17 AM Matthew Booth wrote: > Feel free to remove ^$path. However, for robustness I ditch the leading > ^ from your replacement. The difference will be down to a different > version of file included in the libguestfs appliance on SUSE. I think I've addressed all the concerns you raised in the following patch. Can you take a look and let me know if