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-ia64-devel

RE: [Xen-ia64-devel] [PATCH]E100 network card emulator

To: "Mu, Qin" <qin.mu@xxxxxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH]E100 network card emulator
From: "Zhang, Xing Z" <xing.z.zhang@xxxxxxxxx>
Date: Wed, 28 Nov 2007 22:10:50 +0800
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 28 Nov 2007 06:12:26 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <FC1D1B23302A22499C60C967336B2AE0015DFE5E@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <823A93EED437D048963A3697DB0E35DEE2929E@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <823A93EED437D048963A3697DB0E35DEE6FFB2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <FC1D1B23302A22499C60C967336B2AE0015DFE5E@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgmnTeWlhoJ945gS6GkmYSFS506DAFQ2VMgAW1h9UAADEVkIA==
Thread-topic: [Xen-ia64-devel] [PATCH]E100 network card emulator

>
>Hi, Xing
>
>The E100 network card emulator can't keep functioning in guest
>HVM with the following run environment.
>
>       Xen:
>               1. xen unstable tree, Cset = 16470 (latest)
>               2. open guest firmware, Cset=35:ebf7052731ec (latest)
>
>       Guest HVM Configuration:
>               1. memory=1024
>               2. vcpus=2
>               3. acpi=1
>               4. apic=1
>               5. sdl=1
>               6. vif=['bridge=xenbr0, type=ioemu, model=e100']
>               7. serial=pty
>               8. guest_os_type=linux
>
>Both RHEL5GA and RHEL4u3 as guest HVM OS are used in my
>experiments. E100 network card can be successfully recognized
>and setup during system booting. Although it indeed works as
>expected when use ping, ssh and scp command, the happy work time
>can't last more than 5 minutes. It always failed to require IP
>address again by using "ifup eth0" or "service network restart".
>
>Are there key points missed to make the E100 network care
>emulator functions in guest HVM?
>
>Your help will be appreciated very much!
>
>Amy
>
>
Let's make clear about it. 
1. You use linux guest, don't you?
2. You boot HVM with eepro100 driver in linux?
3. You ping HVM guest and failed after 5 minutes? Do you get "no available 
buffer" message in guest?
If so, this is a known issue, I met it when I use ping in linux guest with 
eepro100 driver. When I changing to e100 driver with an interrupt fixing patch, 
"ping" works well. 
So I don't know how native performs. 
Firstly, I want to know whether you get error info while you use
"ping" in guest. 

BTW: while "ping" failed with "no available buffer" info, network doesn't hang.

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