From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: xen-devel <xen-devel@lists.xen.org>
Subject: PVH guess crash with memory < maxmem
Date: Mon, 8 Aug 2016 12:40:16 +0200 [thread overview]
Message-ID: <20160808104016.GA5701@mail-itl> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1762 bytes --]
Hi,
I'm having troubles with starting PVH guest when memory < maxmem. Exact
crash message:
(XEN) d2v0 EPT violation 0x182 (-w-/---) gpa 0x0000003e7ff000
mfn 0xffffffffffffffff type 4
(XEN) d2v0 Walking EPT tables for GFN 3e7ff:
(XEN) d2v0 gfn exceeds max_mapped_pfn 19000
(XEN) d2v0 --- GLA 0xffff88003e7ff000
(XEN) domain_crash called from vmx.c:3022
(XEN) Domain 2 (vcpu#0) crashed on cpu#2:
(XEN) ----[ Xen-4.7.0 x86_64 debug=n Not tainted ]----
(XEN) CPU: 2
(XEN) RIP: 0010:[<ffffffff813b4d62>]
(XEN) RFLAGS: 0000000000010016 CONTEXT: hvm guest (d2v0)
(XEN) rax: 0000000000000000 rbx: 0000000000000001 rcx: 000000000000003f
(XEN) rdx: 000000003e7ff000 rsi: 0000000002b96000 rdi: ffff88003e7ff000
(XEN) rbp: ffffffff81c03b68 rsp: ffffffff81c03b40 r8: 0000000000000200
(XEN) r9: 0000000000000000 r10: 0000000002b96000 r11: 0000000000000000
(XEN) r12: 0000000000000001 r13: 000000000003e7ff r14: ffff880000000000
(XEN) r15: ffff880001c10828 cr0: 0000000080050033 cr4: 0000000000000020
(XEN) cr3: 0000000001c0e000 cr2: 0000000000000000
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: 0010
(XEN) Guest stack trace from rsp=ffffffff81c03b40:
(XEN) Fault while accessing guest memory.
Guest kernel: 4.1.13, guest config attached.
Is there any way around it, or such configuration isn't supported yet?
Or maybe it is possible to increase maxmem later using some trick
(memory hotplug or something)?
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.1.2: pvhtest.cfg --]
[-- Type: text/plain, Size: 703 bytes --]
name = "pvhtest"
uuid = "ac823572-853b-4c8c-ba77-47aa515ccd63"
maxmem = 400
memory = 1000
pvh = 1
vcpus = 4
localtime = 0
on_poweroff = "destroy"
on_reboot = "destroy"
on_crash = "destroy"
kernel = "/var/lib/qubes/vm-kernels/4.1.13-6/vmlinuz"
ramdisk = "/var/lib/qubes/vm-kernels/4.1.13-6/initramfs"
extra = "root=/dev/mapper/dmroot ro nomodeset console=hvc0 rd_NO_PLYMOUTH 3 nopat"
disk = [ "/var/lib/qubes/vm-templates/fedora-23-clone/root.img,raw,xvda,r,backendtype=phy",
"/var/lib/qubes/appvms/pvhtest/private.img,raw,xvdb,w,backendtype=phy",
"/var/lib/qubes/appvms/pvhtest/volatile.img,raw,xvdc,w,backendtype=phy",
"/var/lib/qubes/vm-kernels/4.1.13-6/modules.img,raw,xvdd,r,backendtype=phy" ]
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-08-08 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 10:40 Marek Marczykowski-Górecki [this message]
2016-08-08 11:38 ` PVH guess crash with memory < maxmem Jan Beulich
2016-08-08 12:14 ` Marek Marczykowski-Górecki
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=20160808104016.GA5701@mail-itl \
--to=marmarek@invisiblethingslab.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.