This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] domU can't start, Non-priv warnings

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] domU can't start, Non-priv warnings
From: Andrew Theurer <habanero@xxxxxxxxxx>
Date: Wed, 17 Aug 2005 14:53:04 -0500
Cc: David F Barrera <dfbp@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 17 Aug 2005 19:51:36 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D282BB7@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D282BB7@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.6 (X11/20050716)
Ian Pratt wrote:

Do you not get a couple of lines from Xen imediately preceeding the
crash? Might be worth a debug=y build.

I'll make sure debug=y is on. I also noticed I did not limit this system to 3g (it has 4g). I recall this being a problem recently. I'll limit my memory and try again.

the xen output:

(XEN) (file=traps.c, line=880) Non-priv domain attempted RDMSR(00000000c0000080. (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 000000
(XEN) Domain 2 (vcpu#0) crashed on cpu#3:
(XEN) CPU:    3

BTW, has anyone tried compiling xenU x86_64 kernels with debug on? I error out on, hmm, can't recall the file right now, maybe entry.S. More info on that shortly.



Please could you lookup the symbols for the eip and maybe the first
couple of text addresses on the stack.

I reproduced with a recent pull:

Latest ChangeSet: Wed Aug 17 13:22:18 2005

Looks like we are stuck in xen_l1_entry_update():

void xen_l1_entry_update(pte_t *ptr, pte_t val) {
mmu_update_t u;
u.ptr = virt_to_machine(ptr);
u.val = pte_val_ma(val);
BUG_ON(HYPERVISOR_mmu_update(&u, 1, NULL, DOMID_SELF) < 0); }

...assuming we are hitting the BUG

stack trace:


(XEN) Domain 3 (vcpu#0) crashed on cpu#3:
(XEN) CPU: 3
(XEN) EIP: e033:[<ffffffff8011ee91>] ???
(XEN) EFLAGS: 0000000000000282
(XEN) rax: 00000000ffffffea rbx: ffffffffff578000 rcx:
ffffffff8011ee8d r0
(XEN) rsi: 0000000000000001 rdi: ffffffff80599e90 rbp:
8000000000000067 r8
(XEN) r8: 0000000000000100 r9: 0000000000020000 r10:
0000000000007ff0 r6
(XEN) r12: ffff880001703fd0 r13: ffff880001704bc0 r14:
8000000000000067 r0
(XEN) Guest stack trace from rsp=ffffffff80599e58:
(XEN) ffffffff8011ee8d 0000000000000206 ffffffff8011ee91
000000010000e030 00
(XEN) 8000000000000067 00000000001eb000 ffffffff8011c9aa
0000000000000000 00
(XEN) ffffffff805c226e 0000000000000e00 ffffffff805cab75
0000000000001000 00
(XEN) ffffffff805c22a3 0000000000000e00 ffffffff805c1115
00000000d7c93830 ff
(XEN) ffffffff80103000 ffffffff0000000f 0000000007020800
ffffffff8047cc00 ff
(XEN) ffffffff805ba558 ffffffff80537740 ffffffff805ba193
80108e0000100038 00
(XEN) 0000000000000000 0000000000000000 0000000000000000
0000000000000000 00

Xen-devel mailing list