Show Table of Contents
Chapter 6. Debugging and troubleshooting
6.1. Debugging V2V conversions
Problems encountered when attempting a V2V conversion can be more easily explained to engineers or support services if debugging messages are enabled when V2V is run.
Exporting the debugging messages increases the verbosity of the V2V process, causing
virt-v2v to print out messages as it runs. These messages will be displayed in the terminal from which virt-v2v is run.
Simple redirection can be used to print
virt-v2v debug messages to a file. The conversion runs normally like this:
virt-v2v -i libvirtxml -os pool --bridge bridge_name guest_name.xml
Instead, edit this command to export the debug messages to the
virt-v2v.log file. To do this, prefix the above command with the environment variables LIBGUESTFS_TRACE=1 LIBGUESTFS_DEBUG=1, and redirect the output to the virt-v2v.log file by adding ... 2>&1 | tee virt-v2v.log to the end of the command.
LIBGUESTFS_TRACE=1 LIBGUESTFS_DEBUG=1 virt-v2v -i libvirtxml -os pool --bridge bridge_name guest_name.xml ... 2>&1 | tee virt-v2v.log
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.