Bug 608415 - unable to re-generate ifcfg-eth0 for virtio NIC
Summary: unable to re-generate ifcfg-eth0 for virtio NIC
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kudzu   
(Show other bugs)
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Bill Nottingham
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-27 12:38 UTC by Qian Cai
Modified: 2014-03-17 03:24 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Qian Cai 2010-06-27 12:38:51 UTC 
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):
kudzu-1.2.57.1.24-1
kernel-2.6.18-194.el5

HOST:
kernel-2.6.32-37.el6.x86_64
qemu-kvm-0.12.1.2-2.78.el6.x86_64

How reproducible:
always

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 Qian Cai 2010-06-27 13:08:41 UTC 
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 Qian Cai 2010-06-27 13:17:56 UTC 
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.