linux-kernel - Re: KVM oops: killing interrupt handler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45CF3BF0.2070103@qumranet.com>
Date:	Sun, 11 Feb 2007 17:53:20 +0200
From:	Avi Kivity <avi@...ranet.com>
To:	Jiri Slaby <jirislaby@...il.com>
CC:	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	kvm-devel@...ts.sourceforge.net
Subject: Re: KVM oops: killing interrupt handler

Jiri Slaby wrote:
> On 2/11/07, Avi Kivity <avi@...ranet.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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/