From: PGNet Dev <pgnet.dev@gmail.com>
To: xen-devel@lists.xen.org
Cc: mukesh.rathor@oracle.com
Subject: Clarifying PVH mode requirements
Date: Sun, 31 Jan 2016 13:27:23 -0800 [thread overview]
Message-ID: <56AE7C3B.7010100@gmail.com> (raw)
I run Xen 4.6 Dom0
rpm -qa | egrep -i "kernel-default-4|xen-4"
kernel-default-devel-4.4.0-8.1.g9f68b90.x86_64
xen-4.6.0_08-405.1.x86_64
My guests are currently HVM in PVHVM mode; I'm exploring PVH.
IIUC, for 4.6, this doc
http://xenbits.xen.org/docs/4.6-testing/misc/pvh-readme.txt
instructs the following necessary changes:
@ GRUBG cfg
- GRUB_CMDLINE_XEN=" ..."
+ GRUB_CMDLINE_XEN=" dom0pvh ..."
&, @ guest.cfg
+ pvh = 1
For my guest.cfg, currently in PVHVM mode, I have
builder = 'hvm'
xen_platform_pci = 1
device_model_version="qemu-xen"
hap = 1
...
Q:
Do any of these^^ params need to also change with the addition of
pvh = 1
> At the moment HAP is required for PVH.
As above, I've 'hap = 1' enabled.
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"
neither 'hap' nor 'emt' are specifically called out,
egrep -wo 'vmx|lm|aes' /proc/cpuinfo | sort | uniq \
| sed -e 's/aes/Hardware encryption=Yes (&)/g' \
-e 's/lm/64 bit cpu=Yes (&)/g' -e 's/vmx/Intel hardware
virtualization=Yes (&)/g'
Hardware encryption=Yes (aes)
64 bit cpu=Yes (lm)
egrep -wo 'hap|vmx|ept|vpid|npt|tpr_shadow|flexpriority|vnmi|lm|aes'
/proc/cpuinfo | sort | uniq
aes
lm
Iiuc, Intel introduced EPT with Nehalem arch, which preceds Haswell by ~
5 years.
Q:
Am I out of luck re: PVH with more modern Haswell? Or is there a
different check I should be running ?
> At present the only PVH guest is an x86 64bit PV linux.
Is this still current/true info?
next reply other threads:[~2016-01-31 21:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 21:27 PGNet Dev [this message]
2016-02-01 3:47 ` Clarifying PVH mode requirements 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
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=56AE7C3B.7010100@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=mukesh.rathor@oracle.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.