From mboxrd@z Thu Jan  1 00:00:00 1970
From: PGNet Dev <pgnet.dev@gmail.com>
Subject: Re: Clarifying PVH mode requirements
Date: Sun, 31 Jan 2016 19:47:20 -0800
Message-ID: <56AED548.2040009@gmail.com>
References: <56AE7C3B.7010100@gmail.com>
Reply-To: PGNet Dev <pgnet.dev@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <56AE7C3B.7010100@gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xen.org
Cc: mukesh.rathor@oracle.com
List-Id: xen-devel@lists.xenproject.org

In any case, the !st issue, prior to any guest being launched, simply adding

> @ GRUBG cfg
>
> -    GRUB_CMDLINE_XEN=" ..."
> +    GRUB_CMDLINE_XEN=" dom0pvh ..."

causes boot fail,

...
(XEN) [2016-01-31 19:28:09] d0v0 EPT violation 0x1aa (-w-/r-x) gpa 
0x000000f100054c mfn 0xf15
(XEN) [2016-01-31 19:28:09] d0v0 Walking EPT tables for GFN f1000:
(XEN) [2016-01-31 19:28:09] d0v0  epte 8000000845108107
(XEN) [2016-01-31 19:28:09] d0v0  epte 800000085b680107
(XEN) [2016-01-31 19:28:09] d0v0  epte 8000000844af7107
(XEN) [2016-01-31 19:28:09] d0v0  epte 80500000f1000905
(XEN) [2016-01-31 19:28:09] d0v0  --- GLA 0xffffc900006a254c
(XEN) [2016-01-31 19:28:09] domain_crash called from vmx.c:2685
(XEN) [2016-01-31 19:28:09] Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) [2016-01-31 19:28:09] ----[ Xen-4.6.0_08-405  x86_64  debug=n 
Tainted:    C ]----
(XEN) [2016-01-31 19:28:09] CPU:    0
(XEN) [2016-01-31 19:28:09] RIP:    0010:[<ffffffff8142a4ac>]
(XEN) [2016-01-31 19:28:09] RFLAGS: 0000000000010246   CONTEXT: hvm 
guest (d0v0)
(XEN) [2016-01-31 19:28:09] rax: 000000000000000d   rbx: 
00000000f100054c   rcx: 000000009e9f
(XEN) [2016-01-31 19:28:09] rdx: 0000000000000000   rsi: 
0000000000000100   rdi: ffffffff81e0
(XEN) [2016-01-31 19:28:09] rbp: ffff880164b57908   rsp: 
ffff880164b578d8   r8:  ffff88016d88
(XEN) [2016-01-31 19:28:09] r9:  0000000002400001   r10: 
0000000000000000   r11: 000000000001
(XEN) [2016-01-31 19:28:09] r12: 0000000000000020   r13: 
ffff88016453aec0   r14: ffffc900006c
(XEN) [2016-01-31 19:28:09] r15: ffff880164b57a20   cr0: 
0000000080050033   cr4: 000000000000
(XEN) [2016-01-31 19:28:09] cr3: 0000000001e0b000   cr2: 0000000000000000
(XEN) [2016-01-31 19:28:09] ds: 0000   es: 0000   fs: 0000   gs: 0000 
ss: 0000   cs: 0010
(XEN) [2016-01-31 19:28:09] Guest stack trace from rsp=ffff880164b578d8:
(XEN) [2016-01-31 19:28:09]   Fault while accessing guest memory.
(XEN) [2016-01-31 19:28:09] Hardware Dom0 crashed: rebooting machine in 
5 seconds.
...

Removing the dom0pvh gets me back up & running.