Red Hat Bugzilla – Bug 682979
libguestfs incorrectly detects Red Hat desktop as 'redhat-based' instead of 'redhat'
Last modified: 2011-03-08 11:21:51 EST
+++ 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):
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
alias eth0 e1000
alias eth0 virtio
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 firstname.lastname@example.org on 2011-02-14 04:20:44 EST ---
Created attachment 478589 [details]
--- Additional comment from email@example.com 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 firstname.lastname@example.org 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'
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 email@example.com on 2011-03-07 08:01:07 EST ---
Huang, could you please let us know the contents of the file:
from *inside* the guest?
--- Additional comment from firstname.lastname@example.org on 2011-03-07 22:07:13 EST ---
Red Hat Desktop release 4 (Nahant Update 8)
--- Additional comment from email@example.com on 2011-03-08 02:54:19 EST ---
I see the problem. Cloning this bug for upstream and 6.2.
Patch posted upstream: