Re: [Libguestfs] [V2V PATCH v3 0/6] Bring support for virtio-scsi back to Windows

Discussion on v2: https://listman.redhat.com/archives/libguestfs/2023-March/030987.html v2 -> v3: * Patch 2/6 ("convert_windows: add Inject_virtio_win.Virtio_SCSI as a possible block type"): omit "Inject_virtio_win." prefix in favor of type inference. Add a short commit message body; * Add tests/test-v2v-block-driver.sh testing the new "--block-driver" option. Discussion on v1: https://listman.redhat.com/archives/libguestfs/2023-February/030849.html https://listman.redhat.com/archives/libguestfs/2023-March/030917.html v1 -> v2: * Adapt the patch suggested by Richard, splitting it up into 3: https://listman.redhat.com/archives/libguestfs/2023-March/030975.html Now we have "--block-driver" command line option which regulates the order in which block drivers are being searched for (and, as a consequence, the default driver). Andrey Drobyshev (3): Revert "Remove guestcaps_block_type Virtio_SCSI" convert_windows: add Inject_virtio_win.Virtio_SCSI as a possible block type tests: add --block-driver option test Richard W.M. Jones (3): convert: introduce "block_driver" convert option convert_windows: set block driver priority according to block_driver option v2v, in-place: introduce --block-driver command line option convert/convert.ml | 11 ++- convert/convert.mli | 1 + convert/convert_linux.ml | 11 ++- convert/convert_linux.mli | 3 +- convert/convert_windows.ml | 11 ++- convert/convert_windows.mli | 3 +- convert/target_bus_assignment.ml | 1 + docs/virt-v2v-in-place.pod | 10 ++ docs/virt-v2v.pod | 10 ++ in-place/in_place.ml | 12 ++- inspector/inspector.ml | 3 +- lib/create_ovf.ml | 1 + lib/types.ml | 3 +- lib/types.mli | 2 +- output/openstack_image_properties.ml | 7 ++ tests/Makefile.am | 2 + tests/test-v2v-block-driver.sh | 143 +++++++++++++++++++++++++++ v2v/v2v.ml | 12 ++- 18 files changed, 231 insertions(+), 15 deletions(-) create mode 100755 tests/test-v2v-block-driver.sh