Thanks Richard for a fast reply.

Yes, indeed, im working on a nested environment. I try to run v2v inside a VM (L1) and to create an L2 by the conversion process. And on Intel. As I wrote, it fails once in few times, mainly when there is a memory pressure on L0.

Kashyap, can you please share your experience? Why should it crash during nested conversion. I'm not too familiar with libguestfs logic - maybe you can point for me, according to the logs, at what stage of the conversion the failure happens.

Thanks,

Rom

On Thu, Jan 16, 2014 at 5:23 PM, Richard W.M. Jones <rjones@redhat.com> wrote:

On Wed, Jan 15, 2014 at 04:35:29PM +0200, Rom Freiman wrote:
> Hi everybody,
>
> Wanted to hear your opinion and to receive a smart advice.
>
> I'm trying to use virt-v2v in order to convert ova image (exported from
> vcenter) to run on libvirt/kvm - all this inside a VM of fedora.
> The converted image is also a fedora.
> During the conversion process, in some point of libguestfs activity, I get
> double fault panic from L2 (printed as part of libguest output) and the
> conversion process fails - no errors appear neither in L0 not in L1 message
> logs.

Are you using nested KVM?

Kashyap (CC'd) has done a lot of testing on nested KVM on *Intel*,
never with satisfactory results. It just doesn't work very well.

On AMD is a different story -- nested KVM just works.

Rich.

--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW