qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Re: QEMU 0.7.2


From: Anthony Liguori
Subject: Re: [Qemu-devel] Re: QEMU 0.7.2
Date: Mon, 12 Sep 2005 22:45:29 -0500
User-agent: Mozilla Thunderbird 1.0.6 (X11/20050831)

Jim C. Brown wrote:

On Mon, Sep 12, 2005 at 07:33:26PM -0500, Anthony Liguori wrote:
What's more, it seems like the easiest way, given the way QEMU currently works, to have an advanced GUI that can manage multiple instances of QEMU (using tabs or something like that).


I'm working on something like that (though I stole the idea from Q, the Mac OS X
Cocoa GUI for qemu). The way it works, one master qemu process creates the
actual window (with full GUI and etc), as well as a VM for one guest. In order
to handle multiple guests, subprocesses are spawned (so one VM per process) but
they display to the GUI of the master process. (Actually, this is implemented
using GtkSocket and GtkPlug.) Currently you'll only be able to see one guest
at a time (though you can switch among them at any time), but I plan on adding
support for using multiple windows later (all windows would be owned and 
controlled by
the same master process).
If I understand this correctly, you have multiple processes displaying to the same widget?

Seems like it would be a lot easier if each process had it's own Socket/Plug pair and then just make use of something like GtkNotebook.

There can then be separate GTK/QT guis without QEMU having to support both widget sets.

Or either (except some minimal GDK and the GtkPlug). There are definite
advantages to going this route.
Yeah, I do like this approach quite a bit. My only concern would be the performance of XShmImage vs whatever SDL is using.

Regards,

Anthony Liguori




reply via email to

[Prev in Thread] Current Thread [Next in Thread]