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). > 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. AFAIK Fabrice isn't supported of externel GUIs for qemu. He wants to have the code as part of qemu. (He has no preference however. GTK or Qt or something else will be fine, as long as it works, the code is simple, and it is easy to use.) > Then another application (running as a separate process) can use a > GtkSocket to embed the QEMU vga device within a larger GUI. > It would be nice if we could keep some sort of GUI-less mode (like what we have now), so that we only have to run one executable/process in order to run a guest. > Regards, > > Anthony Liguori > -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection. _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel