public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mihai Donțu" <mihai.dontu@gmail.com>
To: Oleg Ilyin <on.ilyin@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: ESXi under KVM
Date: Tue, 17 May 2016 17:07:04 +0300	[thread overview]
Message-ID: <20160517170704.7844cfc7@mdontu-l> (raw)
In-Reply-To: <CANLWoXptxUgtL+TcN_C4hdcgS=pimw2XyDH6Ku9YLX4fExGbmw@mail.gmail.com>

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

  reply	other threads:[~2016-05-17 14:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 13:42 ESXi under KVM Oleg Ilyin
2016-05-17 14:07 ` Mihai Donțu [this message]
2016-05-17 16:47 ` Bandan Das

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=20160517170704.7844cfc7@mdontu-l \
    --to=mihai.dontu@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=on.ilyin@gmail.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