On Tue, 17 May 2016 16:42:05 +0300 Oleg Ilyin wrote: > <cpu mode='custom' match='exact'> > <model fallback='allow'>Nehalem</model> > <vendor>Intel</vendor> > <feature policy='require' name='vmx'/> > <feature policy='require' name='lm'/> > <feature policy='require' name='lahf_lm'/> > <feature policy='require' name='nx'/> > <feature policy='require' name='fxsr'/> > <feature policy='require' name='invpcid'/> > </cpu> I use the following CPU configuration with xen & Linux (nested kvm): <cpu mode='custom' match='exact'> <model fallback='allow'>Haswell-noTSX</model> <vendor>Intel</vendor> <topology sockets='1' cores='4' threads='1'/> <feature policy='require' name='abm'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='rdrand'/> <feature policy='require' name='f16c'/> <feature policy='require' name='osxsave'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='tm2'/> <feature policy='require' name='est'/> <feature policy='require' name='smx'/> <feature policy='require' name='vmx'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='monitor'/> <feature policy='require' name='dtes64'/> <feature policy='require' name='pbe'/> <feature policy='require' name='tm'/> <feature policy='require' name='ht'/> <feature policy='require' name='ss'/> <feature policy='require' name='acpi'/> <feature policy='require' name='ds'/> <feature policy='require' name='vme'/> </cpu> I've put it together from various bits I found all over the Internet. The CPU model should be whatever is closest to your host. I would also recommend a newer kernel (Ubuntu 16.04?). -- Mihai Donțu -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
