Red Hat Bugzilla – Bug 586788
Virt-v2v should first detect whether kudzu exists in the guest
Last modified: 2013-07-02 21:39:16 EDT
Description of problem:
Virt-v2v should first detect whether kudzu exists in the guest. If exists, then disable kudzu.
e.g in rhel6, there is no pacakge of kudzu installed
Version-Release number of selected component (if applicable):
Steps to Reproduce:
#virt-v2v -f /usr/share/doc/virt-v2v-0.5.1/virt-v2v.conf -i libvirtxml -o rhev -osd nfs.host:/export_domain /tmp/xen-rhel6-32b-hv.raw.xml
command: error reading information on service kudzu: No such file or directory at /usr/lib/perl5/vendor_perl/5.8.8/Sys/VirtV2V/GuestOS/RedHat.pm line 1313.
virt-v2v: Failed to unmount 10.66.90.115:/vol/v2vwulinglu/wulingluv2v/export. Command exited with status 1. Output was: umount: /tmp/fdfem4j95g: device is busy
umount: /tmp/fdfem4j95g: device is busy
virt-v2v: Failed to remove mount directory /tmp/fdfem4j95g: Device or resource busy
/usr/lib/perl5/vendor_perl/5.8.8/Sys/VirtV2V/GuestOS/RedHat.pm line 1313.
# Disable kudzu in the guest
# Kudzu will detect the changed network hardware at boot time and either:
# require manual intervention, or
# disable the network interface
# Neither of these behaviours is desirable.
$g->command(['/sbin/chkconfig', 'kudzu', 'off']);
There will be loads of issues like this with RHEL 6 guests. RHEL 6 also doesn't use mkinitrd, and it configures consoles differently that I can think of. I'm putting this one under the general 'RHEL 6 support' umbrella.
*** This bug has been marked as a duplicate of bug 580455 ***