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:16:14 -0800 [thread overview]
Message-ID: <56AF4C8E.8090400@gmail.com> (raw)
In-Reply-To: <56AF33E1.9070606@citrix.com>
On 02/01/2016 02:30 AM, Roger Pau Monné wrote:
> Does your kernel support PVH mode (ie: CONFIG_PVH enabled?)
not CONFIG_PVH, but per http://wiki.xenproject.org/wiki/Linux_PVH
egrep \
"CONFIG_HYPERVISOR_GUEST=|CONFIG_PARAVIRT=|CONFIG_PARAVIRT_GUEST=|CONFIG_PARAVIRT_SPINLOCKS=|CONFIG_XEN=|CONFIG_XEN_PVH="
\
/boot/config-4.4.0-8.g9f68b90-default
CONFIG_HYPERVISOR_GUEST=y
CONFIG_PARAVIRT=y
CONFIG_PARAVIRT_SPINLOCKS=y
CONFIG_XEN=y
CONFIG_XEN_PVH=y
note, there's no 'CONFIG_PARAVIRT_GUEST=', which appears an outdated reqt,
http://marc.info/?l=linux-pm&m=136862383726154&w=2
as CONFIG_PARAVIRT_GUEST was replaced with CONFIG_HYPERVISOR_GUEST
> You will have to post the full boot log (Xen + Linux), there's not
> enough information here to diagnose the issue.
I'll get more detail posted.
next prev parent reply other threads:[~2016-02-01 12:16 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 [this message]
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=56AF4C8E.8090400@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).