On Mon, Sep 11, 2017 at 04:27:30PM +0000, Seth Tanner wrote: > Rich, > Here you go > I also noticed that if I use the direct backend rather than libvirt, the > conversion gets farther, but still does not complete, when pulling directly > from vSphere. please let me know if you would like the output of direct as > well. > starting version 233 > + udevadm trigger > + udevadm settle --timeout=600 > [ 3.124522] EDAC MC: Ver: 3.0.0 > [ 3.135246] EDAC sbridge: Ver: 1.1.1
Ugh, looks like this is actually a qemu or kernel bug. Is it reproducible when you just do: libguestfs-test-tool ? Is there anything peculiar about the environment, eg. nested virt, running inside VMware, peculiar hardware? You could also try running without using KVM. It'll be a bit slower but is usually less buggy than nested virt: export LIBGUESTFS_BACKEND_SETTINGS=force_tcg Rich. -- 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. http://libguestfs.org/virt-v2v _______________________________________________ Libguestfs mailing list [email protected] https://www.redhat.com/mailman/listinfo/libguestfs
