From: Olaf Hering <olaf@aepfle.de>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: Jan Beulich <JBeulich@suse.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Alex Bligh <alex@alex.org.uk>,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: Question re live migrate on Xen 4.2 re different cpu capabilities
Date: Mon, 11 Feb 2013 17:18:00 +0100 [thread overview]
Message-ID: <20130211161800.GA15788@aepfle.de> (raw)
In-Reply-To: <CACJDEmpQXeCaSgNWhZCdcEZotsUkQHJHUEVm2G=edsgaaL92AA@mail.gmail.com>
On Fri, Feb 08, Konrad Rzeszutek Wilk wrote:
> I recall seeing that libvirt had some of this figured out. It would
> know which CPUID flags each CPU family had - and you could actually
> set ('I am a Westmere CPU') or it would use the lowest common CPU
> family support for all the guest.
>
> Granted that means you need to know _which_ of the machines has the
> lowest common CPU family first. Or you set the guest to say 'Core' .
>
> Anyhow, perhaps looking at libvirt and implementing something similar
> in 'xl' would be beneficial for these issues?
I havent looked at the code, but I can imagine it does that via qemu.
But it would be nice thing to have proper cpuid= handling were libvirt
can force a certain cpu type.
Olaf
next prev parent reply other threads:[~2013-02-11 16:18 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
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 [this message]
-- 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=20130211161800.GA15788@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=alex@alex.org.uk \
--cc=konrad@kernel.org \
--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.