On 02/25/2015 10:57 AM, Marko Dimjašević wrote:
> Hi all,
>
> On Wed, 2015-02-25 at 08:54 -0500, Cole Robinson wrote:
>
>> New virt-convert does not convert to virt-image, since virt-image has been
>> removed. It converts straight to libvirt XML
>
> Thx Cole for this! Does that version of virt-c
Hi all,
On Wed, 2015-02-25 at 08:54 -0500, Cole Robinson wrote:
> New virt-convert does not convert to virt-image, since virt-image has been
> removed. It converts straight to libvirt XML
Thx Cole for this! Does that version of virt-convert need a minimum
libvirt version that is above 1.2.9?
-
On 02/24/2015 11:57 PM, Marko Dimjašević wrote:
> On Sun, 2015-02-22 at 10:33 -0500, Cole Robinson wrote:
>
>> 0.600.1 is very old, and virt-convert has changed a lot since then. I'd
>> recommend trying the latest version from virt-manager-1.1.0, and if you still
>> hit issues, file an upstream bu
On Sun, 2015-02-22 at 10:33 -0500, Cole Robinson wrote:
> 0.600.1 is very old, and virt-convert has changed a lot since then. I'd
> recommend trying the latest version from virt-manager-1.1.0, and if you still
> hit issues, file an upstream bug:
I did just that, i.e. I used virt-convert 0.600.4 f
On 02/22/2015 01:58 AM, Marko Dimjašević wrote:
> Hi all,
>
> I've been having a problem when trying to convert an Open Virtualization
> Appliance (OVA) format appliance to the "virt-image" format. This is how
> I try to convert the appliance:
>
> $ virt-convert --arch=i686 -i ovf appliance.ova
