qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gerhard Wiesinger <lists@wiesinger.com>
Cc: Mulyadi Santosa <mulyadi.santosa@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Problem with QEMU on KVM
Date: Mon, 19 Apr 2010 12:39:00 +0200	[thread overview]
Message-ID: <4BCC32C4.9000701@siemens.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1004190842190.16477@bbs.intern>

Gerhard Wiesinger wrote:
> On Tue, 13 Apr 2010, Jan Kiszka wrote:
> 
>> Mulyadi Santosa wrote:
>>> Hi Jamie...
>>>
>>> On Mon, Apr 12, 2010 at 19:07, Jamie Lokier <jamie@shareable.org> wrote:
>>>> There are various -no-kvm-XXX options to try:
>>>>
>>>> -no-kvm-irqchip disable KVM kernel mode PIC/IOAPIC/LAPIC
>>>> -no-kvm-pit     disable KVM kernel mode PIT
>>>> -no-kvm-pit-reinjection disable KVM kernel mode PIT interrupt reinjection
>>> I try to read the source code without too much luck understanding the
>>> meaning of the above parameters, especially the reinjection. Please
>>> CMIIW, interrupt reinjection is a way to handle lost ticks, right?
>> Those switches only exist in the qemu-kvm branch. The fact that
>> -enable-kvm has some effect for you makes me think that you tried
>> upstream KVM support (ie. the one that comes with vanilla QEMU), right?
>>
> 
> I tried 0.12.3 stable and also qemu git master:
> http://git.savannah.gnu.org/cgit/qemu.git/log/
> 
>> It would be interesting to check if you can reproduce the problem also
>> with qemu-kvm(-0.12.3 or git head). As you may also face an issue of the
>> kvm kernel bits, it would be furthermore helpful to check with the
>> latest kernel from kvm.git or the modules build via kvm-kmod as well.
> 
> Can you please post links to the different git repositories, since a lot 
> of different repositories exist here (qemu-kvm and kernel).

http://www.linux-kvm.org/page/Code

HTH,
Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2010-04-19 10:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-10 20:09 [Qemu-devel] Problem with QEMU on KVM Gerhard Wiesinger
2010-04-11 10:19 ` Mulyadi Santosa
2010-04-11 13:52   ` Gerhard Wiesinger
2010-04-12  9:16     ` Mulyadi Santosa
2010-04-12 12:07       ` Jamie Lokier
2010-04-13  0:28         ` Mulyadi Santosa
2010-04-13 16:32           ` [Qemu-devel] " Jan Kiszka
2010-04-19  6:45             ` Gerhard Wiesinger
2010-04-19 10:39               ` Jan Kiszka [this message]
2010-04-13 19:38         ` [Qemu-devel] " Gerhard Wiesinger
2010-04-19 18:37 ` Gerhard Wiesinger
2010-04-21  0:36   ` Jamie Lokier
2010-04-21 18:20     ` Gerhard Wiesinger
2010-04-22 10:47       ` Gerd Hoffmann
2010-04-23 19:50         ` Gerhard Wiesinger
2010-04-24  6:58           ` Gerhard Wiesinger
2010-05-04  5:09             ` Gerhard Wiesinger
2010-05-04 13:32               ` Anthony Liguori
2010-05-04 21:30                 ` [Qemu-devel] Problem with QEMU / KVM K D

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=4BCC32C4.9000701@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=lists@wiesinger.com \
    --cc=mulyadi.santosa@gmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).