(In reply to Claudio Fontana from comment #6) > (In reply to Rodney Baker from comment #5) > > Surely this can be dealt with through documentation and/or a warning: "You > > must have the relevant filesystem tools installed for the filesystems used > > by the guest VM you are about to convert", or words to that effect. > > No, It would be almost impossible for users to track down the nest of > runtime requirements. > > If you don't want virt-v2v, do not install it. > > If you want a functional virt-v2v, you need all required runtime > dependencies, or the conversions _will_ fail. Then be consistent and add "requires" for e2fsprogs, ntfsprogs and xfsprogs as well. After all, as you said, "If you want a functional virt-v2v, you need all required runtime dependencies, or the conversions _will_ fail."