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.
Description of problem:
RHEL3 is in ELS(Extended Lifecycle Support) from October 31, 2010 to January 30, 2014",
so we still need to support RHEL3.9 now.
For RHEL3 guest,virt-v2v handle the block driver as IDE and netowrk driver be e1000
after conversion.The output messages when converting rhel3 guest is not so friendly.
Version-Release number of selected component (if applicable):
virt-v2v-0.8.6-1.el6.x86_64
libvirt-0.9.10-2.el6.x86_64
libguestfs-1.16.5-1.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1.Use virt-v2v to convert a rhel3 guest
# virt-v2v -ic qemu+ssh://10.66.72.122/system -os default -b breth0 kvm-rhel3.9-i386
root.72.122's password:
root.72.122's password:
RHEL-3.9-32.raw: 100% [===========================================================================================]D 0h02m04s
virt-v2v: No capability in config matches os='linux' name='virtio' distro='rhel' major='3' minor='9'
virt-v2v: No capability in config matches os='linux' name='cirrus' distro='rhel' major='3' minor='9'
virt-v2v: WARNING: Display driver was updated to cirrus, but unable to install cirrus driver. X may not function correctly
virt-v2v: WARNING: /boot/grub/device.map references unknown device /dev/fd0. This entry must be manually fixed after conversion.
virt-v2v: kvm-rhel3.9-i386 configured without virtio drivers.
Actual results:
virt-v2v prints messages not so friendly:
virt-v2v: No capability in config matches os='linux' name='virtio' distro='rhel' major='3' minor='9'
virt-v2v: No capability in config matches os='linux' name='cirrus' distro='rhel' major='3' minor='9'
Expected results:
1.virt-v2v should print some messages more friendly.
2.We should document the special handle of virt-v2v for rhel3 guest.
Additional info:
Comment 2RHEL Program Management
2012-12-14 06:50:37 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3Richard W.M. Jones
2014-11-18 11:26:55 UTC