[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall
|
From: |
Jan Kiszka |
|
Subject: |
Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall |
|
Date: |
Mon, 20 Jun 2011 17:59:19 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 |
On 2011-06-20 17:45, Avi Kivity wrote:
>> This series does need to introduce a QMP event notification upon
>> crash, so that the crash notification can be propagated to mgmt
>> layers above QEMU.
>
> Yes.
I think the best way to deal with that is to stop the VM on guest panic.
There is already WIP to signal stop reasons via QMP. Maybe we need to
differentiate between hypervisor and guest triggered panics
(VMSTOP_GUEST_PANIC?), but the rest should come for free.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
- Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall, Avi Kivity, 2011/06/20
- Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall,
Jan Kiszka <=
- Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall, Daniel Gollub, 2011/06/20
- Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall, Gleb Natapov, 2011/06/21
- Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall, Avi Kivity, 2011/06/21
- Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall, Gleb Natapov, 2011/06/21
- Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall, Avi Kivity, 2011/06/21
- Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall, Gleb Natapov, 2011/06/21