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

VTI hitting the blocked state (was RE: [PATCH][RESEND]RE: [Xen-ia64-deve

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Subject: VTI hitting the blocked state (was RE: [PATCH][RESEND]RE: [Xen-ia64-devel] [PATCH 0/6] Add fullevtchnmechanism for xen/ia64)
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Wed, 24 May 2006 12:54:58 -0600
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 24 May 2006 11:55:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1148485562.29955.52.camel@localhost>
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>
Organization: LOSL
References: <571ACEFD467F7749BC50E0A98C17CDD8094E7C9D@pdsmsx403> <1148449700.29955.36.camel@localhost> <1148485562.29955.52.camel@localhost>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2006-05-24 at 09:46 -0600, Alex Williamson wrote:
> 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,

  I hit this again building a kernel in a domVTI (RHEL4U3 guest).  I was
only using the network for an ssh login.  The build ran for a while,
consumed 3600+ seconds as reported by xm list, but is now stuck in the
blocked state.  Thanks,

        Alex
-- 
Alex Williamson                             HP Linux & Open Source Lab


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