Bug 239404 - e1000 driver doesn't configure and xen won't create virtual machines
Summary: e1000 driver doesn't configure and xen won't create virtual machines
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xen
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Xen Maintainance List
QA Contact: Virtualization Bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2007-05-08 08:19 UTC by Steven Dake
Modified: 2016-04-26 14:13 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2009-01-13 15:23:38 UTC

Attachments (Terms of Use)

Description Steven Dake 2007-05-08 08:19:13 UTC
Description of problem:
xen doesn't create virtual machines on a T60 laptop unless a network cable is
plugged into the network port and attached to a switch/hub.

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

How reproducible:

Steps to Reproduce:
1. Boot Thinkpad T60 laptop ordered from Red Hat internal sourcing as of May
2007 without network cable plugged in with E1000 network port configured to
static IP addressing
2. xm create -c rhel5n1 (where rhel5n1 is a working virtual machine)
Actual results:
xm create command reports error and doesn't create a virtual machine

Expected results:
xm create should create a virtual machine 

Additional info:
I noticed that if I later plug in the e1000 network cable, xm create works. 
Then if I unplug the network cable, xm create continues to work properly.

It also appears that ifcfg-eth1 is not properly configuring the E1000 network
interface address during startup - but only setting it properly when the network
cable is plugged in.  Once the cable has been plugged in and xend restarted, the
system works properly.

This makes using xen difficult on the T60 requiring plugging the t60 laptop into
a network port at some point before using xen.

Reference bz 239201 which indicates the ipw3945 wireless card does not work at
all with the xen kernel without changing start orders of init scripts.  Note
during this bug report I reverted all start orders to those start orders shipped
with RHEL5.  The ipw3945 wireless adapter can also not be used to boot the xen
machines as a result.

Comment 2 Daniel Berrange 2008-07-11 13:10:31 UTC
Please provide more information if this is still a problem,

 - /var/log/messages
 - /var/log/dmesg
 - ifconfig -a
 - lspci -vv

Comment 3 Rik van Riel 2009-01-09 18:39:11 UTC
This looks like a userspace issue, either with userspace xen or virt-manager and friends.

Comment 6 Rik van Riel 2009-01-13 15:23:38 UTC
Apparently this was fixed by RHEL 5.2.

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