similar to: A problem with converting an OVA appliance

Displaying 20 results from an estimated 6000 matches similar to: "A problem with converting an OVA appliance"

2015 Feb 25
2
Re: A problem with converting an OVA appliance
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 from virt-manager-1.1.0 (while I left the installed libvirt packages at 1.2.9) and the
2015 Feb 25
1
Re: A problem with converting an OVA appliance
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? -- Regards, Marko http://dimjasevic.net/marko
2015 Feb 22
0
Re: A problem with converting an OVA appliance
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 > > The result is: > > ERROR Couldn't import
2015 Feb 25
0
Re: A problem with converting an OVA appliance
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 bug: > > I did just that, i.e. I used virt-convert 0.600.4 from >
2015 Oct 21
2
"could not parse ovf:Name" converting OVA
I got the "IE10 on Win 8" VM download from here: https://dev.modern.ie/tools/vms/linux/ and am trying to convert the .ova file to a format that will work with virt-manager and KVM on Fedora 21. I tried this: $ virt-v2v -v -x -i ova -o libvirt IE10\ -\ Win8.ova and got this output: virt-v2v: libguestfs 1.28.12 (x86_64) [ 0.0] Opening the source -i ova IE10 - Win8.ova tar -xf
2015 Oct 22
1
Re: "could not parse ovf:Name" converting OVA
On Thu, Oct 22, 2015 at 08:47:36AM +0100, Richard W.M. Jones wrote: > On Wed, Oct 21, 2015 at 03:19:15PM -0700, Don Marti wrote: > > I got the "IE10 on Win 8" VM download from here: > > https://dev.modern.ie/tools/vms/linux/ > > > > and am trying to convert the .ova file to a format that > > will work with virt-manager and KVM on Fedora 21. > >
2017 Feb 14
1
Re: [PATCH 1/1] v2v: ova: fix generated JSON for libvirt support
On Tue, Feb 14, 2017 at 01:26:40AM +0100, Tomáš Golembiovský wrote: > We have to be explicit about the drivers in backing file JSON in order > for libvirt to work. > > Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> > --- > v2v/input_ova.ml | 1 + > v2v/test-v2v-i-ova-subfolders.expected2 | 2 +- > v2v/test-v2v-i-ova-tar.expected2
2016 Oct 07
3
[PATCH v5 0/2] Improve OVA manifest parsing
This series fixes and enhances parsing of the OVA manifest file. The changes are: - Added mandatory space to the regexp - Process all lines in the file, not just one - Warn on improperly formated lines - Support SHA256 hashes v4 -> v5: - fix tests - change one test to include the SHA256 checksum Tomáš Golembiovský (2): v2v: ova: fix checking of the manifest file v2v: ova: support SHA256
2017 Feb 23
4
[PATCH v2 0/3] Fix OVA import with libvirt backend
v2: - 1/3: same as in previous version - 2/3: add check for libvirt version - 3/3: restore the disabled test The libvirt patch [2] that should fix our problem with 'raw' driver that is mentioned in [1] was merged. To realy fix things, there is at least one thing we have to change on our side. We have to be explicit about the driver in the JSON we generate. [1]
2017 Feb 14
2
[PATCH 0/1] Fix OVA import with libvirt backend
I've sent a patch to libvirt that should fix our problem with 'raw' driver that is mentioned in [1]. The libvirt patch is here [2]. However, to realy fix things, there is at least one thing we have to change on our side. We have to be explicit about the driver in the JSON we generate. Note that the libvirt patch has not yet been reviewed nor merged, so this may not be the only thing
2016 Nov 30
4
Re: [PATCH v2 5/5] v2v: update tests to match changes in OVA import
On Wednesday, 23 November 2016 16:40:59 CET Tomáš Golembiovský wrote: > On Mon, 21 Nov 2016 16:41:49 +0100 > Pino Toscano <ptoscano@redhat.com> wrote: > > > On Saturday, 12 November 2016 16:37:53 CET Tomáš Golembiovský wrote: > > > The virt-v2v behaviour for OVA input now depends on QEMU version > > > available. The tests affected by this now have two
2018 May 09
1
[PATCH] v2v: update results of test-v2v-i-ova-snapshots for non-json
When using non-JSON disk notation, the disk will be the snapshot #2. Fixes commit e5946165c8ea78e0e91c4cfdb5e793526cd638e1. --- v2v/test-v2v-i-ova-snapshots.expected | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v2v/test-v2v-i-ova-snapshots.expected b/v2v/test-v2v-i-ova-snapshots.expected index 97bce58ad..a64843b35 100644 --- a/v2v/test-v2v-i-ova-snapshots.expected +++
2016 May 19
2
[PATCH] v2v: handle subfolders in ova files
Some ova files have their ovf and other files inside a folder rather than at the root of the tarball. Consider the paths relative to the ovf file to cover this case too. --- v2v/Makefile.am | 1 + v2v/input_ova.ml | 3 +- v2v/test-v2v-i-ova-subfolders.sh | 88 ++++++++++++++++++++++++++++++++++++++++ 3 files changed, 91 insertions(+), 1 deletion(-) create mode
2016 Nov 21
2
Re: [PATCH v2 5/5] v2v: update tests to match changes in OVA import
On Saturday, 12 November 2016 16:37:53 CET Tomáš Golembiovský wrote: > The virt-v2v behaviour for OVA input now depends on QEMU version > available. The tests affected by this now have two *.expect files and > the expected result now also depends on the QEMU used. > > Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> > --- This IMHO should be part of patch #4 as
2017 Jan 11
3
[PATCH v5 0/3] Import directly from OVA tar archive if possible
v5: - rebase, patches 1,3,5 were merged - 1/3: we still need to discuss whether to detect compressed discs - 2/3: - renamed argument noempty to keep_empty - tests were not run - 3/3: - using JSON module to generate JSON (as suggested by Pino) - all the other comments raised by Pino v4: - rebase to more recent master - 1/6: using just "quote" instead of
2017 Jan 31
1
Re: [PATCH v6 3/3] v2v: ova: don't extract files from OVA if it's not needed
On Mon, Jan 30, 2017 at 10:43:16PM +0100, Tomáš Golembiovský wrote: > + QV=$(expr match "$(qemu-img --version)" 'qemu-img version \([0-9]\+\.[0-9]\+\)') Maybe consider using bash's internal regexp functions? We already use them in many other places, try doing: $ git grep '=~' -- \*.sh > diff --git a/v2v/input_ova.ml b/v2v/input_ova.ml > index
2016 Nov 16
2
Re: [ovirt-users] OVA import of FC21 VM hangs during virt-v2v conversion?
"Richard W.M. Jones" <rjones@redhat.com> writes: > On Wed, Nov 16, 2016 at 09:06:29AM +0200, Michal Skrivanek wrote: >> >> > On 7 Nov 2016, at 22:16, Derek Atkins <derek@ihtfp.com> wrote: >> > >> > Hi, >> > >> > My last VM imported in 2 minutes. This one has been sitting for three >> > hours. I think this is
2017 Mar 13
7
[PATCH 0/4] v2v: -i -ova: Various fixes.
This has to be applied on top of this series: https://www.redhat.com/archives/libguestfs/2017-March/msg00144.html This is a fix for: https://bugzilla.redhat.com/show_bug.cgi?id=1430680 Kun Wei noticed that virt-v2v -i ova has a problem if we are running as root and the OVA is not located on a path which is fully readable by non-root. The reason for this is that libvirt runs qemu as a
2016 Nov 04
10
[PATCH 0/5] Import directly from OVA tar archive if possible
This is still a draft, not ready for commit yet. But feedback is welcomed. This series is related to the problem of inefficient import of OVA files. The needed enhancements of QEMU was merged into the codebase and should be available in QEMU 2.8. From there we can use 'size' and 'offset' options in raw driver to tell QEMU to use only subset of a file as an image. The first three
2018 Mar 23
2
[PATCH] v2v: ova: convert E1000 network interfaces as such
So far v2v did not read the model of network interfaces, resulting in "virtio" as the model for such interfaces. Start reading the model, if available, mapping only E1000 for now. There are also other models, e.g. PCNet32 or VmxNet3, but they are ignored for now: reading them as Source_other_nic would result in v2v rejecting OVAs previously converted. --- v2v/parse_ovf_from_ova.ml