<div dir="ltr"><div>Hi Shahar,</div><div><br></div><div>Doesn't appear to be there:</div><div><br></div><div>engine=> select vm_name from vm_static where vm_name='wvm2';</div><div> vm_name </div><div>---------</div><div>(0 rows)</div><div><br></div><div>Thanks,</div><div><br></div><div>Cam</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi <span dir="ltr"><<a href="mailto:shavivi@redhat.com" target="_blank">shavivi@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 20.07.16 20:06, Richard W.M. Jones wrote:<br>
> On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:<br>
> > ><br>
> > > The import doesn't happen automatically, you have to do the final step<br>
> > > manually (when using the command line). See:<br>
> > ><br>
> > > <a href="http://libguestfs.org/virt-v2v.1.html#output-to-rhev" rel="noreferrer" target="_blank">http://libguestfs.org/virt-v2v.1.html#output-to-rhev</a><br>
> > ><br>
> > > However that error shouldn't happen. It looks like the name is the<br>
> > > same as the name of an existing VM. From virt-v2v you can do the<br>
> > > whole conversion/import over again, this time adding the `-on<br>
> > > new_name' option to the command line (obviously choosing a name which<br>
> > > is not otherwise being used).<br>
> > ><br>
> > > I don't know if there's a way to get oVirt to change the name when<br>
> > > importing from the export domain. As far as I know you have to start<br>
> > > the import from scratch.<br>
> > ><br>
> > ><br>
> > There's no existing VM with that name that I can see. It may have come from<br>
> > one of my earlier import attempts,<br>
> > though that earlier attempt did not show up in the GUI, it did write files<br>
> > to the export domain.<br>
> ><br>
> > I re-ran the conversion again with a rename but it failed to import it<br>
> > again, with the same error.<br>
> ><br>
> > Could there be a record in the DB somewhere, or does it look at the files<br>
> > alone? Just trying to work out where the conflict is.<br>
><br>
> I had a look at the ovirt-engine code where<br>
> ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come<br>
> from a database check. However I'm not really familiar enough with<br>
> the code to be sure. Probably best to ask an oVirt developer, or try<br>
> dumping the database to see if "wvm2" appears in a column anywhere.<br>
><br>
> Rich.<br>
><br>
> --<br>
> Richard Jones, Virtualization Group, Red Hat <a href="http://people.redhat.com/~rjones" rel="noreferrer" target="_blank">http://people.redhat.com/~rjones</a><br>
> Read my programming and virtualization blog: <a href="http://rwmj.wordpress.com" rel="noreferrer" target="_blank">http://rwmj.wordpress.com</a><br>
> Fedora Windows cross-compiler. Compile Windows programs, test, and<br>
> build Windows installers. Over 100 libraries supported.<br>
> <a href="http://fedoraproject.org/wiki/MinGW" rel="noreferrer" target="_blank">http://fedoraproject.org/wiki/MinGW</a><br>
</div></div>It may be in the DB...<br>
Try to run this via psql:<br>
<br>
select vm_name from vm_static where vm_name='wvm2';<br>
<br>
and see if there is a result...<br>
</blockquote></div><br></div>