Bug 608415 - unable to re-generate ifcfg-eth0 for virtio NIC
unable to re-generate ifcfg-eth0 for virtio NIC
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kudzu (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Bill Nottingham
BaseOS QE Security Team
Depends On:
  Show dependency treegraph
Reported: 2010-06-27 08:38 EDT by CAI Qian
Modified: 2014-03-16 23:24 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-27 09:17:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description CAI Qian 2010-06-27 08:38:51 EDT
Description of problem:
If ifcfg-eth0 had been removed or changed to another NIC before changed back to virtio NIC in a rhel5.5 guest, it ended up ifcfg-eth0 was not re-generated.

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1. remove /etc/sysconfig/network-scripts/ifcfg-eth0
2. reboot the guest
Actual results:
no eth0

Expected results:
eth0 is up
Comment 1 CAI Qian 2010-06-27 09:08:41 EDT
I think the real problem is the sequence,
1) remove ifcfg-eth0 under virtio NIC
2) change the NIC to other NICs (like e1000) and reboot
3) change the NIC to virtio NIC and reboot

In rhel4.8, kudzu detected the change and re-generated ifcfg-eth0 in both 2) and 3). In rhel5.5, it only generated it in 2).
Comment 2 CAI Qian 2010-06-27 09:17:56 EDT
Oops, looks like e1000 behaviour the same. Although this is a different behaviour with rhel4.8, I am fine with the new behaviour.

Note You need to log in before you can comment on or make changes to this bug.