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] (default
> task-317) [27b3ad4b] Lock freed to object
> 'EngineLock:{exclusiveLocks='[wvm2=<VM_NAME,
> 7d40eaee-2f3f-4a4e-8254-4c2c3312ce5c=<VM,
> sharedLocks='[7d40eaee-2f3f-4a4e-8254-4c2c3312ce5c=<REMOTE_VM,
> 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:


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.


Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
Users mailing list

Reply via email to