From: Laurent Vivier <Laurent.Vivier@bull.net>
To: carsteno@de.ibm.com
Cc: "kvm-devel@lists.sourceforge.net"
<kvm-devel@lists.sourceforge.net>,
Linux-kernel@vger.kernel.org,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [kvm-devel] severe bug in 2.6.23+ kvm.git
Date: Fri, 19 Oct 2007 13:53:55 +0200 [thread overview]
Message-ID: <47189AD3.8010301@bull.net> (raw)
In-Reply-To: <471899CA.8060206@de.ibm.com>
Carsten Otte a écrit :
> Laurent Vivier wrote:
>> How do you know the problem has been introduced by kvm ?
> I don't. In fact I think it has not been introduced by kvm. All I
> stated, is that we experienced the problem when running the kvm.git
> kernel after the 2.6.23 update that has not been present in the
> kvm.git -rc8 as of last thursday.
Perhaps 2.6.23.1 corrects this ?
http://lkml.org/lkml/2007/10/12/302
Laurent
--
---------------- Laurent.Vivier@bull.net -----------------
"Given enough eyeballs, all bugs are shallow" E. S. Raymond
next prev parent reply other threads:[~2007-10-19 11:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 11:22 severe bug in 2.6.23+ kvm.git Carsten Otte
2007-10-19 11:31 ` [kvm-devel] " Aurelien Jarno
2007-10-19 11:37 ` Carsten Otte
2007-10-19 11:42 ` Laurent Vivier
2007-10-19 11:49 ` Carsten Otte
2007-10-19 11:53 ` Laurent Vivier [this message]
2007-10-19 11:58 ` Christian Borntraeger
2007-10-19 11:57 ` Mike Lampard
2007-10-19 12:21 ` Carsten Otte
2007-10-19 13:44 ` Carsten Otte
2007-10-19 14:18 ` Jan Engelhardt
2007-10-19 14:48 ` Christian Borntraeger
2007-10-19 14:57 ` Laurent Vivier
2007-10-19 15:23 ` Christian Borntraeger
2007-10-19 15:43 ` Luca Tettamanti
2007-10-19 18:49 ` Christian Borntraeger
2007-10-19 11:55 ` Carsten Otte
2007-10-19 15:13 ` [kvm-devel] " Avi Kivity
2007-10-22 10:57 ` Carsten Otte
2007-10-22 11:48 ` Avi Kivity
2007-10-22 13:14 ` Carsten Otte
2007-10-22 14:00 ` Carsten Otte
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=47189AD3.8010301@bull.net \
--to=laurent.vivier@bull.net \
--cc=Linux-kernel@vger.kernel.org \
--cc=aurelien@aurel32.net \
--cc=carsteno@de.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
/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