-
Bug
-
Resolution: Won't Do
-
Undefined
-
None
-
rhel-9.7
-
None
-
No
-
Low
-
rhel-virt-tools
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
Description of problem:
Improve info about guest must not be running or must be shut down in virt-v2v related man pages
Version-Release number of selected component (if applicable):
virt-v2v-2.7.1-12.el9.x86_64
How reproducible:
100%
Steps:
1. The v2v conversion won't fail when converting a running guest since bug RHEL-88543 was fixed for virt-v2v-inspector
# virt-v2v Auto-esx7.0-rhel7.5-multi-disks -on Auto-esx7.0-rhel7.5-multi-disks-running [ 0.0] Setting up the source: -i libvirt Auto-esx7.0-rhel7.5-multi-disks virt-v2v: warning: libvirt domain ‘Auto-esx7.0-rhel7.5-multi-disks’ is running or paused. Converting a live guest will result in corrupted output. However this is safe if you're converting from a snapshot [ 4.3] Opening the source [ 12.4] Inspecting the source [ 23.4] Checking for sufficient free disk space in the guest [ 23.4] Converting Red Hat Enterprise Linux Server 7.5 (Maipo) (rhel7.5) to run on KVM virt-v2v: This guest has virtio drivers installed. [ 107.7] Setting a random seed [ 107.7] SELinux relabelling [ 142.3] Mapping filesystem data to avoid copying unused and blank areas [ 145.5] Closing the overlay [ 145.9] Assigning disks to buses [ 145.9] Checking if the guest needs BIOS or UEFI to boot [ 145.9] Setting up the destination: -o libvirt [ 150.1] Copying disk 1/4 █ 100% [****************************************] [ 150.9] Copying disk 2/4 █ 100% [****************************************] [ 166.5] Copying disk 3/4 █ 100% [****************************************] [ 177.9] Copying disk 4/4 █ 100% [****************************************] [ 211.8] Creating output metadata [ 211.8] Finishing off
2. So the info about 'guest must not be running' 'guest shutdown' should be improved in v2v related man page
#man virt-v2v .... The guest must not be running. Virt-v2v would not need to be run as root in this case. ..... # man virt-v2v-input-vmware |grep shut VMX: Guest must be shut down The guest must be shut down before conversion starts. If you don't shut it down, you will end up with a corrupted - Fedora 20 shut off - Windows 2003 shut off - Fedora 20 shut off - Windows 2003 shut off where "Windows 2003" is the name of the guest (which must be shut down). # man virt-v2v-input-xen |grep shut - rhel49-x86_64-pv shut off where "rhel49-x86_64-pv" is the name of the guest (which must be shut down).
Actual result:
As above description
Expect result:
Fix the bug
Additional info
- is cloned by
-
RHEL-99745 Improve info about guest must not be running or must be shut down in virt-v2v related man page [rhel-10.1]
-
- Release Pending
-