From: Jan Kiszka <jan.kiszka@siemens.com>
To: Carsten Emde <Carsten.Emde@osadl.org>
Cc: Avi Kivity <avi@qumranet.com>,
kvm-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [kvm-devel] 2.6.23.1-rt4 and kvm 48
Date: Tue, 30 Oct 2007 10:49:30 +0100 [thread overview]
Message-ID: <4726FE2A.1040607@siemens.com> (raw)
In-Reply-To: <4726DF66.4000000@osadl.org>
Carsten Emde wrote:
> Avi Kivity wrote:
>> David Brown wrote:
>>> I thought I'd try out the realtime patch set and it didn't work at all
>>> with kvm. The console didn't dump anything and the system completely
>>> locked up.
> Up to now, the unmodified kvm module never worked with any RT kernel.
> This would only change, if RT patched kernels were routinely used in the
> kvm release tests which is, for the time being, not the case.
As far as I understood (but didn't re-test yet), latest kvm release does
include all features required to run over -rt. This was at least the
case for kvm-git I picked up last week and merged into 2.6.23-rt1. The
only issue is that out-of-tree kvm doesn't enable the preemption
notifiers (maybe there were one or two further minor issues, I think to
recall missing smp_ops exports being one, but these were not -rt related).
>
> However, tglx once provided a hand-crafted kvm version that can be used
> together with a selected RT kernel -> see "Latest Stable"
> (http://www.osadl.org/Latest-Stable.latest-stable-realtime-kernel.0.html)
> realtime kernel. It is based on kernel 2.6.21.6-rt21 and kvm-28.
>
> We used these modules to carry out a number of "proof of concept" tests
> which were very successful. The realtime capabilities of the host system
> remained unchanged irrespective of whether the kvm guest system (no
> graphics) was running or not. This was even the case while the guest
> system was booting.
Interesting result - you've read about the wbinvd issues? Is there no
wbinvd in the bios shipped with older kvm? Which VM extension did you
test, both Intel and AMD? I would bet that your X issues are due to the
same effect. X startup/shutdown involves a lot of wbinvd calls on my
test boxes.
To sum up my findings: kvm over whatever RT kernel is risky
(latency-wise) unless you can audit or even para-virtualise your guest
OS /wrt wbinvd. Maybe we can discuss this also in Linz by the end of the
week. :)
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2007-10-30 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 14:09 2.6.23.1-rt4 and kvm 48 David Brown
2007-10-30 4:18 ` [kvm-devel] " Avi Kivity
2007-10-30 7:38 ` Carsten Emde
2007-10-30 9:49 ` Jan Kiszka [this message]
2007-10-30 10:02 ` Alexander Graf
2007-10-30 11:07 ` Avi Kivity
2007-10-30 11:34 ` Jan Kiszka
2007-10-30 11:37 ` Avi Kivity
2007-11-01 9:28 ` Dor Laor
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=4726FE2A.1040607@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Carsten.Emde@osadl.org \
--cc=avi@qumranet.com \
--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