lkml.org 
[lkml]   [2012]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 2/2 v3] deal with guest panicked event
At 03/08/2012 06:08 PM, Jan Kiszka Wrote:
> On 2012-03-08 09:07, Wen Congyang wrote:
>> When the host knows the guest is panicked, it will set
>> exit_reason to KVM_EXIT_GUEST_PANICKED. So if qemu receive
>> this exit_reason, we can send a event to tell management
>> application that the guest is panicked and set the guest
>> status to RUN_STATE_PANICKED.
>>
>> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
>> ---
>> kvm-all.c | 4 ++++
>> monitor.c | 3 +++
>> monitor.h | 1 +
>> qapi-schema.json | 2 +-
>> qmp.c | 3 ++-
>> vl.c | 1 +
>> 6 files changed, 12 insertions(+), 2 deletions(-)
>>
>> diff --git a/kvm-all.c b/kvm-all.c
>> index 77eadf6..01062af 100644
>> --- a/kvm-all.c
>> +++ b/kvm-all.c
>> @@ -1290,6 +1290,10 @@ int kvm_cpu_exec(CPUState *env)
>> (uint64_t)run->hw.hardware_exit_reason);
>> ret = -1;
>> break;
>> + case KVM_EXIT_GUEST_PANICKED:
>> + monitor_protocol_event(QEVENT_GUEST_PANICKED, NULL);
>> + vm_stop(RUN_STATE_PANICKED);
>> + break;
>
> You're still lacking "ret = -1;".

Sorry, I forgot it...

Thanks
Wen Congyang

>
> Jan
>



\
 
 \ /
  Last update: 2012-03-08 11:13    [W:0.102 / U:0.312 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site