Am 21.10.2009 20:08, schrieb Anthony Liguori: > Glauber Costa wrote: >> On Wed, Oct 21, 2009 at 2:55 PM, Anthony Liguori <anth...@codemonkey.ws> >> wrote: >> >>> Glauber Costa wrote: >>> >>>> Why don't we provide a mechanism to make a macro out of a sequence of >>>> monitor commands, and let the user assign whatever he wants out of that? >>>> >>>> >>> Really? This seems exceedingly complicated to me. >>> >>> Redirecting the kernel output to serial and logging is a considerably better >>> solution. >>> >> To his specific problem, yes. >> >> But this probably don't work so well on some OSes that are less serial >> friendly. >> Also, there are valid use cases in which one may want, for example, to pause >> fast if some graphical event happens, which is an extension of what he >> mentioned >> initially. >> > > Then type "stop" in the monitor and hit enter when you need to. Or, > write a simple VNC client using gtk-vnc that can have any sort of crazy > key sequences you want.
Having two different consoles at the same time is easy. Guest graphics in the SDL window, serial console on stdio. And now I need to add a monitor. Means that I need to start using named pipes or TCP connections or something. And I need to arrange the windows so that I can see qemu's SDL window and the shell with my netcat (or whatever) gets the enter key I hit. Yes, it's possible, but it's not nice. I like Jamie's suggestion for macros. Kevin
