All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	kvm-devel@lists.sourceforge.net
Subject: Re: KVM oops: killing interrupt handler
Date: Sun, 11 Feb 2007 17:53:20 +0200	[thread overview]
Message-ID: <45CF3BF0.2070103@qumranet.com> (raw)
In-Reply-To: <4af2d03a0702110601g36b4780fuec82be8290d6a397@mail.gmail.com>

Jiri Slaby wrote:
> On 2/11/07, Avi Kivity <avi@qumranet.com> wrote:
>> Jiri Slaby wrote:
>> > Hi!
>> >
>> > My schoolmate got this while using kvm-12 on 2.6.20-rc6:
>> > http://www.fi.muni.cz/~xslaby/sklad/kvm-intel-panic/a/
>> >
>> > Unfortunately it's only shots taken by camera. If we are able to
>> > reproduce it in 2.6.20, we'll grab netconsole output.
>> >
>>
>> What guest? what host?  How to reproduce?
>
> It's intel core 2 duo emulating 32-bit wxp. It happened after
> suspend/resume (he doesn't know if qemu was actually running) of the
> machine.
>

kvm suspend/resume support is only present in -mm (what's more, I don't 
think in any released -mm).  A workaround is to rmmod kvm_intel before 
suspending.



-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jiri Slaby <jirislaby-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Linux kernel mailing list
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: KVM oops: killing interrupt handler
Date: Sun, 11 Feb 2007 17:53:20 +0200	[thread overview]
Message-ID: <45CF3BF0.2070103@qumranet.com> (raw)
In-Reply-To: <4af2d03a0702110601g36b4780fuec82be8290d6a397-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Jiri Slaby wrote:
> On 2/11/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>> Jiri Slaby wrote:
>> > Hi!
>> >
>> > My schoolmate got this while using kvm-12 on 2.6.20-rc6:
>> > http://www.fi.muni.cz/~xslaby/sklad/kvm-intel-panic/a/
>> >
>> > Unfortunately it's only shots taken by camera. If we are able to
>> > reproduce it in 2.6.20, we'll grab netconsole output.
>> >
>>
>> What guest? what host?  How to reproduce?
>
> It's intel core 2 duo emulating 32-bit wxp. It happened after
> suspend/resume (he doesn't know if qemu was actually running) of the
> machine.
>

kvm suspend/resume support is only present in -mm (what's more, I don't 
think in any released -mm).  A workaround is to rmmod kvm_intel before 
suspending.



-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2007-02-11 15:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-10 19:45 KVM oops: killing interrupt handler Jiri Slaby
2007-02-10 19:45 ` Jiri Slaby
2007-02-11  9:02 ` Avi Kivity
2007-02-11  9:02   ` Avi Kivity
2007-02-11 14:01   ` Jiri Slaby
2007-02-11 14:01     ` Jiri Slaby
2007-02-11 15:53     ` Avi Kivity [this message]
2007-02-11 15:53       ` Avi Kivity
2007-02-11 16:19       ` Jiri Slaby
2007-02-11 16:19         ` Jiri Slaby
2007-02-11 16:58       ` Jiri Slaby
2007-02-11 16:58         ` Jiri Slaby
2007-02-11 17:10         ` Avi Kivity
2007-02-11 17:10           ` Avi Kivity
2007-02-11 17:37           ` Jiri Slaby
2007-02-11 17:37             ` Jiri Slaby
2007-02-11 19:18             ` Jiri Slaby
2007-02-11 19:18               ` Jiri Slaby

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45CF3BF0.2070103@qumranet.com \
    --to=avi@qumranet.com \
    --cc=jirislaby@gmail.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.