From mboxrd@z Thu Jan  1 00:00:00 1970
From: Samuel Thibault <samuel.thibault@eu.citrix.com>
Subject: Re: VMX nightly testing for Xen:#17269 is blocked
Date: Fri, 21 Mar 2008 13:53:24 +0000
Message-ID: <20080321135324.GF4353@implementation.uk.xensource.com>
References: <FC1D1B23302A22499C60C967336B2AE0028B70F3@pdsmsx411.ccr.corp.intel.com>
	<C4092E17.153FE%keir.fraser@eu.citrix.com>
	<FC1D1B23302A22499C60C967336B2AE0028B71EE@pdsmsx411.ccr.corp.intel.com>
	<20080321115307.GA8067@implementation.uk.xensource.com>
	<FC1D1B23302A22499C60C967336B2AE0028B7254@pdsmsx411.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="FCuugMFkClbJLl1L"
Content-Transfer-Encoding: 8bit
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <FC1D1B23302A22499C60C967336B2AE0028B7254@pdsmsx411.ccr.corp.intel.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "Li, Haicheng" <haicheng.li@intel.com>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir.fraser@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org


--FCuugMFkClbJLl1L
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Li, Haicheng, le Fri 21 Mar 2008 21:02:30 +0800, a écrit :
> Actually since qemu window disappears immediately after OS enters graphic mode, it's hard to locate the exact step.
> Only can say it is just after `startx &`  on Linux and "driver loading progress bar" on Windows. 

Ok, so that's when we switch to OpenGL rendering.

> > Could you tell the exact configuration of Windows/Linux?
> Guest config file is attached.

Well, I meant the guest configuration actually (resolution/color depth).

> > Are there useful information in /var/log/xen/qemu-dm-yourdomain.log?
> Seems no useful info for this bug in qemu log.

Indeed :/

Could you try to use the attached qemu-dm.gdb script for the device
model?  It is just a gdb wrapper around the actual qemu-dm, which should
let get a backtrace.

Samuel

--FCuugMFkClbJLl1L
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="qemu-dm.gdb"

#!/bin/sh

if [ "`arch`" = "x86_64" ]; then
    LIBDIR="lib64"
else
    LIBDIR="lib"
fi
xterm -e /bin/sh -c "gdb --args /usr/$LIBDIR/xen/bin/qemu-dm $*"

--FCuugMFkClbJLl1L
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--FCuugMFkClbJLl1L--