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.
DescriptionRichard W.M. Jones
2011-03-08 07:55:44 UTC
+++ This bug was initially created as a clone of Bug #677286 +++
Description of problem:
convert rhel4u8 guest from esx to kvm (libvirt and rhevm) modprobe.conf is incorrect
the network and storage driver are not virtio
Version-Release number of selected component (if applicable):
virt-v2v-0.6.3-5.el5
libguestfs-1.2.7-1.el5.8
libguestfs-*-1.2.7-1.el5.8
libvirt-0.8.2-15.el5_6.1
febootstrap-2.6-1.el5.2
hivex-1.2.2-1.el5.1
augeas-libs-0.7.3-1.el5.1
virtio-win-1.0.1-2.52454.el5
RHEVM ic91
rhevh-5.6-8.1
How reproducible:
always
Steps to Reproduce:
1.# virt-v2v -ic esx://10.66.72.149/?no_verify=1 -op esx -n default ESX4.0-rhel4u8-32b
unknown filesystem /dev/hdc
unknown filesystem /dev/fd0
virt-v2v: No capability in config matches os='linux' name='virtio' distro='redhat-based'
virt-v2v: ESX4.0-rhel4u8-32b configured without virtio drivers
2.check the modprobe.conf
# cat /etc/modprobe.conf
alias eth0 e1000
Actual results:
alias eth0 e1000
Expected results:
alias eth0 virtio
Additional info:
esx3.5 esx4.0 and esx4.1 all can reproduce this bug
/boot/devive.map is not update
if the guest is rhel4u9 ,everything is fine .
--- Additional comment from whuang on 2011-02-14 04:20:44 EST ---
Created attachment 478589[details]
ESX4.1-RHEL4.8-64b.log
--- Additional comment from whuang on 2011-02-14 05:21:01 EST ---
set Priority: low Severity:low
sorry Matt , We install the wrong guest(redhat desktop 4u8 ) ,the "Red Hat Enterprise Linux 4u8" is fine ,but it is also a bug .
--- Additional comment from mbooth on 2011-02-14 06:12:09 EST ---
Note from the error message that the guest OS has been detected as 'redhat-based', which we don't have any config for:
virt-v2v: No capability in config matches os='linux' name='virtio'
distro='redhat-based'
This seems to be an oversight in libguestfs's OS detection. I've moved this to to libguestfs and updated the title.
--- Additional comment from rjones on 2011-03-07 08:01:07 EST ---
Huang, could you please let us know the contents of the file:
/etc/redhat-release
from *inside* the guest?
--- Additional comment from yupzhang on 2011-03-07 22:07:13 EST ---
From guest:
#cat /etc/redhat-release
Red Hat Desktop release 4 (Nahant Update 8)
--- Additional comment from rjones on 2011-03-08 02:54:19 EST ---
I see the problem. Cloning this bug for upstream and 6.2.
Comment 1Richard W.M. Jones
2011-06-10 10:26:02 UTC
This requires a small backport, along with the scheduled
rebase of virt-v2v so it uses the core inspection APIs.
Comment 2Richard W.M. Jones
2011-08-10 12:34:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1512.html