public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Bart Trojanowski <bart@jukie.net>
Cc: linux-kernel@vger.kernel.org, kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-devel] [BUG] 2.6.23.1 host freezes when running kvm
Date: Mon, 22 Oct 2007 15:41:31 +0200	[thread overview]
Message-ID: <471CA88B.7000706@qumranet.com> (raw)
In-Reply-To: <20071022132820.GA3962@jukie.net>

Bart Trojanowski wrote:
> * Avi Kivity <avi@qumranet.com> [071021 07:23]:
>   
>> Does 2.6.23 hang immediately?  If so, these may be two separate problems 
>> and it's worth bisecting to find out what's the fix in 2.6.24-rc.
>>
>> Of course we'll have to address the later hang as well.
>>     
>
> Avi,
>
> it does not hang immediately.  It seems to wait until I go to bed to
> hang -- so it's going to be really fun to rebase.  It could be triggered
> by something that runs off cron in the guest or host.  I am not sure.  
>
> At this point I know that 2.6.23 and 2.6.24-rc0 hung, and 2.6.22.10
> (with kvm-userspace.git) ran overnight.
>
> I will try some of the 23-rc's next.
>   

I'm not sure that's useful -- very little changed after 2.6.23-rc1 (10 
patches).

There were 92 kvm patches in 2.6.23, so a bisect should take about a 
week worst case.


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


  reply	other threads:[~2007-10-22 13:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19 20:20 [BUG] 2.6.23.1 host freezes when running kvm Bart Trojanowski
2007-10-20  0:02 ` Bart Trojanowski
2007-10-20 15:44   ` Bart Trojanowski
2007-10-21 11:22     ` [kvm-devel] " Avi Kivity
2007-10-22 13:28       ` Bart Trojanowski
2007-10-22 13:41         ` Avi Kivity [this message]
2007-10-23 13:54           ` Bart Trojanowski
2007-10-23 14:20             ` Avi Kivity
2007-11-02 17:19               ` Bart Trojanowski
2007-11-04  7:37                 ` Avi Kivity

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=471CA88B.7000706@qumranet.com \
    --to=avi@qumranet.com \
    --cc=bart@jukie.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox