From owner-freebsd-xen@FreeBSD.ORG  Thu Aug 29 10:07:30 2013
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id E529B78A
 for <freebsd-xen@freebsd.org>; Thu, 29 Aug 2013 10:07:30 +0000 (UTC)
 (envelope-from kpielorz_lst@tdx.co.uk)
Received: from mail.tdx.com (mail.tdx.com [62.13.128.18])
 by mx1.freebsd.org (Postfix) with ESMTP id AED3E25FA
 for <freebsd-xen@freebsd.org>; Thu, 29 Aug 2013 10:07:30 +0000 (UTC)
Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251])
 (authenticated bits=0)
 by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id r7TA7Sb4034091
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
 for <freebsd-xen@freebsd.org>; Thu, 29 Aug 2013 11:07:29 +0100 (BST)
Date: Thu, 29 Aug 2013 11:07:30 +0100
From: Karl Pielorz <kpielorz_lst@tdx.co.uk>
To: freebsd-xen@freebsd.org
Subject: Console 'lag'?
Message-ID: <974A077DC3EC33CC574373B6@Mail-PC.tdx.co.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 10:07:31 -0000


So we've got our test FreeBSD 9.2-RC3 amd64 system running under Xen Server 
6.2 - with the xen 'guest' tools enabled (i.e. Xen Server can see it can 
suspend / resume the guest etc.)

We've noticed the console under XenCenter 'lags' sometimes - or, more 
accurately it doesn't update until you hit a key.

Best example is:

root@v1:~ #echo "Hello World!"
Hello World!

You *sometimes* don't get the prompt back, until you press a key. Other 
examples would be running 'ps ax' - nothing appears to happen - again, 
until you press another key.

This is only a cosmetic annoyance - just wondered if it was a known issue / 
any fix for it?

-Karl