From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Christoph Egger <Christoph.Egger@amd.com>,
Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen HVM cpuid problem
Date: Tue, 13 May 2008 13:56:00 +0100 [thread overview]
Message-ID: <C44F4E70.20A5D%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <200805131441.05576.Christoph.Egger@amd.com>
All HVM guests receive a default configuration from libxc's
xc_cpuid_apply_policy(). You must update your tools if you have updated your
hypervisor to recent xen-unstable. Otherwise you will indeed get bogus CPUID
behaviour.
-- Keir
On 13/5/08 13:41, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
>
> Hi Keir,
>
> For HVM guests, all cpuid Fn's going through domain_cpuid()
> iterate over the loop and then return 0 for all four registers.
>
> Guests OS's and cpuid tools in HVM which query for
> cpuid Fn 0000.0000 %eax and 8000.0000 %eax, see the value 0 and think,
> Xen emulates oldish 386/486 CPUs.
>
> This leads to strange boot failures, "your CPU does not support long mode"
> or "minimum required CPU is a 486DX CPU" when launching 32bit or 64bit HVM
> guests.
>
> To reproduce this, cpuid is NOT explicitely configured
> in the guest config file.
>
> BTW: Is there a reason for not handling cpuid in one central place?
>
> Christoph
>
next prev parent reply other threads:[~2008-05-13 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 12:41 Xen HVM cpuid problem Christoph Egger
2008-05-13 12:53 ` Jean Guyader
2008-05-13 12:56 ` Keir Fraser [this message]
2008-05-13 13:49 ` Christoph Egger
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=C44F4E70.20A5D%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Christoph.Egger@amd.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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 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.