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

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


  • To: "Zhang, Xing Z" <xing.z.zhang@xxxxxxxxx>, "Mu, Qin" <qin.mu@xxxxxxxxx>
  • From: "You, Yongkang" <yongkang.you@xxxxxxxxx>
  • Date: Wed, 28 Nov 2007 23:25:41 +0800
  • Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 28 Nov 2007 07:26:51 -0800
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcgmnTeWlhoJ945gS6GkmYSFS506DAFQ2VMgAW1h9UAADEVkIAAC2w5g
  • Thread-topic: [Xen-ia64-devel] [PATCH]E100 network card emulator

Em, it might be the issue of using default Linux e100 driver/ 
Qin, you can try with eepro100 driver.

Best Regards,
Yongkang You
 

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
>Of Zhang, Xing Z
>Sent: Wednesday, November 28, 2007 10:11 PM
>To: Mu, Qin
>Cc: xen-ia64-devel
>Subject: RE: [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
>

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


 


Rackspace

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