Loading...
Loading...
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.
Done-Errata
Red Hat Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.