Product SiteDocumentation Site

Chapter 4. Debugging and Troubleshooting

4.1. Debugging V2V conversions

4.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.
  1. Before running a V2V conversion, enter the following in the terminal:
    export LIBGUESTFS_TRACE=1
    export LIBGUESTFS_DEBUG=1
  2. The above exports increase 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.
  3. Simple redirection can be used to print virt-v2v debug messages to a file. Instead of running the conversion normally like this:
    virt-v2v -i libvirtxml -os pool --bridge brname vm-name.xml
    virt-v2v can be run like this:
    LIBGUESTFS_TRACE=1 LIBGUESTFS_DEBUG=1 virt-v2v -i libvirtxml -os pool --bridge brname vm-name.xml ... 2>&1 | tee virt-v2v.log