>From b611133cf6641f3dc1a082ac5019e924a8bd21b5 Mon Sep 17 00:00:00 2001 From: Roman Kagan Date: Fri, 18 Mar 2016 19:15:39 +0300 Subject: [PATCH] v2v: better explain --in-place 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 --- v2v/virt-v2v.pod | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index 14da764..3a4da06 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -354,6 +354,8 @@ This mode is meant for integration with other toolsets, which take the responsibility of converting the VM configuration, providing for rollback in case of errors, transforming the storage, etc. +See L below. + Conflicts with all I<-o *> options. =item B<--machine-readable> @@ -1730,6 +1732,31 @@ that instead. +=head1 IN PLACE CONVERSION + +It is also possible to use virt-v2v in scenarios where a foreign VM +has already been imported into a KVM-based hypervisor, but still needs +adjustments in the guest to make it run in the new virtual hardware. + +In that case it is assumed that a third-party tool has created the +target VM in the supported KVM-based hypervisor based on the source VM +configuration and contents, but using virtual devices more appropriate +for KVM (e.g. virtio storage and network, etc.). + +Then, to make the guest OS boot and run in the changed environment, +one can use: + + virt-v2v -ic qemu:///system converted_vm --in-place + +Virt-v2v will analyze the configuration of C in the +C libvirt instance, and apply various fixups to the +guest OS configuration to make it match the VM configuration. This +may include installing virtio drivers, configuring the bootloader, the +mountpoints, the network interfaces, and so on. + +Should an error occur during the operation, virt-v2v exits with an +error code leaving the VM in an undefined state. + =head1 MACHINE READABLE OUTPUT The I<--machine-readable> option can be used to make the output more -- 2.7.4