-
Bug
-
Resolution: Done-Errata
-
Major
-
rhel-9.5
-
None
-
virt-v2v-2.5.6-7.el9_5
-
No
-
Moderate
-
ZStream
-
rhel-sst-virtualization
-
ssg_virtualization
-
26
-
31
-
3
-
False
-
-
None
-
None
-
Approved Blocker
-
-
Pass
-
Automated
-
None
Description
virt-v2v can migrate VMs from vSphere to CNV, however, many disks that are being touched will not be brought online after migration, because the bus changed.
In MTV-1299 a small powershell script is getting injected in order to bring online all disks which are attachde to a virtio bus.
The request is to take this into virt-v2v
Acceptance Criteria
A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.
- Verify a vmware VM with additional 6 disks with drive letters F, G, N, O, T, Y, after virt-v2v processed, boot on KVM, all disks with correct drive letters are still visible
- Verify Y
- Verify Z
Note:
There were quite a few bugs about this in the past:
RHELPLAN-27074
RHELPLAN-79363
What SSTs and Layered Product teams should review this?
virt
- is duplicated by
-
RHEL-55271 virt-v2v / Windows to take disks online after they got moved to virtio
- Closed
- is related to
-
RHEL-56318 Re-enable Windows disks post-live migration [rhel-10 beta]
- In Progress
- links to
-
RHBA-2024:129426 virt-v2v bug fix and enhancement update