OS validation before copy starts

[OmkarDeshpande7]

What steps did you take and what happened?

There is a limited list of operating systems supported by virt-v2v-in-place. Right now if we try to migrate a VM with unsupported OS, we see virt-v2v command failing, but this is after the copy completes, we should fail early. We should add a validation for the VM OS before we start the migration.

Supported OS:

Red Hat Enterprise Linux 4, 5, 6, 7, 8, 9, 10
CentOS 4, 5, 6, 7, 8, 9, 10
Scientific Linux 4, 5, 6, 7
Oracle Linux
Fedora
SLES 10 and up
OpenSUSE 10 and up
ALT Linux 9 and up
Debian 6 and up
Ubuntu 10.04, 12.04, 14.04, 16.04, and up
Windows XP to Windows 11 / Windows Server 2025

What did you expect to happen?

Get an early failure for unsupported OS.

Environment

v0.1.4

vCenter version

any

Anything else you would like to add?

No response

[huly-for-github]

Connected to Huly®: VJAIL-212