On 05/17/2010 05:55 PM, Alexander Graf wrote:
IMHO, the problem with an external GUI is that the interaction just gets too
complicated.
What interaction do you mean? I'm not advocating to move the GUI to a different
project. I was more thinking of a separation like with perf where the kernel
side does the recording and the userspace side does the displaying of profiling
results. Qemu would run the VM and the tightly coupled viewer app would show it.
If it's the same project, why go through the extra work of plumbing
everything through an RPC interface? I'm suggesting that we want to
make writing a good GUI as easy as possible and IMHO that means not
putting up an artificial constraint like everything needs to be done
through RPC.
But we're putting the cart before the horse. Let's save this argument
until we have some patches :-)
Regards,
Anthony Liguori
If you like, we could even move the backend qemu to "qemu-backend" and have the
normally invoked binaries be the GUI application that just runs the respective
qemu-backend application. That way it'd be 100% seamless for the average user, but qemu
-demonize becomes really powerful.
Alex
