public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: david ahern <daahern@cisco.com>
To: Avi Kivity <avi@qumranet.com>, Marcelo Tosatti <marcelo@kvack.org>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: KVM Test result, KVM62-RC2
Date: Wed, 27 Feb 2008 07:22:32 -0700	[thread overview]
Message-ID: <47C57228.7000507@cisco.com> (raw)
In-Reply-To: <47C56D4D.7090103@qumranet.com>

I'm the 'dsahern' in the bug report (that's my sourceforge login). Per the
thread below yes it is due to networking and as recently as 3 days ago it made a
bit of difference for Arne Kepp with his Centos 5 VM.

david


Avi Kivity wrote:
> Marcelo Tosatti wrote:
>> On Wed, Feb 27, 2008 at 11:12:03AM +0100, Farkas Levente wrote:
>>   
>>>> You can workaround these problems by using a different, less problematic
>>>> clocksource such as acpipm, until the TSC/migration issues are fully
>>>> resolved.
>>>>
>>>> Add "clocksource=acpi_pm" to the kernel options.
>>>>       
>>> than just quck question we use the noapic kernel option for the guest (i
>>> don't remember why but there was some problem without it about half year
>>> ago). do i still have to use the noapic option for the kernel? (i hope
>>> somebody remember the reason:-)
>>>     
>> Apparently dsahern found that the noapic option fixed or alleviated
>> rtl8139 problems under high traffic:
>>
>> https://sourceforge.net/tracker/index.php?func=detail&aid=1802082&group_id=180599&atid=893831
>>
>>   
> 
> I've just run several hours with noapic to confirm.
> 
>> I don't know details of the problem or why noapic made a difference.
>>   
> 
> Seems to point the finger at the ioapic code.  Could be because the load 
> is lower with pic, though.
> 
> I've looked at the ioapic locking and it seems fine.
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-02-27 14:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26  9:20 KVM Test result, KVM62-RC2 Zhao, Yunfeng
2008-02-26  9:44 ` Yang, Sheng
2008-02-26  9:53   ` Avi Kivity
2008-02-26 11:58 ` Farkas Levente
2008-02-26 12:12   ` Izik Eidus
2008-02-26 13:11     ` Farkas Levente
2008-02-26 13:38       ` Farkas Levente
2008-02-27  4:53         ` Marcelo Tosatti
2008-02-27 10:12           ` Farkas Levente
2008-02-27 14:00             ` Marcelo Tosatti
2008-02-27 14:01               ` Avi Kivity
2008-02-27 14:22                 ` david ahern [this message]
2008-03-01 14:05               ` Farkas Levente

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=47C57228.7000507@cisco.com \
    --to=daahern@cisco.com \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=marcelo@kvack.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