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

RE: [PATCH][RESEND]RE: [Xen-ia64-devel] [PATCH 0/6] Addfullevtchnmechanism for xen/ia64


  • To: "Alex Williamson" <alex.williamson@xxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Thu, 25 May 2006 09:56:59 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 24 May 2006 18:57:17 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZ/SUTl69zTlRLwQkap/CPrkCfyLAAVKQiQ
  • Thread-topic: [PATCH][RESEND]RE: [Xen-ia64-devel] [PATCH 0/6] Addfullevtchnmechanism for xen/ia64

>From: Alex Williamson [mailto:alex.williamson@xxxxxx]
>Sent: 2006年5月24日 23:46
>
>On Tue, 2006-05-23 at 23:48 -0600, Alex Williamson wrote:
>>    It appeared to be stuck in the "-b----" state as shown by xm list,
>> but let me do some verification tomorrow.  Thanks for testing this.
>I'm
>> running UP dom0 + 4-way SMP domU + UP domVTI on an 8 thread (4
>core)
>> system.  Thanks,
>
>   Actually, running networking in domU concurrently accelerates the
>problem, but is not required.  I hit it again with only a domVTI
>running.  I'm pulling a 512MB empty file from another server and writing
>it to /dev/null using wget.  At some point it just stops and xm list
>reports the domain as blocked.  There's nothing in xend.log or
>xend-debug.log to indicate something went bad.  The qemu-dm
>process has
>select listed in it's wait channel, so seems like it's ok.  Thanks,
>
>       Alex
>

Thanks for detail info. Then can VTI domain resume the process after 
some period of 'block'?

Thanks,
Kevin

_______________________________________________
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®.