WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Virtual ethernet driver.

To: Lukasz Grzelak <gigi@xxxxxxx>
Subject: Re: [Xen-devel] Virtual ethernet driver.
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 26 Nov 2004 12:06:06 +0000
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, Jacob Gorm Hansen <jacobg@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Fri, 26 Nov 2004 12:11:20 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: Your message of "Fri, 26 Nov 2004 10:04:22 +0100." <Pine.LNX.4.61.0411260959140.16695@xxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> 
> On Fri, 26 Nov 2004, Ian Pratt wrote:
> 
> > Perhaps start xend with 'xend trace_start' and then see if
> > xend.log can shed any light.
> 
> Xend work fine i thing i have broken kernel or system.

Have you used your own kernel config? You haven't disabled 
CONFIG_XEN_NETDEV_FRONTEND have you?

What happens if you use our binary install?

Ian


> > While the hang is going on, do you see the new vif if you do an
> > 'ifconfig' in domain 0? Has it been added to the bridge?
> 
> 
> 5: xen-br0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
>      link/ether 00:50:da:1c:b1:74 brd ff:ff:ff:ff:ff:ff
>      inet 192.168.244.13/32 scope global xen-br0
>      inet6 fe80::200:ff:fe00:0/64 scope link
> 6: vif1.0: <BROADCAST,MULTICAST,PROMISC> mtu 1500 qdisc noop
>      link/ether aa:00:01:7d:49:8a brd ff:ff:ff:ff:ff:ff
> 
> anubis ~ # brctl show
> bridge name     bridge id               STP enabled     interfaces
> xen-br0         8000.0050da1cb174       no              eth0
>                                                          vif1.0
> 
> 
> vif1.0 added to system and to bridge, but it dont up.
> 
> 
> Pozdrawiam.
> 
> Lukasz Grzelak
> Sys-Net Admin
> ------------------------------------------------------
> iTk - info@xxxxxx - http://www.itk.pl - +48 91 8137012
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel