On Wed, May 19, 2021 at 01:40:04PM -0400, Alan Daniels wrote:
> Directly importing from VMware would be desirable to not have a 2-step process.
> I'll look into updating.
> And just to confirm - it still has to go through vCenter right? (Can't go
> directly to the ESXi host).
It can import directly from ESXi, although you'll have to use the VDDK
method which involves using some software from VMware with a non-libre
license. This is all detailed in the manual:
> I tried the OVA method where I exported the VM using VMware's ovftool directly
> to the new KVM host. However, importing this local OVA (with the oVirt GUI
> rather than virt-v2v on the command line) still failed.
> virt-v2v: error: inspection could not detect the source guest (or physical
Thanks for attaching the log. It shows that virt-v2v found a single
disk with two partitions, but it couldn't make sense of what was on
the disk. In particular it seems as if the second partition doesn't
have C:\windows\system32\cmd.exe ? If this was missing it would be
enough to confuse virt-v2v into thinking there is no system partition.
If you didn't delete the file then it might be some obscure Windows
version we've not seen before, or some problem with ntfs-3g.
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.