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

xen-devel

[Top] [All Lists]

RE: [Xen-devel] VMX nightly testing for Xen:#17269 is blocked

To: "Samuel Thibault" <samuel.thibault@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] VMX nightly testing for Xen:#17269 is blocked
From: "Li, Haicheng" <haicheng.li@xxxxxxxxx>
Date: 2008年3月24日 17:26:22 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: 2008年3月24日 02:28:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080321135324.GF4353@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <FC1D1B23302A22499C60C967336B2AE0028B70F3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><C4092E17.153FE%keir.fraser@xxxxxxxxxxxxx><FC1D1B23302A22499C60C967336B2AE0028B71EE@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><20080321115307.GA8067@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx><FC1D1B23302A22499C60C967336B2AE0028B7254@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080321135324.GF4353@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AciLWzzA7knYfXDtT468xlvk6yhvoACMGsNA
Thread-topic: [Xen-devel] VMX nightly testing for Xen:#17269 is blocked
Samuel Thibault wrote:
> 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). 
Resolution: 800 * 600, color: 24 bit.
>>> 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.
There is a segment fault caused by sdl_resize() in tools/ioemu/sdl.c. 
I changed a few code as below and found SDL_SetVideoMode() failed with 
error:Couldn't find matching GLX visual. 
And detailed qemu log is attached.
==
diff -r 76c9cf11ce23 tools/ioemu/sdl.c
--- a/tools/ioemu/sdl.c Fri Mar 21 09:45:34 2008 +0000
+++ b/tools/ioemu/sdl.c Mon Mar 24 16:49:09 2008 +0800
@@ -191,15 +191,18 @@ static void sdl_resize(DisplayState *ds,
 {
 int flags;
 
- // printf("resizing to %d %d\n", w, h);
+ printf("resizing to %d %d\n", w, h);
 
 #ifdef CONFIG_OPENGL
 if (ds->shared_buf && opengl_enabled)
 flags = SDL_OPENGL|SDL_RESIZABLE;
 else
 #endif
- flags = 
SDL_HWSURFACE|SDL_ASYNCBLIT|SDL_HWACCEL|SDL_DOUBLEBUF|SDL_HWPALETTE;
-
+ flags = 
SDL_HWSURFACE|SDL_ASYNCBLIT|SDL_HWACCEL|SDL_DOUBLEBUF|SDL_HWPALETTE;
+
+#ifdef CONFIG_OPENGL
+ printf("opengl is defined\n");
+#endif
 if (gui_fullscreen) {
 flags |= SDL_FULLSCREEN;
 flags &= ~SDL_RESIZABLE;
@@ -210,11 +213,11 @@ static void sdl_resize(DisplayState *ds,
 
 again:
 screen = SDL_SetVideoMode(w, h, 0, flags);
-#ifndef CONFIG_OPENGL
 if (!screen) {
 fprintf(stderr, "Could not open SDL display: %s\n", SDL_GetError());
 exit(1);
 }
+#ifndef CONFIG_OPENGL
 if (!screen->pixels && (flags & SDL_HWSURFACE) && (flags & 
SDL_FULLSCREEN)) {
 flags &= ~SDL_HWSURFACE;
 goto again;
-- haicheng

Attachment: qemu-log.txt
Description: qemu-log.txt

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: [Xen-devel] why each process needs a separate page for kernel's pgd table in PV x86_64? , weiming
Next by Date: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- no new issue , Li, Haicheng
Previous by Thread: Re: [Xen-devel] VMX nightly testing for Xen:#17269 is blocked , Samuel Thibault
Next by Thread: Re: [Xen-devel] VMX nightly testing for Xen:#17269 is blocked , Keir Fraser
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /