All of lore.kernel.org
 help / color / mirror / Atom feed
From: PGNet Dev <pgnet.dev@gmail.com>
To: roger.pau@citrix.com, xen-devel@lists.xen.org
Cc: boris.ostrovsky@oracle.com
Subject: Re: Clarifying PVH mode requirements
Date: Mon, 1 Feb 2016 04:30:01 -0800	[thread overview]
Message-ID: <56AF4FC9.5050408@gmail.com> (raw)
In-Reply-To: <56AF3336.7040906@citrix.com>

On 02/01/2016 02:28 AM, Roger Pau Monné wrote:
>>      Do any of these^^ params need to also change with the addition of
>>
>>      pvh = 1
>
> Yes, you need to remove builder, xen_platform_pci and
> device_model_version, and add a kernel and ramdisk parameters that point
> to the actual kernel and ramdisk that you want to use. The file should
> look like:

Got it now.  It's a PVH config to start, not an HVM -- different than 
PVHVM ...

>> But checking cpu,
>>
>>      hwinfo --cpu | egrep "Arch|Model"
>>        Arch: X86-64
>>        Model: 6.60.3 "Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz"
>
> You CPU is perfectly capable of running both a PVH Dom0 or DomU, check:
>
> http://ark.intel.com/products/52269/Intel-Xeon-Processor-E3-1220-8M-Cache-3_10-GHz
>
> Look for EPT and VT-d which are the main requirements for PVH.

Clear enough.  Guess it's presumed in 'modern' VT-x; odd that cat 
/proc/cpuinfo provides no indication

  reply	other threads:[~2016-02-01 12:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31 21:27 Clarifying PVH mode requirements PGNet Dev
2016-02-01  3:47 ` PGNet Dev
2016-02-01 10:30   ` Roger Pau Monné
2016-02-01 12:16     ` PGNet Dev
2016-02-01  9:59 ` Wei Liu
2016-02-01 12:23   ` PGNet Dev
2016-02-01 12:29     ` Wei Liu
2016-02-01 12:29     ` Roger Pau Monné
2016-02-01 12:38       ` PGNet Dev
2016-02-01 13:38         ` PGNet Dev
2016-02-01 14:54           ` Boris Ostrovsky
2016-02-01 16:56             ` Jan Beulich
2016-02-01 19:17               ` Boris Ostrovsky
2016-02-02  9:32                 ` Jan Beulich
2016-02-02 15:51             ` Jan Beulich
2016-02-02 16:16               ` PGNet Dev
2016-02-01 10:28 ` Roger Pau Monné
2016-02-01 12:30   ` PGNet Dev [this message]
2016-02-01 14:11   ` Boris Ostrovsky
2016-02-01 15:49     ` PGNet Dev
2016-02-01 19:14       ` Boris Ostrovsky
2016-02-01 19:27         ` PGNet Dev
2016-02-01 19:58           ` Boris Ostrovsky
2016-02-01 23:49             ` Brendan Gregg
2016-02-02 15:28               ` Boris Ostrovsky
2016-02-04 22:01                 ` PGNet Dev
2016-02-04 22:39                   ` Boris Ostrovsky

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=56AF4FC9.5050408@gmail.com \
    --to=pgnet.dev@gmail.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=roger.pau@citrix.com \
    --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.