Re: [Xen-devel] HVM domU with sdl not scheduled after vt-switch

[Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>]

Am 28.04.2011 schrieb "Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>":

> Am 27.04.2011 schrieb "Vincent Hanquez <vincent.hanquez@xxxxxxxxxxxxx>":

> > On 04/27/2011 12:27 PM, Dietmar Hahn wrote:

> > >

> > > The domU gets scheduled again after switching back to the virtual screen.

> > >

> > > This is not the case when using vnc.

> > >

> > > What is the cause and where in the source can I find the implementation?

> > >

> > > Thanks!

> > >

> > That's a known problem of SDL generally, it's not linked to qemu itself

> > (i've seen the same behavior happened on other program using SDL). You

> > probably want to look at the SDL source for the reason why.

>

> Great, I will have a look at this.

It hangs in qemu in gui_update() -> dpy_refresh() -> sdl_refresh()

Via libSDL, libX11, libxcb the function xcb_wait_for_reply() gets called.

It never gets an answer from the Xserver, because the Xserver doesn't answer

any requests when switching the vt-console.

Because gui_update() gets called via a qemu timer and never return it stops qemu.

I tried to move the qui_update() into an own thread to get the main qemu loop

running but then the first call of sdl_update() leads to:

X Error of failed request: BadAccess (attempt to access private resource denied)

Major opcode of failed request: 154 (GLX)

Minor opcode of failed request: 26 (X_GLXMakeContextCurrent)

Serial number of failed request: 31

Current serial number in output stream: 31

and qemu exits.

I googled a little bit and found XInitThreads() but this doesn't help.

Any hints are welcome ;-) !

Dietmar.

--

Company details: http://ts.fujitsu.com/imprint.html

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