From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm@vger.kernel.org
Subject: Re: Houston, we have May 15, 1953 (says guest when host uses cpufreq, and dies)
Date: Wed, 18 Feb 2009 17:11:19 +0100 [thread overview]
Message-ID: <499C3327.3090207@wpkg.org> (raw)
In-Reply-To: <499C3131.3030601@codemonkey.ws>
Anthony Liguori schrieb:
> Tomasz Chmielewski wrote:
>> Is using cpufreq (i.e. with ondemand governor) on KVM host safe for
>> guests?
>>
>> I enabled cpufreq on the host, it scaled down the host CPU (Dual-Core
>> AMD Opteron(tm) Processor 2212) to 1 GHz from 2 GHz.
>
> Not with your processor. Intel processors should be fine and any AMD
> processor that's Barcelona/Phenom or newer.
Looks I'm a bad, bad, anti-environment CO2 contributor then.
From a technical perspective, what are the problems with my CPU that it
scales down on the host just fine, but makes the guests "return to the
past"?
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2009-02-18 16:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 14:51 Houston, we have May 15, 1953 (says guest when host uses cpufreq, and dies) Tomasz Chmielewski
2009-02-18 16:02 ` Anthony Liguori
2009-02-18 16:11 ` Tomasz Chmielewski [this message]
2009-02-18 16:59 ` Avi Kivity
2009-02-18 17:02 ` Tomasz Chmielewski
2009-02-18 20:37 ` Anthony Liguori
2009-02-19 9:15 ` Gerd Hoffmann
2009-02-19 9:20 ` Tomasz Chmielewski
2009-02-19 10:27 ` Gerd Hoffmann
2009-02-18 18:46 ` Marcelo Tosatti
2009-02-18 18:53 ` Tomasz Chmielewski
2009-02-18 18:57 ` Marcelo Tosatti
2009-02-18 19:07 ` Tomasz Chmielewski
2009-02-18 19:10 ` Marcelo Tosatti
2009-02-18 19:18 ` Tomasz Chmielewski
2009-02-18 19:32 ` Marcelo Tosatti
2009-02-18 20:02 ` Tomasz Chmielewski
2009-02-18 20:03 ` Marcelo Tosatti
2009-02-19 14:43 ` Tomasz Chmielewski
2009-03-07 14:59 ` Tomasz Chmielewski
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=499C3327.3090207@wpkg.org \
--to=mangoo@wpkg.org \
--cc=anthony@codemonkey.ws \
--cc=kvm@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 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.