xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "James Harper" <james.harper@bendigoit.com.au>
To: MaoXiaoyun <tinnycloud@hotmail.com>,
	xen devel <xen-devel@lists.xensource.com>
Subject: RE: A simple question of CPU emulation in Xen
Date: Sat, 14 May 2011 09:41:39 +1000	[thread overview]
Message-ID: <AEC6C66638C05B468B556EA548C1A77D01D5706D@trantor> (raw)
In-Reply-To: <BLU157-w314A18AF1F667FC0BE4DD3DA880@phx.gbl>

> Hi :
> 
>      I have a simple question on CPU emulation in Xen.
> 
>     Currently, inside guest, we can see that the CPU information
incluing
> types and frequency is exactly
> same as physical CPU. Is it possible for Xen(or qemu) to emulate a
different
> type of CPU. That is inside
> guest, we see a different CPU types?
> 
>     If it is possible, could someone elighten me where to start.
> 

Do you want to emulate a completely different platform (eg PPC / alpha /
Sparc) or just pretend the cpu is a slightly different flavours (eg
running a late model Xeon CPU but emulate a P2)?

In a lot of cases you can do the latter by changing some CPUID values in
the DomU config to mask the CPU features so the guest thinks it is
running on an older model.

James

  parent reply	other threads:[~2011-05-13 23:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <COL0-MC1-F16ijYRq7A00088f57@col0-mc1-f16.Col0.hotmail.com>
2011-05-13 14:41 ` A simple question of CPU emulation in Xen MaoXiaoyun
2011-05-13 14:51   ` Alan Cox
2011-05-13 17:39     ` Dan Magenheimer
2011-05-13 23:41   ` James Harper [this message]
2011-05-15 16:48     ` hotmaim
2011-05-16  1:46       ` James Harper
2011-05-16  2:11         ` MaoXiaoyun
2011-05-16  8:04         ` Ian Campbell
2011-05-19  2:15           ` MaoXiaoyun
2011-05-19  6:21             ` Ian Campbell

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=AEC6C66638C05B468B556EA548C1A77D01D5706D@trantor \
    --to=james.harper@bendigoit.com.au \
    --cc=tinnycloud@hotmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).