It seems that the documentation for --in-place mode of v2v wasn't clear enough, so try to explain it better.
Signed-off-by: Roman Kagan <rka...@virtuozzo.com> --- v2v/virt-v2v.pod | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index 14da764..e7b9558 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -348,7 +348,8 @@ format in the metadata. Do not create an output virtual machine in the target hypervisor. Instead, adjust the guest OS in the source VM to run in the input -hypervisor. +hypervisor (which is also the target one in this case) on the virtual +hardware defined in the VM configuration. This mode is meant for integration with other toolsets, which take the responsibility of converting the VM configuration, providing for -- 2.5.0 _______________________________________________ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs
