Re: [Qemu-devel] [PATCH] Adds null check for DisplayStatus

[Gerd Hoffmann <kraxel@redhat.com>]

Stefano Stabellini wrote:
> Allocate a DisplaySurface in dumb_display_init if none else does it.
> The DisplaySurface will be used for the qemu monitor, serial and
> parallel ports, etc.

Ah.  That one should fix the "-vga none -vnc :0" crashes, right?

Some more displaystate questions:

I'm sitting here with a initialization order issue I'm not sure how to
tackle best.  xenfb calls graphics_console_init() once the frontend and
backend finished the handshake, usually a few seconds after the guest
started running.  In case the guest has no framebuffer frontend driver
the graphics_console_init() call doesn't happen at all.  So it behaves
like a hot-plugged graphics card.

With the new displaystate allocation rules and dumb_display_init() in
place I will end up with *two* displaystates in case I keep the setup
logic this way.  Is that going to work?  There is a new
register_displaystate() which maintains a linked list of displaystates,
so it looks like it might work?  Or is this work in progress?

What do you suggest to do?  What other patches do you have in the queue
I maybe should know about when adapting xenfb?  Will the text consoles
(monitor, serial line, ...) continue to hitchhike on the displaystate of
the graphics display?

cheers,
  Gerd