[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bulk] Re: [Bulk] Re: [Xen-users] eth0 / device problem in dom0


  • To: Peter Fastré <peter.fastre@xxxxxxxxx>
  • From: phcolaris <phcolaris@xxxxxxxxxxx>
  • Date: Tue, 27 Mar 2007 19:04:25 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 27 Mar 2007 11:03:02 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=Received:X-YMail-OSG:Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date:Message-Id:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=Vr4wxDUirvdgrc6ewsAvZKTEpEhpqB5NTzBwNwfJvHcAe2t/m2sNJevtu2CgVv/W5o8Wq7wxep9ZQ4ct3MsnHQN7FL6PFmWyyFnWJmGNA/eO0g13wUA5aBJtmiVXpXX8OHMUTxicIvD6zZwKLgvPBF0VyH+r1i/Pr9/Q36rn3jo= ;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

well, got the driver, after loading got this

Intel(R) PRO/1000 Network Driver - version 7.4.35
Copyright (c) 1999-2007 Intel Corporation.
GSI 17 sharing vector 0xA0 and IRQ 17
ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 24 (level, low) -> IRQ 17
e1000: 0000:00:04.0: e1000_probe: (PCI:33MHz:32-bit) 00:e0:81:47:e2:8c
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection


so I believe that its just fine. but the boot is without change :-(

any idea?

thanks
phil


boot log:

Loading console font lat9w-16.psfu  -m trivial G0:loadable
done
BLKTAPCTRL[3818]: blktapctrl: v1.0.0

BLKTAPCTRL[3818]: Found driver: [raw image (aio)]

BLKTAPCTRL[3818]: Found driver: [raw image (sync)]

BLKTAPCTRL[3818]: Found driver: [vmware image (vmdk)]

BLKTAPCTRL[3818]: Found driver: [ramdisk image (ram)]

BLKTAPCTRL[3818]: Found driver: [qcow disk (qcow)]

BLKTAPCTRL[3818]: /dev/xen/blktap0 device already exists

device vif0.0 entered promiscuous mode
xenbr0: port 1(vif0.0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 1(vif0.0) entering forwarding state
e1000: peth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex,
Flow Control: RX
device peth0 entered promiscuous mode
xenbr0: port 2(peth0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 2(peth0) entering forwarding state
Setting up network interfaces:
    lo        
    lo        IP address: 127.0.0.1/8
done
    eth0      
              No configuration found for eth0
unused
    veth0     
              No configuration found for veth0
unused
    veth1     
              No configuration found for veth1
unused
    veth2     
              No configuration found for veth2
unused
    veth3     
              No configuration found for veth3
unused
    vif0.0    
              No configuration found for vif0.0
unused
    vif0.1    
              No configuration found for vif0.1
unused
    vif0.2    
              No configuration found for vif0.2
unused
    vif0.3    
              No configuration found for vif0.3
unused
Waiting for mandatory devices:  eth-bus-pci-0000:00:04.0 __NSC__
18 17 16 15 14 13 12 11 10 9 8 6 5 4 3 2 1 0 
    peth0     
              No configuration found for peth0
failed
    peth0     interface could not be set up until now
failed
Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  .
failed




On Tue, 2007-03-27 at 16:47 +0200, Peter Fastré wrote:
> 
> 
> On 3/27/07, phcolaris <phcolaris@xxxxxxxxxxx> wrote:
>         
>         00:04.0 Ethernet controller: Intel Corporation 82541GI Gigabit
>         Ethernet
>         Controller (rev 05)
> 
> I have a recent supermicro server, and the Intel network cards weren't
> recognized by the 2.6.16.33 kernel either. You can get an updated
> driver from http://sourceforge.net/projects/e1000.
> 
> You can compile the driver as a module, as described in the driver
> install procedure. If you do that, however, you have to make sure you
> don't have the older e1000 driver compiled in your kernel. So
> recompile your Xen kernel WITHOUT the intel e1000 driver. It took me
> some time before I had figured that out. 
> You can also replace the driver in the 2.6.16.33-kernel by the files
> you got from sourceforge. This way, it's possible to compile the
> driver in the kernel, if you would like that.
> 
> Peter
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


        
        
                
___________________________________________________________ 
Win tickets to the 2006 FIFA World Cup Germany with Yahoo! Messenger. 
http://advision.webevents.yahoo.com/fifaworldcup_uk/


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.