From: Peter Lieven <pl@dlhnet.de>
To: Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
Gleb Natapov <gleb@redhat.com>
Subject: Re: race between kvm-kmod-3.0 and kvm-kmod-3.3 // was: race condition in qemu-kvm-1.0.1
Date: Wed, 04 Jul 2012 16:57:04 +0200 [thread overview]
Message-ID: <4FF459C0.2060608@dlhnet.de> (raw)
In-Reply-To: <4FF2F2D7.2050207@redhat.com>
On 07/03/12 15:25, Avi Kivity wrote:
> On 07/03/2012 04:15 PM, Peter Lieven wrote:
>> On 03.07.2012 15:13, Avi Kivity wrote:
>>> On 07/03/2012 04:01 PM, Peter Lieven wrote:
>>>> Further output from my testing.
>>>>
>>>> Working:
>>>> Linux 2.6.38 with included kvm module
>>>> Linux 3.0.0 with included kvm module
>>>>
>>>> Not-Working:
>>>> Linux 3.2.0 with included kvm module
>>>> Linux 2.6.28 with kvm-kmod 3.4
>>>> Linux 3.0.0 with kvm-kmod 3.4
>>>> Linux 3.2.0 with kvm-kmod 3.4
>>>>
>>>> I can trigger the race with any of qemu-kvm 0.12.5, 1.0 or 1.0.1.
>>>> It might be that the code was introduced somewhere between 3.0.0
>>>> and 3.2.0 in the kvm kernel module and that the flaw is not
>>>> in qemu-kvm.
>>>>
>>>> Any hints?
>>>>
>>> A bisect could tell us where the problem is.
>>>
>>> To avoid bisecting all of linux, try
>>>
>>> git bisect v3.2 v3.0 virt/kvm arch/x86/kvm
>>>
>>>
>> would it also be ok to bisect kvm-kmod?
> Yes, but note that kvm-kmod is spread across two repositories which are
> not often tested out of sync, so you may get build failures.
>
ok, i just started with this with a 3.0 (good) and 3.2 (bad) vanilla
kernel. i can confirm
the bug and i am no starting to bisect. it will take while with my
equipment if anyone
has a powerful testbed to run this i would greatly appreciate help.
if anyone wants to reproduce:
a) v3.2 from git.kernel.org
b) qemu-kvm 1.0.1 from sourceforge
c) ubuntu 64-bit 12.04 server cd
d) empty (e.g. all zero) hard disk image
cmdline:
./qemu-system-x86_64 -m 512 -cdrom
/home/lieven/Downloads/ubuntu-12.04-server-amd64.iso -hda
/dev/hd1/vmtest -vnc :1 -monitor stdio -boot dc
then choose boot from first harddisk and try to quit the qemu monitor
with 'quit'. -> hypervisor hangs.
peter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Lieven <pl@dlhnet.de>
To: Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Gleb Natapov <gleb@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] race between kvm-kmod-3.0 and kvm-kmod-3.3 // was: race condition in qemu-kvm-1.0.1
Date: Wed, 04 Jul 2012 16:57:04 +0200 [thread overview]
Message-ID: <4FF459C0.2060608@dlhnet.de> (raw)
In-Reply-To: <4FF2F2D7.2050207@redhat.com>
On 07/03/12 15:25, Avi Kivity wrote:
> On 07/03/2012 04:15 PM, Peter Lieven wrote:
>> On 03.07.2012 15:13, Avi Kivity wrote:
>>> On 07/03/2012 04:01 PM, Peter Lieven wrote:
>>>> Further output from my testing.
>>>>
>>>> Working:
>>>> Linux 2.6.38 with included kvm module
>>>> Linux 3.0.0 with included kvm module
>>>>
>>>> Not-Working:
>>>> Linux 3.2.0 with included kvm module
>>>> Linux 2.6.28 with kvm-kmod 3.4
>>>> Linux 3.0.0 with kvm-kmod 3.4
>>>> Linux 3.2.0 with kvm-kmod 3.4
>>>>
>>>> I can trigger the race with any of qemu-kvm 0.12.5, 1.0 or 1.0.1.
>>>> It might be that the code was introduced somewhere between 3.0.0
>>>> and 3.2.0 in the kvm kernel module and that the flaw is not
>>>> in qemu-kvm.
>>>>
>>>> Any hints?
>>>>
>>> A bisect could tell us where the problem is.
>>>
>>> To avoid bisecting all of linux, try
>>>
>>> git bisect v3.2 v3.0 virt/kvm arch/x86/kvm
>>>
>>>
>> would it also be ok to bisect kvm-kmod?
> Yes, but note that kvm-kmod is spread across two repositories which are
> not often tested out of sync, so you may get build failures.
>
ok, i just started with this with a 3.0 (good) and 3.2 (bad) vanilla
kernel. i can confirm
the bug and i am no starting to bisect. it will take while with my
equipment if anyone
has a powerful testbed to run this i would greatly appreciate help.
if anyone wants to reproduce:
a) v3.2 from git.kernel.org
b) qemu-kvm 1.0.1 from sourceforge
c) ubuntu 64-bit 12.04 server cd
d) empty (e.g. all zero) hard disk image
cmdline:
./qemu-system-x86_64 -m 512 -cdrom
/home/lieven/Downloads/ubuntu-12.04-server-amd64.iso -hda
/dev/hd1/vmtest -vnc :1 -monitor stdio -boot dc
then choose boot from first harddisk and try to quit the qemu monitor
with 'quit'. -> hypervisor hangs.
peter
next prev parent reply other threads:[~2012-07-04 14:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 15:39 race between kvm-kmod-3.0 and kvm-kmod-3.3 // was: race condition in qemu-kvm-1.0.1 Peter Lieven
2012-06-27 16:54 ` Jan Kiszka
2012-06-28 9:11 ` Peter Lieven
2012-06-28 9:21 ` Jan Kiszka
2012-06-28 9:31 ` Peter Lieven
2012-06-28 9:38 ` Peter Lieven
2012-07-02 15:05 ` Avi Kivity
2012-07-02 15:05 ` [Qemu-devel] " Avi Kivity
2012-07-02 15:57 ` Peter Lieven
2012-07-02 15:57 ` [Qemu-devel] " Peter Lieven
2012-07-03 13:01 ` Peter Lieven
2012-07-03 13:01 ` [Qemu-devel] " Peter Lieven
2012-07-03 13:13 ` Avi Kivity
2012-07-03 13:13 ` [Qemu-devel] " Avi Kivity
2012-07-03 13:15 ` Peter Lieven
2012-07-03 13:15 ` [Qemu-devel] " Peter Lieven
2012-07-03 13:25 ` Avi Kivity
2012-07-03 13:25 ` [Qemu-devel] " Avi Kivity
2012-07-04 14:57 ` Peter Lieven [this message]
2012-07-04 14:57 ` Peter Lieven
2012-07-04 23:12 ` Peter Lieven
2012-07-04 23:12 ` [Qemu-devel] " Peter Lieven
2012-07-05 6:48 ` Xiao Guangrong
2012-07-05 6:48 ` [Qemu-devel] " Xiao Guangrong
2012-06-28 9:39 ` Jan Kiszka
2012-06-28 10:13 ` Peter Lieven
2012-06-28 10:34 ` Peter Lieven
2012-07-05 8:51 ` Xiao Guangrong
2012-07-05 8:51 ` [Qemu-devel] " Xiao Guangrong
2012-07-05 12:42 ` Peter Lieven
2012-07-05 12:42 ` [Qemu-devel] " Peter Lieven
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=4FF459C0.2060608@dlhnet.de \
--to=pl@dlhnet.de \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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.