From: Marcelo Tosatti <marcelo@kvack.org>
To: Farkas Levente <lfarkas@bppiac.hu>
Cc: Marcelo Tosatti <marcelo@kvack.org>,
Avi Kivity <avi@qumranet.com>,
kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: KVM Test result, KVM62-RC2
Date: Wed, 27 Feb 2008 11:00:13 -0300 [thread overview]
Message-ID: <20080227140013.GA13385@dmt> (raw)
In-Reply-To: <47C53773.8080603@bppiac.hu>
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 don't know details of the problem or why noapic made a difference.
Anyone?
-------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2008-02-27 14:00 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 [this message]
2008-02-27 14:01 ` Avi Kivity
2008-02-27 14:22 ` david ahern
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=20080227140013.GA13385@dmt \
--to=marcelo@kvack.org \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=lfarkas@bppiac.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.