On 21.07.16 16:24, Cam Mac wrote:
> Bug ID 1358828. I can do another for the direct import of the OVF (without
Thanks,
Please attach the ovf and ova (no need for the disk inside the ova) to the
bug.
> virt-v2v) if needed.
>
> Cheers,
>
> Cam
>
> On Thu, Jul 21, 2016 at 2:56 PM, Shahar Havivi wr
Bug ID 1358828. I can do another for the direct import of the OVF (without
virt-v2v) if needed.
Cheers,
Cam
On Thu, Jul 21, 2016 at 2:56 PM, Shahar Havivi wrote:
> On 21.07.16 14:38, Cam Mac wrote:
> > I tried that already, and it fails. I gave it another try with the GUI on
> > the new VM I c
On 21.07.16 14:38, Cam Mac wrote:
> I tried that already, and it fails. I gave it another try with the GUI on
> the new VM I created, as you described, and it fails.
> I can attach the engine log if you like.
no need,
please file a bug and attach the ova (without the disks - its a tar file that
you
I tried that already, and it fails. I gave it another try with the GUI on
the new VM I created, as you described, and it fails.
I can attach the engine log if you like.
Thanks,
Cam
On Thu, Jul 21, 2016 at 2:17 PM, Shahar Havivi wrote:
> On 21.07.16 14:01, Campbell McLeay wrote:
> > Thanks Shah
On 21.07.16 14:01, Campbell McLeay wrote:
> Thanks Shahar. Will do. I created a new VM on VMWare for the purposes
> of testing the import again with a new hostname, and it failed with
> the same error.
What you are trying to do is as far as I understand is to use virt-v2v utility
to put the ova in
Thanks Shahar. Will do. I created a new VM on VMWare for the purposes
of testing the import again with a new hostname, and it failed with
the same error.
Cheers,
Cam
On 21 July 2016 at 12:59, Shahar Havivi wrote:
> On 21.07.16 14:58, Shahar Havivi wrote:
>> The error looks like you have a probl
On 21.07.16 14:58, Shahar Havivi wrote:
> The error looks like you have a problem in the storage pool which is null by
> the log.
>
> Please open a bug and specify the exact steps that you took,
> ie.
> 1. $ virt-v2v -o rhev ...
> 2. goto the admin portal and try to view the VMs in the export doma
The error looks like you have a problem in the storage pool which is null by
the log.
Please open a bug and specify the exact steps that you took,
ie.
1. $ virt-v2v -o rhev ...
2. goto the admin portal and try to view the VMs in the export domain
3. etc...
If you can attach the ova without the di
Sent, thanks Shahar.
On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi wrote:
> On 21.07.16 10:03, Cam Mac wrote:
> OK,
> Can you please share the engine.log
> > Hi Shahar,
> >
> > Doesn't appear to be there:
> >
> > engine=> select vm_name from vm_static where vm_name='wvm2';
> > vm_name
> > ---
On 21.07.16 10:03, Cam Mac wrote:
OK,
Can you please share the engine.log
> Hi Shahar,
>
> Doesn't appear to be there:
>
> engine=> select vm_name from vm_static where vm_name='wvm2';
> vm_name
> -
> (0 rows)
>
> Thanks,
>
> Cam
>
>
>
> On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi
Hi Shahar,
Doesn't appear to be there:
engine=> select vm_name from vm_static where vm_name='wvm2';
vm_name
-
(0 rows)
Thanks,
Cam
On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi wrote:
> On 20.07.16 20:06, Richard W.M. Jones wrote:
> > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam
On 20.07.16 20:06, Richard W.M. Jones wrote:
> On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > >
> > > The import doesn't happen automatically, you have to do the final step
> > > manually (when using the command line). See:
> > >
> > > http://libguestfs.org/virt-v2v.1.html#output-to-
On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> >
> > The import doesn't happen automatically, you have to do the final step
> > manually (when using the command line). See:
> >
> > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> >
> > However that error shouldn't happen. It loo
>
> The import doesn't happen automatically, you have to do the final step
> manually (when using the command line). See:
>
> http://libguestfs.org/virt-v2v.1.html#output-to-rhev
>
> However that error shouldn't happen. It looks like the name is the
> same as the name of an existing VM. From vir
On Wed, Jul 20, 2016 at 06:37:38PM +0100, Cam Mac wrote:
> It did show up in the list of importable VMs
> under the 'Import VM' tab under
> the export domain. I tried importing it from there but it gave me:
>
> 2016-07-20 18:27:24,518 INFO
> [org.ovirt.engine.core.bll.exportimport.ImportVmCommand
Hi Richard,
Sorry for missing that TMPDIR, I was looking rather than actually reading.
I used the original ova I'd exported from VMWare, and that worked fine
(after fixing perms). The command I ran was:
virt-v2v -x -v -i ova /mnt/import-vm/wvm2.ova -o rhev -os
ovirt-engine:/mnt/export-vm -of qco
On Wed, Jul 20, 2016 at 03:40:16PM +0100, Cam Mac wrote:
> Hi Rich,
>
>
> > > >
> > >
> > > I can try this but I'm not quite sure how to go about it. The ovf I
> > created
> > > via guest-image-ovf-creator is on an NFS mount
Originally you were trying to import OVAs from VMware, which is the
onl
I tried the GUI first (in 3.6 and later 4.0 after upgrading) and it fails.
I posted to the list about this here:
http://lists.ovirt.org/pipermail/users/2016-June/040442.html
No solution was found so far.
Thanks,
Cam
On Tue, Jul 19, 2016 at 8:51 PM, Richard W.M. Jones
wrote:
> And I suppose
Hi Rich,
> > >
> >
> > I can try this but I'm not quite sure how to go about it. The ovf I
> created
> > via guest-image-ovf-creator is on an NFS mount
> > on the engine: do I need to run virt-v2v on one of the nodes? If so, I
> > assume I need to set the output to an export domain.
> > Does '-o
On 19.07.16 20:51, Richard W.M. Jones wrote:
> And I suppose it's worth saying that recent oVirt can import from
> VMware using the oVirt GUI (which works via virt-v2v, but automates
> everything for you).
>
> Rich.
Richard is right,
you can try to use the import from VMWare to oVirt directly via
And I suppose it's worth saying that recent oVirt can import from
VMware using the oVirt GUI (which works via virt-v2v, but automates
everything for you).
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rw
On Tue, Jul 19, 2016 at 07:02:24PM +0100, Cam Mac wrote:
> > Try to run virt-v2v -i ova -o local to import the ova to local disk (see
> > the
> > virt-v2v man page for more options) and see if that pass - the errors can
> > be
> > more detailed there (it suppose to reflect the same error that you g
Hi Shahar,
> I'm trying to import some .ova images from VMWare that have been copied to
> > a node. In both cases they fail with the error:
> >
> > "Conversion of VM from exteral enironment failed: copy-disk stream closed
> > unexpectedly"
> First you need to look at vdsm log to see more details
On 14.07.16 18:14, Cam Mac wrote:
> Hi,
>
> I'm trying to import some .ova images from VMWare that have been copied to
> a node. In both cases they fail with the error:
>
> "Conversion of VM from exteral enironment failed: copy-disk stream closed
> unexpectedly"
First you need to look at vdsm log
24 matches
Mail list logo