public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jiri Kosina <jkosina@suse.cz>, Ingo Molnar <mingo@elte.hu>,
	Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Joerg Roedel <joerg.roedel@amd.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: KVM warning about uncertified CPU for SMP for AMD model 2, stepping 3
Date: Wed, 31 Mar 2010 14:11:57 +0200	[thread overview]
Message-ID: <4BB33C0D.9090808@amd.com> (raw)
In-Reply-To: <20100331024213.GV20695@one.firstfloor.org>

Andi Kleen wrote:
> On Wed, Mar 31, 2010 at 01:03:02AM +0200, Jiri Kosina wrote:
>> Hi,
>>
>> booting 32bit guest on 32bit host on AMD system gives me the following 
>> warning when KVM is instructed to boot as SMP:
> 
> I guess these warnings could be just disabled. With nearly everyone
> using multi-core these days they are kind of obsolete anyways.
Well, the warning refers to an old single-core only CPU model. Most of 
those were able to run in SMP boards, but only a subset of them was 
officially certified to do so (Athlon-MP instead of Athlon-XP).
To avoid complaints about instability of such systems, the warning was 
introduced. If you consider these systems still supported, I wouldn't 
disable this warning, at least the check should be disabled only if the 
hypervisor CPUID bit is set.

But the far better solution is to instruct QEMU/KVM to inject a better 
CPU model (as it was suggested by some people two weeks ago). I am about 
to test various guests with respect to their behavior regarding 
different family/model/stepping settings (one issue is already fixed). 
If this goes well, I will send out the patch to inject the host's CPUID 
F/M/S into the guest by default (which has other advantages, but denies 
migration mostly).

BTW.: I encourage people to test their KVM guests with "-cpu host" (on 
newer QEMUs) and send me any crash logs.

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448-3567-12

  parent reply	other threads:[~2010-03-31 12:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 23:03 KVM warning about uncertified CPU for SMP for AMD model 2, stepping 3 Jiri Kosina
2010-03-30 23:25 ` KVM warning about uncertified CPU for SMP for AMD model 2, stepping3 Brian Jackson
2010-03-31  2:42 ` KVM warning about uncertified CPU for SMP for AMD model 2, stepping 3 Andi Kleen
2010-03-31  8:15   ` [PATCH][RFC] x86: remove SMP check/taint for AMD K7 (was Re: KVM warning about uncertified CPU for SMP for AMD model 2, stepping 3) Jiri Kosina
2010-03-31 12:53     ` Andi Kleen
2010-03-31 12:11   ` Andre Przywara [this message]
2010-03-31 12:51     ` KVM warning about uncertified CPU for SMP for AMD model 2, stepping 3 Andi Kleen
2010-03-31 14:36       ` Pavel Machek
2010-04-25  4:22       ` Yuhong Bao
2010-03-31 13:45     ` Jiri Kosina
2010-03-31 14:39       ` Andre Przywara
2010-03-31 14:45         ` Jiri Kosina

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=4BB33C0D.9090808@amd.com \
    --to=andre.przywara@amd.com \
    --cc=andi@firstfloor.org \
    --cc=avi@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=joerg.roedel@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mtosatti@redhat.com \
    /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