-
Bug
-
Resolution: Won't Do
-
Undefined
-
None
-
rhel-10.1
-
None
-
No
-
None
-
rhel-virt-tools
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
Description of problem:
Virt-v2v can't convert a guest with two same volume groups
Version-Release number of selected component (if applicable):
virt-v2v-2.7.1-16.el9.x86_64
libguestfs-1.54.0-11.el9.x86_64
guestfs-tools-1.52.2-6.el9.x86_64
nbdkit-1.38.5-12.el9.x86_64
libnbd-1.20.3-4.el9.x86_64
selinux-policy-38.1.64-1.el9.noarch
How reproducible:
100%
Steps:
1. Prepare a rhel guest with two same volume groups on VMware
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 16G 0 disk
├─sda1 8:1 0 600M 0 part /boot/efi
├─sda2 8:2 0 1G 0 part /boot
└─sda3 8:3 0 14.4G 0 part
├─rhel-root 253:0 0 12.8G 0 lvm /
└─rhel-swap 253:1 0 1.6G 0 lvm [SWAP]
sdb 8:16 0 4G 0 disk
sr0 11:0 1 12.8G 0 rom /run/media/root/RHEL-8-10-0-BaseOS-x86_64
# cat /etc/fstab
.....
/dev/mapper/rhel-root / xfs defaults 0 0
UUID=c2bcf7f6-a2c5-4b47-ac69-debb5d307719 /boot xfs defaults 0 0
UUID=86F5-945A /boot/efi vfat umask=0077,shortname=winnt 0 2
/dev/mapper/rhel-swap none swap defaults 0 0
# lvm pvs
WARNING: VG name rhel is used by VGs ojDWyk-TFd8-QaIT-jle3-RpSz-K79r-HTyxIl and YEXtAu-Nb9v-FkgN-MG8u-k3pN-Ricd-0cS2TC.
Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
PV VG Fmt Attr PSize PFree
/dev/sda3 rhel lvm2 a-- 14.41g 0
/dev/sdb rhel lvm2 a-- <4.00g <3.00g
# lvm vgs
WARNING: VG name rhel is used by VGs ojDWyk-TFd8-QaIT-jle3-RpSz-K79r-HTyxIl and YEXtAu-Nb9v-FkgN-MG8u-k3pN-Ricd-0cS2TC.
Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
VG #PV #LV #SN Attr VSize VFree
rhel 1 1 0 wz--n- <4.00g <3.00g
rhel 1 2 0 wz--n- 14.41g 0
# lvm lvs
WARNING: VG name rhel is used by VGs ojDWyk-TFd8-QaIT-jle3-RpSz-K79r-HTyxIl and YEXtAu-Nb9v-FkgN-MG8u-k3pN-Ricd-0cS2TC.
Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
new-lv rhel -wi------- 1.00g
root rhel -wi-ao---- <12.81g
swap rhel -wi-ao---- 1.60g
2. Convert the guest from VMware by virt-v2v
# virt-v2v -ic vpx://non-admin%40vsphere.local@10.73.213.134/data/cluster/10.73.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk9.0.0 -io vddk-thumbprint=C3:83:1D:C0:6D:4C:47:83:5A:B9:6E:0E:FA:5A:15:22:B4:75:D5:7E -ip /home/passwd esx8.0-rhel8.10-efi-with-two-same-vgs [ 0.1] Setting up the source: -i libvirt -ic vpx://non-admin%40vsphere.local@10.73.213.134/data/cluster/10.73.212.36/?no_verify=1 -it vddk esx8.0-rhel8.10-efi-with-two-same-vgs [ 3.1] Opening the source [ 46.9] Inspecting the source virt-v2v: error: inspection could not detect the source guest (or physical machine) operating system. Assuming that you are running virt-v2v/virt-p2v on a source which is supported (and not, for example, a blank disk), then this should not happen. No root device found in this operating system image. If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...]
Actual result:
As above description
Expect result:
Fix the bug
Additional info
- clones
-
RHEL-115243 Virt-v2v can't convert a guest with two same volume groups [rhel-10.1]
-
- Closed
-