On Thu, Feb 28, 2013 at 02:23:42PM +0100, Jan Kiszka wrote: > On 2013-02-28 13:13, Hu Tao wrote: > > From: Wen Congyang <wency@xxxxxxxxxxxxxx> > > > > The guest should run after resetting it, but it does not run if its > > old state is RUN_STATE_INTERNAL_ERROR or RUN_STATE_PAUSED. > > > > We don't set runstate to RUN_STATE_PAUSED when resetting the guest, > > so the runstate will be changed from RUN_STATE_INTERNAL_ERROR or > > RUN_STATE_PAUSED to RUN_STATE_RUNNING(not RUN_STATE_PAUSED). > > I just wonder what will happen if I interrupted the guest via gdb and > then issue "monitor system_reset", also via gdb - common pattern if you > set a breakpoint on some BUG() or fault handler and then want to restart > the guest. Will the guest continue then while gdb thinks it is still > stopped? Likely, we do not differentiate between gdb-initiated stops and > the rest. Could you clarify? Guest won't continue unless issue gdb "continue". Anyway, I'll seperate this patch, as Paolo requested. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
