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"

(the message above is copied verbatim from the log, including the misspellings) One of the VMs is a RHEL 6.6 and the other is Windows 7. The import reports adding a disk and then running a conversion, then appears to fail about 5 or 6 minutes into converting the image. I'm considering using virt-v2v to do the conversion of the .ova, but I'm not sure how to get that into ovirt then. Any suggestions?

Regards, Cam

_______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

> 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 get in > vdsm > log)., another options you can do is run virt-v2v in verbose mode (virt-v2v > -v). > 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 local' stick it on the node's VM storage?

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

I'm using 'virt-v2v -v -i ova wvm2.ovf -o rhev -os ovirt-engine:/mnt/export-vm' (my export domain), though unfortunately it fails Error is: [root@kvm-ldn-01 tmp]# virt-v2v -v -x -i ova wvm2.ovf -o rhev -os ovirt-engine:/mnt/export-vm virt-v2v: libguestfs 1.28.1 (x86_64) [ 0.0] Opening the source -i ova wvm2.ovf tar -xzf 'wvm2.ovf' -C '/var/tmp/ova.dEFSqi' virt-v2v: error: could not parse ovf:Name from OVF document

BTW: is there a way of specifying the extraction directory? My first attempt filled up /var/tmp until I found another host that luckily had a big enough partition.

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] (default task-317) [27b3ad4b] Lock freed to object 'EngineLock:{exclusiveLocks='[wvm2=<VM_NAME, ACTION_TYPE_FAILED_NAME_ALREADY_USED>, 7d40eaee-2f3f-4a4e-8254-4c2c3312ce5c=<VM, ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName wvm2>]', sharedLocks='[7d40eaee-2f3f-4a4e-8254-4c2c3312ce5c=<REMOTE_VM, ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName wvm2>]'}' So I guess it is doing the import still.

> > 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 virt-v2v you can do the > whole conversion/import over again, this time adding the `-on > new_name' option to the command line (obviously choosing a name which > is not otherwise being used). > > I don't know if there's a way to get oVirt to change the name when > importing from the export domain. As far as I know you have to start > the import from scratch. > > There's no existing VM with that name that I can see. It may have come from one of my earlier import attempts, though that earlier attempt did not show up in the GUI, it did write files to the export domain. I re-ran the conversion again with a rename but it failed to import it again, with the same error. Could there be a record in the DB somewhere, or does it look at the files alone? Just trying to work out where the conflict is.

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-rhev > > > > > > However that error shouldn't happen. It looks like the name is the > > > same as the name of an existing VM. From virt-v2v you can do the > > > whole conversion/import over again, this time adding the `-on > > > new_name' option to the command line (obviously choosing a name which > > > is not otherwise being used). > > > > > > I don't know if there's a way to get oVirt to change the name when > > > importing from the export domain. As far as I know you have to start > > > the import from scratch. > > > > > > > > There's no existing VM with that name that I can see. It may have come from > > one of my earlier import attempts, > > though that earlier attempt did not show up in the GUI, it did write files > > to the export domain. > > > > I re-ran the conversion again with a rename but it failed to import it > > again, with the same error. > > > > Could there be a record in the DB somewhere, or does it look at the files > > alone? Just trying to work out where the conflict is. > > I had a look at the ovirt-engine code where > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come > from a database check. However I'm not really familiar enough with > the code to be sure. Probably best to ask an oVirt developer, or try > dumping the database to see if "wvm2" appears in a column anywhere. > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > Fedora Windows cross-compiler. Compile Windows programs, test, and > build Windows installers. Over 100 libraries supported. > http://fedoraproject.org/wiki/MinGW It may be in the DB... Try to run this via psql: select vm_name from vm_static where vm_name='wvm2'; and see if there is a result...

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 <shavivi(a)redhat.com&gt; wrote: > > > 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-rhev > > > > > > > > > > However that error shouldn't happen. It looks like the name is the > > > > > same as the name of an existing VM. From virt-v2v you can do the > > > > > whole conversion/import over again, this time adding the `-on > > > > > new_name' option to the command line (obviously choosing a name which > > > > > is not otherwise being used). > > > > > > > > > > I don't know if there's a way to get oVirt to change the name when > > > > > importing from the export domain. As far as I know you have to start > > > > > the import from scratch. > > > > > > > > > > > > > > There's no existing VM with that name that I can see. It may have come > > from > > > > one of my earlier import attempts, > > > > though that earlier attempt did not show up in the GUI, it did write > > files > > > > to the export domain. > > > > > > > > I re-ran the conversion again with a rename but it failed to import it > > > > again, with the same error. > > > > > > > > Could there be a record in the DB somewhere, or does it look at the > > files > > > > alone? Just trying to work out where the conflict is. > > > > > > I had a look at the ovirt-engine code where > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come > > > from a database check. However I'm not really familiar enough with > > > the code to be sure. Probably best to ask an oVirt developer, or try > > > dumping the database to see if "wvm2" appears in a column anywhere. > > > > > > Rich. > > > > > > -- > > > Richard Jones, Virtualization Group, Red Hat > > http://people.redhat.com/~rjones > > > Read my programming and virtualization blog: http://rwmj.wordpress.com > > > Fedora Windows cross-compiler. Compile Windows programs, test, and > > > build Windows installers. Over 100 libraries supported. > > > http://fedoraproject.org/wiki/MinGW > > It may be in the DB... > > Try to run this via psql: > > > > select vm_name from vm_static where vm_name='wvm2'; > > > > and see if there is a result... > >

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 disk it will be great.

