Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1064625[details]
The log file of on both iSCSI and SATA device
Description of problem:
Device.map didn't updated correctly when converting rhel6.7-i386 host on SATA/iSCSI device to KVM server by virt-p2v
Version-Release number of selected component (if applicable):
virt-v2v-1.28.1-1.49.el7.x86_64
virt-p2v-1.28.1-1.49.el7-1.iso
How reproducible:
100%
Steps to Reproduce:
1. Install rhel6.7-i386 on SATA storage
2. Boot into rhel6.7-i386 and check disk info original of OS host as below:
# cat /boot/grub/device.map
# this device map was generated by anaconda
(hd0) /dev/sda
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 253:0 0 149.1G 0 disk
└─sda1 253:1 0 141.6G 0 part /
└─sda2 253:2 0 7.5G 0 part [SWAP]
3. Boot the source machine into virt-p2v and input the ip and password of conversion server.
4. Convert rhel6.7-i386 SATA host to KVM server via virt-p2v client.
5. After conversion, boot into rhel6.7-i386 guest and examine checkpoints on KVM server.
6. Check disk info of rhel6.7-i386 guest on KVM server as below
#cat /boot/grub/device.map
# this device map was generated by anaconda
(hd0) /dev/sda
#lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 253:0 0 149.1G 0 disk
└─vda1 253:1 0 141.6G 0 part /
└─vda2 253:2 0 7.5G 0 part [SWAP]
Actual results:
Device.map of rhel6.7-i386 guest did not updated to vda.
Expected results:
Device.map of rhel6.7-i386 guest should be updated to vda.
Additional info:
Similar situation happens in iSCSI storage, steps are the same as described above.
Attatched is the log file of both SATA and iSCSI conversion.
Comment 2Richard W.M. Jones
2015-08-19 15:13:27 UTC
There's something wrong with the SATA conversion log file.
It appears to be truncated, and it may be the log from a different
run of the program:
rhel6.7-32-SATA.zip -> virt-v2v-conversion-log.txt ends with:
virt-v2v: error: internal error: invalid argument: cannot find libvirt pool
'/var/tmp': Storage pool not found: no storage pool with matching name
'/var/tmp'
and is clearly not the log from a full conversion.
To debug this issue I really need to see the full conversion log file.
Comment 3Richard W.M. Jones
2015-08-19 15:15:41 UTC
The iSCSI log shows the same problem as bug 1253223, so I'm going
to ignore that.
Comment 5Richard W.M. Jones
2015-08-20 16:21:44 UTC
According to the log, device.map in the original guest had:
(hd0) /dev/sdb
This contradicts the bug description, which says that the mapping
had /dev/sda. Can you go back and check the bug description is correct
and also that the log file corresponds to the conversion.
(In reply to Richard W.M. Jones from comment #5)
> According to the log, device.map in the original guest had:
>
> (hd0) /dev/sdb
>
> This contradicts the bug description, which says that the mapping
> had /dev/sda. Can you go back and check the bug description is correct
> and also that the log file corresponds to the conversion.
I think wufan hit bug 1253223.
So wufan,would you pls check the orignial mapping in iscsi host?
I think it's better to attach full log from conversion of SATA host.
The log was correct and the description was not. Previously, I installed my host using USB device. After conversion, the device.map didn't update correctly. The issue, as Tingting said, hits Bug 1253223.
Then I tried again, after reinstall the guest with DVD and make sure the device map of original host had:'(hd0) /dev/sda', the conversion was a success.
From my perspective, the problem occurs in this bug duplicate with Bug 1253223.
Comment 8Richard W.M. Jones
2015-08-24 08:39:14 UTC
Created attachment 1064625 [details] The log file of on both iSCSI and SATA device Description of problem: Device.map didn't updated correctly when converting rhel6.7-i386 host on SATA/iSCSI device to KVM server by virt-p2v Version-Release number of selected component (if applicable): virt-v2v-1.28.1-1.49.el7.x86_64 virt-p2v-1.28.1-1.49.el7-1.iso How reproducible: 100% Steps to Reproduce: 1. Install rhel6.7-i386 on SATA storage 2. Boot into rhel6.7-i386 and check disk info original of OS host as below: # cat /boot/grub/device.map # this device map was generated by anaconda (hd0) /dev/sda # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 253:0 0 149.1G 0 disk └─sda1 253:1 0 141.6G 0 part / └─sda2 253:2 0 7.5G 0 part [SWAP] 3. Boot the source machine into virt-p2v and input the ip and password of conversion server. 4. Convert rhel6.7-i386 SATA host to KVM server via virt-p2v client. 5. After conversion, boot into rhel6.7-i386 guest and examine checkpoints on KVM server. 6. Check disk info of rhel6.7-i386 guest on KVM server as below #cat /boot/grub/device.map # this device map was generated by anaconda (hd0) /dev/sda #lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 253:0 0 149.1G 0 disk └─vda1 253:1 0 141.6G 0 part / └─vda2 253:2 0 7.5G 0 part [SWAP] Actual results: Device.map of rhel6.7-i386 guest did not updated to vda. Expected results: Device.map of rhel6.7-i386 guest should be updated to vda. Additional info: Similar situation happens in iSCSI storage, steps are the same as described above. Attatched is the log file of both SATA and iSCSI conversion.