At 06/13/2012 03:53 PM, Paolo Bonzini Wrote:
> Il 13/06/2012 09:02, Wen Congyang ha scritto:
>> +Other possible actions are:
>> +@code{pause} (emit QEVENT_GUEST_PANICKED and pause VM),
>> +@code{quit} (emit QEVENT_GUEST_PANICKED and quit VM).
Rather than just "quit", there sho
Il 13/06/2012 09:02, Wen Congyang ha scritto:
>>> >> +Other possible actions are:
>>> >> +@code{pause} (emit QEVENT_GUEST_PANICKED and pause VM),
>>> >> +@code{quit} (emit QEVENT_GUEST_PANICKED and quit VM).
>> >
>> > Rather than just "quit", there should be choices for "shutdown",
>> > "poweroff"
At 06/12/2012 09:29 PM, Paolo Bonzini Wrote:
> Il 21/05/2012 08:50, Wen Congyang ha scritto:
>> +DEF("onpanic", HAS_ARG, QEMU_OPTION_onpanic, \
>> +"-onpanic report|pause|quit\n" \
>> +"action when the guest is panicked [default=report]",
>> +QEMU_ARCH_ALL)
>> +STEXI
>>
Il 21/05/2012 08:50, Wen Congyang ha scritto:
> +DEF("onpanic", HAS_ARG, QEMU_OPTION_onpanic, \
> +"-onpanic report|pause|quit\n" \
> +"action when the guest is panicked [default=report]",
> +QEMU_ARCH_ALL)
> +STEXI
> +@item -onpanic @var{action}
> +
> +The @var{action}
On Tue, 12 Jun 2012 13:40:45 +0100
"Daniel P. Berrange" wrote:
> On Tue, Jun 12, 2012 at 09:35:04AM -0300, Luiz Capitulino wrote:
> > On Tue, 12 Jun 2012 14:55:37 +0800
> > Wen Congyang wrote:
> >
> > > >> +static void panicked_perform_action(void)
> > > >> +{
> > > >> +switch(panicked_acti
On Tue, Jun 12, 2012 at 09:35:04AM -0300, Luiz Capitulino wrote:
> On Tue, 12 Jun 2012 14:55:37 +0800
> Wen Congyang wrote:
>
> > >> +static void panicked_perform_action(void)
> > >> +{
> > >> +switch(panicked_action) {
> > >> +case PANICKED_REPORT:
> > >> +panicked_mon_event("rep
On Tue, 12 Jun 2012 14:55:37 +0800
Wen Congyang wrote:
> >> +static void panicked_perform_action(void)
> >> +{
> >> +switch(panicked_action) {
> >> +case PANICKED_REPORT:
> >> +panicked_mon_event("report");
> >> +break;
> >> +
> >> +case PANICKED_PAUSE:
> >> +p
At 05/31/2012 03:23 AM, Luiz Capitulino Wrote:
> On Mon, 21 May 2012 14:50:51 +0800
> Wen Congyang wrote:
>
>> When the guest is panicked, it will write 0x1 to the port 0x505. So if
>> qemu reads 0x1 from this port, we can do the folloing three things
>> according to the parameter -onpanic:
>> 1.
On Mon, 21 May 2012 14:50:51 +0800
Wen Congyang wrote:
> When the guest is panicked, it will write 0x1 to the port 0x505. So if
> qemu reads 0x1 from this port, we can do the folloing three things
> according to the parameter -onpanic:
> 1. emit QEVENT_GUEST_PANICKED only
> 2. emit QEVENT_GUEST_P
On 2012-05-21 03:50, Wen Congyang wrote:
> When the guest is panicked, it will write 0x1 to the port 0x505. So if
> qemu reads 0x1 from this port, we can do the folloing three things
> according to the parameter -onpanic:
> 1. emit QEVENT_GUEST_PANICKED only
> 2. emit QEVENT_GUEST_PANICKED and paus
When the guest is panicked, it will write 0x1 to the port 0x505. So if
qemu reads 0x1 from this port, we can do the folloing three things
according to the parameter -onpanic:
1. emit QEVENT_GUEST_PANICKED only
2. emit QEVENT_GUEST_PANICKED and pause VM
3. emit QEVENT_GUEST_PANICKED and quit VM
Not
11 matches
Mail list logo
