From: PGNet Dev <pgnet.dev@gmail.com>
To: xen-devel@lists.xen.org
Cc: mukesh.rathor@oracle.com
Subject: Re: Clarifying PVH mode requirements
Date: Sun, 31 Jan 2016 19:47:20 -0800 [thread overview]
Message-ID: <56AED548.2040009@gmail.com> (raw)
In-Reply-To: <56AE7C3B.7010100@gmail.com>
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.
next prev parent reply other threads:[~2016-02-01 3:47 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 [this message]
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=56AED548.2040009@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 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).