On 05/30/2016 06:25 AM, Kashyap Chamarthy wrote: > On Thu, May 26, 2016 at 10:55:47AM -0400, Sean Dague wrote: >> On 05/26/2016 05:38 AM, Kashyap Chamarthy wrote: >>> On Wed, May 25, 2016 at 05:42:04PM +0200, Kashyap Chamarthy wrote: >>> >>> [...] >>> >>>> So, in short, the central issue seems to be this: the custom 'gate64' >>>> model is not being trasnalted by libvirt into a model that QEMU can >>>> recognize. >>> >>> An update: >>> >>> Upstream libvirt points out that this turns to be regression, and >>> bisected it to commit (in libvirt Git): 1.2.9-31-g445a09b -- "qemu: >>> Don't compare CPU against host for TCG". >>> >>> So, I expect there's going to be fix pretty soon upstream libvirt. >> >> Which is good... I wonder how long we'll be waiting for that back in our >> distro packages though. > > Yeah, until the fix lands, our current options seem to be: > > (a) Revert to a known good version of libvirt
Downgrading libvirt so dramatically isn't a thing we'll be able to do. > (b) Use nested virt (i.e. <domain type='kvm'>) -- I doubt is possible > on RAX environment, which is using Xen, last I know. We turned off nested virt even where it was enabled, because it locks up at a non trivial rate. So not really an option. > (c) Or a different CPU model Right, although it's not super clear what that will be. -Sean -- Sean Dague http://dague.net __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev