Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-21 Thread shawn che
HI, I am using kvm-kmod with version 2.6.36, but I encountered a fatal problem. In linux run on KVM,I using request(irq,*,*,*) function to request a interrupt line. However, When I using a irq bigger than 15, it will return error. Now I have simulated a PCI device and decide to using IOAPIC to sen

Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-21 Thread Avi Kivity
On 06/21/2011 12:03 PM, Gleb Natapov wrote:> >> > >Something like steal time, but for watchdog. But this become complicated fast. > >Watchdog emulation will have to move into kernel for starter. > > Why? You can use a performance counter from userspace. > Heh, haven't thought about such way

Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-21 Thread Gleb Natapov
On Tue, Jun 21, 2011 at 11:56:26AM +0300, Avi Kivity wrote: > On 06/21/2011 11:41 AM, Gleb Natapov wrote: > >On Tue, Jun 21, 2011 at 11:09:21AM +0300, Avi Kivity wrote: > >> On 06/21/2011 09:02 AM, Gleb Natapov wrote: > >> >On Mon, Jun 20, 2011 at 07:34:57PM +0300, Avi Kivity wrote: > >> >> >T

Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-21 Thread Avi Kivity
On 06/21/2011 11:41 AM, Gleb Natapov wrote: On Tue, Jun 21, 2011 at 11:09:21AM +0300, Avi Kivity wrote: > On 06/21/2011 09:02 AM, Gleb Natapov wrote: > >On Mon, Jun 20, 2011 at 07:34:57PM +0300, Avi Kivity wrote: > >> >The only two things which came to my mind are: > >> > > >> >* N

Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-21 Thread Gleb Natapov
On Tue, Jun 21, 2011 at 11:09:21AM +0300, Avi Kivity wrote: > On 06/21/2011 09:02 AM, Gleb Natapov wrote: > >On Mon, Jun 20, 2011 at 07:34:57PM +0300, Avi Kivity wrote: > >> >The only two things which came to my mind are: > >> > > >> > * NMI (aka. ipmitool diag) - already available in qemu/kvm

Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-21 Thread Avi Kivity
On 06/21/2011 09:02 AM, Gleb Natapov wrote: On Mon, Jun 20, 2011 at 07:34:57PM +0300, Avi Kivity wrote: > >The only two things which came to my mind are: > > > > * NMI (aka. ipmitool diag) - already available in qemu/kvm - but requires > > in-guest kexec/kdump > > * Hardware-Watchdog

Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-20 Thread Gleb Natapov
On Mon, Jun 20, 2011 at 08:23:20PM +0300, Avi Kivity wrote: > On 06/20/2011 08:13 PM, Jan Kiszka wrote: > >> A watchdog has the advantage that is also detects lockups. > >> > >> In fact you could implement the panic device via the existing > >> watchdogs. Simply program the timer for the minimu

Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-20 Thread Gleb Natapov
On Mon, Jun 20, 2011 at 07:34:57PM +0300, Avi Kivity wrote: > >The only two things which came to my mind are: > > > > * NMI (aka. ipmitool diag) - already available in qemu/kvm - but requires > >in-guest kexec/kdump > > * Hardware-Watchdog (also available in qemu/libvirt) > > A watchdog has

Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-20 Thread Jan Kiszka
On 2011-06-20 18:34, Avi Kivity wrote: >> > >> > Do ILO cards / IPMI support something like this? We could follow >> their >> > lead in that case. >> >> The only two things which came to my mind are: >> >> * NMI (aka. ipmitool diag) - already available in qemu/kvm - but >> requires >> in-g

Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-20 Thread Avi Kivity
On 06/20/2011 08:13 PM, Jan Kiszka wrote: > A watchdog has the advantage that is also detects lockups. > > In fact you could implement the panic device via the existing > watchdogs. Simply program the timer for the minimum interval and > *don't* service the interrupt. This would work for no

Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-20 Thread Avi Kivity
On 06/20/2011 07:26 PM, Daniel Gollub wrote: > > I agree. But let's do this via a device, this way kvm need not be changed. Is a device reliable enough if the guest kernel crashes? Do you mean something like a hardware watchdog? I'm proposing a 1:1 equivalent. Instead of issuing a hypercall

Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-20 Thread Daniel Gollub
On Monday, June 20, 2011 05:45:36 pm Avi Kivity wrote: > > > However, I'm not sure I see the gain. Most enterprisey guests > > > already contain in-guest crash dumpers which provide more > > > information than a qemu memory dump could, since they know exact > > > load addresses etc. and are in

Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-20 Thread Jan Kiszka
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 WI

Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall

2011-06-20 Thread Avi Kivity
On 06/20/2011 06:38 PM, Daniel P. Berrange wrote: On Mon, Jun 20, 2011 at 06:31:23PM +0300, Avi Kivity wrote: > On 06/20/2011 04:38 PM, Daniel Gollub wrote: > >Introduce panic hypercall to enable the crashing guest to notify the > >host. This enables the host to run some actions as soon a gues