From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: David Brown <dmlb2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Oopse in kvm
Date: Wed, 18 Apr 2007 18:32:01 +0300 [thread overview]
Message-ID: <462639F1.4020802@qumranet.com> (raw)
In-Reply-To: <9c21eeae0704180802o492dc754p1eef426bc4408e0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
David Brown wrote:
>>
>> I see. Consider it pushed. I'll send it linuswards if there's no
>> negative feedback in a day or two.
>>
>
> Oooo, patch!
>
> What was the method for reproduction? since I was unable to reproduce
> the bug maybe I could with your method.
>
It was the SLES 9 installer/initrd pair, booting with 1.5G RAM
reproduced it almost always.
> Don't worry I'll be on this thread until the problem is fixed, I'm not
> the type that takes the patch and runs with it without telling you
> guys that it indeed fixed the problem. I like the whole cycle; bug
> found, bug fixed, bug verified :)
Great, that increases the probability that the patch is a net gain.
I don't think you need to run the SLES installer as both Sergey and me
have it working. Instead, running with your regular workload (possibly
stressing it) would be a good test.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-04-18 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 20:48 Oopse in kvm David Brown
[not found] ` <9c21eeae0704171348r71a62af8nc98bb018313ca35-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-04-17 20:50 ` David Brown
2007-04-18 4:57 ` Avi Kivity
[not found] ` <4625A521.6010407-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-18 5:11 ` David Brown
2007-04-18 8:21 ` Avi Kivity
[not found] ` <4625D50A.3010005-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-18 14:18 ` Thomas Glanzmann
[not found] ` <20070418141819.GA13284-vCsBGSbFJi4XOLVLeuLo0p3xXOyapcuTYd9OGiuxSwg@public.gmane.org>
2007-04-18 14:30 ` Avi Kivity
[not found] ` <46262BA3.8070307-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-18 14:35 ` Thomas Glanzmann
[not found] ` <20070418143548.GD13284-vCsBGSbFJi4XOLVLeuLo0p3xXOyapcuTYd9OGiuxSwg@public.gmane.org>
2007-04-18 14:42 ` Avi Kivity
[not found] ` <46262E3B.4010608-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-18 15:02 ` David Brown
[not found] ` <9c21eeae0704180802o492dc754p1eef426bc4408e0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-04-18 15:32 ` Avi Kivity [this message]
[not found] ` <462639F1.4020802-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-18 17:07 ` David Brown
2007-04-18 15:07 ` Kiselev, Sergey
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=462639F1.4020802@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=dmlb2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox