public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jeremy Katz <katzj-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] Match virtual machine processor vendor to that	of the host
Date: Thu, 21 Dec 2006 11:20:00 +0200	[thread overview]
Message-ID: <458A51C0.6020506@qumranet.com> (raw)
In-Reply-To: <1166675645.10717.99.camel-T9xAYgMuJli44ywRPIzf9A@public.gmane.org>

Jeremy Katz wrote:
> Currently, kvm ends up just using the standard qemu cpu initialization.
> This means that all x86_64 virtual machines appear to have an
> AuthenticAMD (AMD64) processor.  This ends up causing a problem when
> booting some x86_64 Linux kernels as they attempt to do AMD64 specific
> initialization for things like performance counters.  Since those MSRs
> aren't supported on the Intel host, the virtual machine is halted.
>
> The attached patch makes it so that we check the actual cpu type of the
> host and then provide the same cpu type for the virtual machine.
>
>   

Windows crashes immediately with this patch (STOP: 0x7E (0xc0000005 
0xF724879C 0xF7A168DC 0xF7A165D8) for those who know how to decode 
BSODs), so either it's doing too much or not enough.

Note that we support migration from Intel to AMD and vice versa, so it 
would be good to supply a command line parameter to set the cpuid (to a 
least common denominator CPU).


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  parent reply	other threads:[~2006-12-21  9:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21  4:34 [PATCH] Match virtual machine processor vendor to that of the host Jeremy Katz
     [not found] ` <1166675645.10717.99.camel-T9xAYgMuJli44ywRPIzf9A@public.gmane.org>
2006-12-21  9:20   ` Avi Kivity [this message]
     [not found]     ` <458A51C0.6020506-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-12-21  9:49       ` Michael Riepe
2006-12-21 14:01       ` Jeremy Katz
     [not found]         ` <1166709696.10717.113.camel-T9xAYgMuJli44ywRPIzf9A@public.gmane.org>
2006-12-21 14:26           ` Avi Kivity
     [not found]             ` <458A99AB.30701-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-12-21 15:49               ` Jeremy Katz
     [not found]                 ` <1166716174.10717.145.camel-T9xAYgMuJli44ywRPIzf9A@public.gmane.org>
2006-12-21 16:16                   ` Avi Kivity
     [not found]                     ` <458AB35A.3060402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-12-24 10:54                       ` Avi Kivity

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=458A51C0.6020506@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=katzj-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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