Shahar. On 21.07.16 10:16, Cam Mac wrote: > Sent, thanks Shahar. > > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi <shavivi(a)redhat.com&gt; 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 > > > --------- > > > (0 rows) > > > > > > Thanks, > > > > > > Cam > > > > > > > > > > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi <shavivi(a)redhat.com&gt; > > wrote: > > > > > > > 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-rhev > > > > > > > > > > > > > > However that error shouldn't happen. It looks like the name is > > the > > > > > > > same as the name of an existing VM. From virt-v2v you can do the > > > > > > > whole conversion/import over again, this time adding the `-on > > > > > > > new_name' option to the command line (obviously choosing a name > > which > > > > > > > is not otherwise being used). > > > > > > > > > > > > > > I don't know if there's a way to get oVirt to change the name > > when > > > > > > > importing from the export domain. As far as I know you have to > > start > > > > > > > the import from scratch. > > > > > > > > > > > > > > > > > > > > There's no existing VM with that name that I can see. It may have > > come > > > > from > > > > > > one of my earlier import attempts, > > > > > > though that earlier attempt did not show up in the GUI, it did > > write > > > > files > > > > > > to the export domain. > > > > > > > > > > > > I re-ran the conversion again with a rename but it failed to > > import it > > > > > > again, with the same error. > > > > > > > > > > > > Could there be a record in the DB somewhere, or does it look at the > > > > files > > > > > > alone? Just trying to work out where the conflict is. > > > > > > > > > > I had a look at the ovirt-engine code where > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come > > > > > from a database check. However I'm not really familiar enough with > > > > > the code to be sure. Probably best to ask an oVirt developer, or try > > > > > dumping the database to see if "wvm2" appears in a column anywhere. > > > > > > > > > > Rich. > > > > > > > > > > -- > > > > > Richard Jones, Virtualization Group, Red Hat > > > > http://people.redhat.com/~rjones > > > > > Read my programming and virtualization blog: > > http://rwmj.wordpress.com > > > > > Fedora Windows cross-compiler. Compile Windows programs, test, and > > > > > build Windows installers. Over 100 libraries supported. > > > > > http://fedoraproject.org/wiki/MinGW > > > > It may be in the DB... > > > > Try to run this via psql: > > > > > > > > select vm_name from vm_static where vm_name='wvm2'; > > > > > > > > and see if there is a result... > > > > > >

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 <shavivi(a)redhat.com&gt; wrote: > 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 domain >> 3. etc... >> >> If you can attach the ova without the disk it will be great. > And please attach the engine.log as well. >> >> Shahar. >> >> On 21.07.16 10:16, Cam Mac wrote: >> > Sent, thanks Shahar. >> > >> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi <shavivi(a)redhat.com&gt; 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 >> > > > --------- >> > > > (0 rows) >> > > > >> > > > Thanks, >> > > > >> > > > Cam >> > > > >> > > > >> > > > >> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi <shavivi(a)redhat.com&gt; >> > > wrote: >> > > > >> > > > > 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-rhev >> > > > > > > > >> > > > > > > > However that error shouldn't happen. It looks like the name is >> > > the >> > > > > > > > same as the name of an existing VM. From virt-v2v you can do the >> > > > > > > > whole conversion/import over again, this time adding the `-on >> > > > > > > > new_name' option to the command line (obviously choosing a name >> > > which >> > > > > > > > is not otherwise being used). >> > > > > > > > >> > > > > > > > I don't know if there's a way to get oVirt to change the name >> > > when >> > > > > > > > importing from the export domain. As far as I know you have to >> > > start >> > > > > > > > the import from scratch. >> > > > > > > > >> > > > > > > > >> > > > > > > There's no existing VM with that name that I can see. It may have >> > > come >> > > > > from >> > > > > > > one of my earlier import attempts, >> > > > > > > though that earlier attempt did not show up in the GUI, it did >> > > write >> > > > > files >> > > > > > > to the export domain. >> > > > > > > >> > > > > > > I re-ran the conversion again with a rename but it failed to >> > > import it >> > > > > > > again, with the same error. >> > > > > > > >> > > > > > > Could there be a record in the DB somewhere, or does it look at the >> > > > > files >> > > > > > > alone? Just trying to work out where the conflict is. >> > > > > > >> > > > > > I had a look at the ovirt-engine code where >> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come >> > > > > > from a database check. However I'm not really familiar enough with >> > > > > > the code to be sure. Probably best to ask an oVirt developer, or try >> > > > > > dumping the database to see if "wvm2" appears in a column anywhere. >> > > > > > >> > > > > > Rich. >> > > > > > >> > > > > > -- >> > > > > > Richard Jones, Virtualization Group, Red Hat >> > > > > http://people.redhat.com/~rjones >> > > > > > Read my programming and virtualization blog: >> > > http://rwmj.wordpress.com >> > > > > > Fedora Windows cross-compiler. Compile Windows programs, test, and >> > > > > > build Windows installers. Over 100 libraries supported. >> > > > > > http://fedoraproject.org/wiki/MinGW >> > > > > It may be in the DB... >> > > > > Try to run this via psql: >> > > > > >> > > > > select vm_name from vm_static where vm_name='wvm2'; >> > > > > >> > > > > and see if there is a result... >> > > > > >> > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users -- Campbell McLeay · Senior Systems Administrator London · New York · Los Angeles · Montréal T +44 (0)20 7344 8000 19-23 Wells Street, London W1T 3PQ Twitter · Facebook · framestore.com

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 <shavivi(a)redhat.com&gt; wrote: > 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 export domain, there may be something wrong between the > virt-v2v output ovf and the oVirt engine. > You can try the new feature to import ova strait on oVirt admin portal (if > you > already try that the forget it), go to the vms tab -> import and select > "vmware ova" from the select box... > > > > > Cheers, > > > > Cam > > > > On 21 July 2016 at 12:59, Shahar Havivi <shavivi(a)redhat.com&gt; wrote: > > > 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 domain > > >> 3. etc... > > >> > > >> If you can attach the ova without the disk it will be great. > > > And please attach the engine.log as well. > > >> > > >> Shahar. > > >> > > >> On 21.07.16 10:16, Cam Mac wrote: > > >> > Sent, thanks Shahar. > > >> > > > >> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi <shavivi(a)redhat.com&gt; > 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 > > >> > > > --------- > > >> > > > (0 rows) > > >> > > > > > >> > > > Thanks, > > >> > > > > > >> > > > Cam > > >> > > > > > >> > > > > > >> > > > > > >> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi < > shavivi(a)redhat.com&gt; > > >> > > wrote: > > >> > > > > > >> > > > > 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-rhev > > >> > > > > > > > > > >> > > > > > > > However that error shouldn't happen. It looks like the > name is > > >> > > the > > >> > > > > > > > same as the name of an existing VM. From virt-v2v you > can do the > > >> > > > > > > > whole conversion/import over again, this time adding > the `-on > > >> > > > > > > > new_name' option to the command line (obviously > choosing a name > > >> > > which > > >> > > > > > > > is not otherwise being used). > > >> > > > > > > > > > >> > > > > > > > I don't know if there's a way to get oVirt to change > the name > > >> > > when > > >> > > > > > > > importing from the export domain. As far as I know you > have to > > >> > > start > > >> > > > > > > > the import from scratch. > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > There's no existing VM with that name that I can see. It > may have > > >> > > come > > >> > > > > from > > >> > > > > > > one of my earlier import attempts, > > >> > > > > > > though that earlier attempt did not show up in the GUI, > it did > > >> > > write > > >> > > > > files > > >> > > > > > > to the export domain. > > >> > > > > > > > > >> > > > > > > I re-ran the conversion again with a rename but it failed > to > > >> > > import it > > >> > > > > > > again, with the same error. > > >> > > > > > > > > >> > > > > > > Could there be a record in the DB somewhere, or does it > look at the > > >> > > > > files > > >> > > > > > > alone? Just trying to work out where the conflict is. > > >> > > > > > > > >> > > > > > I had a look at the ovirt-engine code where > > >> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it > appears to come > > >> > > > > > from a database check. However I'm not really familiar > enough with > > >> > > > > > the code to be sure. Probably best to ask an oVirt > developer, or try > > >> > > > > > dumping the database to see if "wvm2" appears in a column > anywhere. > > >> > > > > > > > >> > > > > > Rich. > > >> > > > > > > > >> > > > > > -- > > >> > > > > > Richard Jones, Virtualization Group, Red Hat > > >> > > > > http://people.redhat.com/~rjones > > >> > > > > > Read my programming and virtualization blog: > > >> > > http://rwmj.wordpress.com > > >> > > > > > Fedora Windows cross-compiler. Compile Windows programs, > test, and > > >> > > > > > build Windows installers. Over 100 libraries supported. > > >> > > > > > http://fedoraproject.org/wiki/MinGW > > >> > > > > It may be in the DB... > > >> > > > > Try to run this via psql: > > >> > > > > > > >> > > > > select vm_name from vm_static where vm_name='wvm2'; > > >> > > > > > > >> > > > > and see if there is a result... > > >> > > > > > > >> > > > > > _______________________________________________ > > > Users mailing list > > > Users(a)ovirt.org > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > -- > > Campbell McLeay · Senior Systems Administrator > > > > London · New York · Los Angeles · Montréal > > T +44 (0)20 7344 8000 > > 19-23 Wells Street, London W1T 3PQ > > Twitter · Facebook · framestore.com >

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 <shavivi(a)redhat.com&gt; 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 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 can edit) > > > > Thanks, > > > > Cam > > > > On Thu, Jul 21, 2016 at 2:17 PM, Shahar Havivi <shavivi(a)redhat.com&gt; > wrote: > > > > > 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 export domain, there may be something wrong between > the > > > virt-v2v output ovf and the oVirt engine. > > > You can try the new feature to import ova strait on oVirt admin portal > (if > > > you > > > already try that the forget it), go to the vms tab -> import and select > > > "vmware ova" from the select box... > > > > > > > > > > > Cheers, > > > > > > > > Cam > > > > > > > > On 21 July 2016 at 12:59, Shahar Havivi <shavivi(a)redhat.com&gt; wrote: > > > > > 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 > domain > > > > >> 3. etc... > > > > >> > > > > >> If you can attach the ova without the disk it will be great. > > > > > And please attach the engine.log as well. > > > > >> > > > > >> Shahar. > > > > >> > > > > >> On 21.07.16 10:16, Cam Mac wrote: > > > > >> > Sent, thanks Shahar. > > > > >> > > > > > >> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi < > shavivi(a)redhat.com&gt; > > > 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 > > > > >> > > > --------- > > > > >> > > > (0 rows) > > > > >> > > > > > > > >> > > > Thanks, > > > > >> > > > > > > > >> > > > Cam > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > > >> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi < > > > shavivi(a)redhat.com&gt; > > > > >> > > wrote: > > > > >> > > > > > > > >> > > > > 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-rhev > > > > >> > > > > > > > > > > > >> > > > > > > > However that error shouldn't happen. It looks like > the > > > name is > > > > >> > > the > > > > >> > > > > > > > same as the name of an existing VM. From virt-v2v > you > > > can do the > > > > >> > > > > > > > whole conversion/import over again, this time adding > > > the `-on > > > > >> > > > > > > > new_name' option to the command line (obviously > > > choosing a name > > > > >> > > which > > > > >> > > > > > > > is not otherwise being used). > > > > >> > > > > > > > > > > > >> > > > > > > > I don't know if there's a way to get oVirt to change > > > the name > > > > >> > > when > > > > >> > > > > > > > importing from the export domain. As far as I know > you > > > have to > > > > >> > > start > > > > >> > > > > > > > the import from scratch. > > > > >> > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > There's no existing VM with that name that I can see. > It > > > may have > > > > >> > > come > > > > >> > > > > from > > > > >> > > > > > > one of my earlier import attempts, > > > > >> > > > > > > though that earlier attempt did not show up in the > GUI, > > > it did > > > > >> > > write > > > > >> > > > > files > > > > >> > > > > > > to the export domain. > > > > >> > > > > > > > > > > >> > > > > > > I re-ran the conversion again with a rename but it > failed > > > to > > > > >> > > import it > > > > >> > > > > > > again, with the same error. > > > > >> > > > > > > > > > > >> > > > > > > Could there be a record in the DB somewhere, or does > it > > > look at the > > > > >> > > > > files > > > > >> > > > > > > alone? Just trying to work out where the conflict is. > > > > >> > > > > > > > > > >> > > > > > I had a look at the ovirt-engine code where > > > > >> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it > > > appears to come > > > > >> > > > > > from a database check. However I'm not really familiar > > > enough with > > > > >> > > > > > the code to be sure. Probably best to ask an oVirt > > > developer, or try > > > > >> > > > > > dumping the database to see if "wvm2" appears in a > column > > > anywhere. > > > > >> > > > > > > > > > >> > > > > > Rich. > > > > >> > > > > > > > > > >> > > > > > -- > > > > >> > > > > > Richard Jones, Virtualization Group, Red Hat > > > > >> > > > > http://people.redhat.com/~rjones > > > > >> > > > > > Read my programming and virtualization blog: > > > > >> > > http://rwmj.wordpress.com > > > > >> > > > > > Fedora Windows cross-compiler. Compile Windows programs, > > > test, and > > > > >> > > > > > build Windows installers. Over 100 libraries supported. > > > > >> > > > > > http://fedoraproject.org/wiki/MinGW > > > > >> > > > > It may be in the DB... > > > > >> > > > > Try to run this via psql: > > > > >> > > > > > > > > >> > > > > select vm_name from vm_static where vm_name='wvm2'; > > > > >> > > > > > > > > >> > > > > and see if there is a result... > > > > >> > > > > > > > > >> > > > > > > > _______________________________________________ > > > > > Users mailing list > > > > > Users(a)ovirt.org > > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > > > > > > > -- > > > > Campbell McLeay · Senior Systems Administrator > > > > > > > > London · New York · Los Angeles · Montréal > > > > T +44 (0)20 7344 8000 > > > > 19-23 Wells Street, London W1T 3PQ > > > > Twitter · Facebook · framestore.com > > > >

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://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top