public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Carsten Emde <Carsten.Emde-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org>
To: dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: 2.6.23.1-rt4 and kvm 48
Date: Tue, 06 Nov 2007 10:53:54 +0100	[thread overview]
Message-ID: <473039B2.1010106@osadl.org> (raw)
In-Reply-To: <47302208.2090301-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

Dor,

>>>> I tried to recreate your problem using 2.6.23-1 and latest rt patch 
>>>> (rt5).
>>>> The problem is that the kernel is not stable at all, I can't even
>>>> compile the code over vnc -
>>>> my connection is constantly lost. So it might not be kvm problem?
>>>> Can you try is with -no-kvm and see if it's working - then its just a
>>>> regular userspace process.
>>>> Anyway if all other things are stable on your end, can you send us
>>>> dmesg/strace outputs?
>>> Thanks, Dor, for offering help.
>>> The most recent RT-Preempt patch (2.6.23.1-rt5) still has an SMP issue
>>> which need to be sorted out first.
>>> When a working RT-Preempt patch is available, I will be glad to send
>>> dmesg outputs. We may then share our activities to create the next
>>> "Latest stable" RT-Preempt kernel that includes kvm support.
>> Wow, that smp issue may be a problem I've got a Intel Core 2 cpu with
>> just 2 cores.
>> but I've not seen a dump like this in a while (lustre?).
We see this all the time when we try to run unmodified kvm in an 
rt-kernel, nothing special.

>> I've updated to 2.6.23-rt5 and kvm-50 and I got this dump....
>> [..]
>> BUG: scheduling while atomic: 
>> [..]
>> This loops forever basically...
>> I'm really confused about this one. I've got the full minicom.cap file
>> from the session that produced this its attached zipped up.
>> If you'd like any other information I'd be glad to post it.
No, please not. Our log files are full of it. The "BUG: scheduling while 
atomic" problem is not related to the current SMP issue. It is the 
result of running rt-unaware code in an rt-kernel.

> If the rt patch is not smp stable you can boot with single cpu and run 
> kvm there.
> Maybe just pinning the guest to specific cpu will help although I had 
> troubles with X too.
This does not fix the problem. Save your energy. We live with this 
situation since kvm-28. Please wait until 2.6.23.<x>-rt<y> is stable. 
Thereafter, let's create together a kvm version that works in an 
rt-kernel and let's make sure that from this moment onwards subsequent 
kvm upgrade changes are tested in an rt-kernel before being released.

	--cbe

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  parent reply	other threads:[~2007-11-06  9:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29 14:09 2.6.23.1-rt4 and kvm 48 David Brown
     [not found] ` <9c21eeae0710290709x527cf4fcq52bb410907ff496-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-30  4:18   ` Avi Kivity
     [not found]     ` <4726B088.1010709-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-30  7:38       ` Carsten Emde
     [not found]         ` <4726DF66.4000000-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org>
2007-10-30  9:49           ` Jan Kiszka
     [not found]             ` <4726FE2A.1040607-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org>
2007-10-30 10:02               ` Alexander Graf
2007-10-30 11:07               ` Avi Kivity
     [not found]                 ` <47271057.5040102-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-30 11:34                   ` Jan Kiszka
2007-10-30 11:37                     ` [kvm-devel] " Avi Kivity
2007-11-01  9:28   ` Dor Laor
     [not found]     ` <47299C43.1070703-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-05 20:27       ` Carsten Emde
     [not found]         ` <472F7CA7.8060707-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org>
2007-11-06  5:22           ` David Brown
     [not found]             ` <9c21eeae0711052122y483b06d8ycbcfbfb95fb36663-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-06  8:12               ` Dor Laor
     [not found]                 ` <47302208.2090301-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-06  9:53                   ` Carsten Emde [this message]
     [not found]                     ` <473039B2.1010106-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org>
2007-11-06 14:53                       ` David Brown

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=473039B2.1010106@osadl.org \
    --to=carsten.emde-q945khdl0dbytjvyw6ydsg@public.gmane.org \
    --cc=dor.laor-atKUWr5tajBWk0Htik3J/w@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