-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-9.7
-
None
-
virt-v2v-2.7.1-16.el9
-
No
-
Moderate
-
rhel-virt-tools
-
ssg_virtualization
-
13
-
None
-
False
-
False
-
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
To get the possible roots for the virt-v2v we need to run the virt-inspector. But we can't run the virt-inspector on the vmware disks directly without using the nbdkit. As an alternative, there is the virt-v2v-inspector, which runs on the VMware diks and does even the guest conversion but does not output the list of roots as the virt-inspector. It only outputs the one operating system and its root, which was converted.
Could we get the list of available roots from the virt-v2v-inspector so the users could choose which root should be converted?
What is the impact of this issue to you?
This is blocking the MTV-2431, where we would want to run the inspection even before starting the migration plan. We would want to try if the VM could be converted and get the information.
- is cloned by
-
RHEL-89993 Add possible roots to the virt-v2v-inspector output [rhel-10.1]
-
- Release Pending
-
- is depended on by
-
MTV-2431 Create a inspection job for the guest information before migration
-
- In Progress
-
-
MTV-2435 Fail warm migration early
-
- In Progress
-
- links to
-
RHBA-2025:147143 virt-v2v bug fix and enhancement update