From: Olaf Hering <olaf@aepfle.de>
To: Alex Bligh <alex@alex.org.uk>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: Question re live migrate on Xen 4.2 re different cpu capabilities
Date: Thu, 7 Feb 2013 16:11:26 +0100 [thread overview]
Message-ID: <20130207151126.GA31180@aepfle.de> (raw)
In-Reply-To: <496E7A8DB9DCF257D29E10F2@nimrod.local>
On Thu, Feb 07, Alex Bligh wrote:
> >You can also level down an entire host using the cpuid_mask_* command
> >line options described in
> >http://xenbits.xen.org/docs/unstable/misc/xen-command-line.html
>
> Thanks - that's really helpful. Looking at the documentation for cpuid=
> I can't see an obvious way of saying 'mask everything except the
> least common denominator of features' using the libxl method, without
> having prior knowledge of what each version of xen supports. I'm not
> even clear how to do this on the xend method (obviously I want to
> pass long bitstrings of zeros, but how many?). Am I missing something?
cpuid= is what the guest sees, so its not so much a feature of Xen
itself but what the host cpu provides. I'm not sure if Xen can emulate
certain important bits. The wikipedia CPUID entry has a list what each
bit means.
Olaf
next prev parent reply other threads:[~2013-02-07 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 9:08 Question re live migrate on Xen 4.2 re different cpu capabilities Alex Bligh
2013-02-07 9:19 ` Olaf Hering
2013-02-07 9:47 ` Ian Campbell
2013-02-07 10:59 ` Alex Bligh
2013-02-07 15:11 ` Olaf Hering [this message]
2013-02-07 15:59 ` Alex Bligh
2013-02-07 16:16 ` Ian Campbell
2013-02-07 16:59 ` Alex Bligh
2013-02-07 16:19 ` Jan Beulich
2013-02-07 16:59 ` Alex Bligh
2013-02-08 13:36 ` Olaf Hering
2013-02-08 20:04 ` Konrad Rzeszutek Wilk
2013-02-11 16:18 ` Olaf Hering
-- strict thread matches above, loose matches on Subject: below --
2013-02-07 9:07 Alex Bligh
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=20130207151126.GA31180@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=alex@alex.org.uk \
--cc=xen-devel@lists.xen.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.