From: David F Barrera <dfbp@us.ibm.com>
To: Andrew Theurer <habanero@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: domU can't start, Non-priv warnings
Date: Tue, 16 Aug 2005 16:59:09 -0500 [thread overview]
Message-ID: <1124229549.6363.1.camel@localhost.localdomain> (raw)
In-Reply-To: <43025990.6010402@us.ibm.com>
I am seeing these messages on the serial console; should I be concerned
about them. They don't seem innocuous enough:
(XEN) (file=traps.c, line=880) Non-priv domain attempted RDMSR
(00000000c0000080,00020000,00020000).
(XEN) (file=traps.c, line=872) Non-priv domain attempted WRMSR
(00000000c0000100,00000000,00000000).
(XEN) (file=traps.c, line=872) Non-priv domain attempted WRMSR
(00000000c0000102,00000000,00000000).
(XEN) (file=traps.c, line=880) Non-priv domain attempted RDMSR
(00000000c0000080,00000000,00000000).
(XEN) (file=mm.c, line=2467) PTE entry 3f4a4067 for address
ffffc20000035000 doesn't match frame 3f4ad
(XEN) (file=grant_table.c, line=1086) Grant unref rd(1) ld(0) frm(3f4a4)
flgs(0).
(XEN) (file=traps.c, line=880) Non-priv domain attempted RDMSR
(00000000c0000080,00020000,00020000).
(XEN) (file=traps.c, line=872) Non-priv domain attempted WRMSR
(00000000c0000100,00000000,00000000).
(XEN) (file=traps.c, line=872) Non-priv domain attempted WRMSR
(00000000c0000102,00000000,00000000).
(XEN) (file=traps.c, line=880) Non-priv domain attempted RDMSR
(00000000c0000080,00000000,00000000).
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 000000c0
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 0000009f
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 000000c0
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 0000009f
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 000000c0
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 0000009f
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 000000c0
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 0000009f
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 000000c0
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 0000009f
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 000000c0
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 0000009f
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 000000c0
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 0000009f
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 000000c0
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 0000009f
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM1: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 000000c0
On Tue, 2005-08-16 at 16:24 -0500, Andrew Theurer wrote:
> David F Barrera wrote:
>
> >I was able to boot domU on 3 EMT64T machines, SLES 9 SP2 based.
> >
> >
>
> I seem to have problems on that changeset:
>
> (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
> (XEN) EIP: e033:[<ffffffff8011ee11>] ???
> (XEN) EFLAGS: 0000000000000282
> (XEN) rax: 00000000ffffffea rbx: ffffffffff578000 rcx:
> ffffffff8011ee0d 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) ffffffff8011ee0d 0000000000000206 ffffffff8011ee11
> 000000010000e030 00
> (XEN) 8000000000000067 0000000000fc1000 ffffffff8011c91a
> 0000000000000000 00
> (XEN) ffffffff805c21fe 0000000000000e00 ffffffff805cab05
> 0000000000001000 00
> (XEN) ffffffff805c2233 0000000000000e00 ffffffff805c10a5
> 0000000004a93830 ff
> (XEN) ffffffff80103000 ffffffff0000000f 0000000007020800
> ffffffff8047cb00 ff
> (XEN) ffffffff805ba558 ffffffff80537c40 ffffffff805ba193
> 80108e0000100038 00
> (XEN) 0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 00
>
> >changeset: 6192:3d187585c1415fbb14cb285cc71e0ff0faf81e67
> >tag: tip
> >user: kaf24@firebug.cl.cam.ac.uk
> >date: Tue Aug 16 06:20:47 2005
> >summary: Use a SWIOTLB to use pre-reserved bounce buffers for high
> >memory
> >
> >On Tue, 2005-08-16 at 14:19 -0500, Andrew Theurer wrote:
> >
> >
> >>Can't seem to fully boot a domU on either EM64T or Opteron with x86_64
> >>xen-unstable. Both systems' report this from xen:
> >>
> >>(XEN) (file=traps.c, line=872) Non-priv domain attempted
> >>WRMSR(00000000c0000100.
> >>(XEN) (file=traps.c, line=872) Non-priv domain attempted
> >>WRMSR(00000000c0000102.
> >>(XEN) (file=traps.c, line=880) Non-priv domain attempted
> >>RDMSR(00000000c0000080.
> >>
> >>They boot partially, ending with:
> >>
> >>xen_mem: Initialising balloon driver.
> >>Grant table initialized
> >>IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
> >>audit: initializing netlink socket (disabled)
> >>audit(1124251914.348:0): initialized
> >>VFS: Disk quotas dquot_6.5.1
> >>Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> >>
> >>
> >>This is with the default kernel configs xen-unstable provides. NX is
> >>enabled on the EM64T. I could not find a similar BIOS option for
> >>Opteron. Even through they are "stuck", cpu time for these domains
> >>increments steadily. Any ideas?
> >>
> >>-Andrew
> >>
> >>_______________________________________________
> >>Xen-devel mailing list
> >>Xen-devel@lists.xensource.com
> >>http://lists.xensource.com/xen-devel
> >>
> >>
> >>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
next prev parent reply other threads:[~2005-08-16 21:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 19:19 domU can't start, Non-priv warnings Andrew Theurer
2005-08-16 19:32 ` Jerone Young
2005-08-16 19:45 ` Keir Fraser
2005-08-16 19:56 ` Andrew Theurer
2005-08-16 20:02 ` Jerone Young
2005-08-16 20:01 ` David F Barrera
2005-08-16 21:24 ` Andrew Theurer
2005-08-16 21:53 ` David F Barrera
2005-08-16 21:52 ` Keir Fraser
2005-08-16 21:59 ` David F Barrera [this message]
2005-08-16 22:14 ` Keir Fraser
2005-08-17 16:54 ` David F Barrera
-- strict thread matches above, loose matches on Subject: below --
2005-08-16 20:23 Nakajima, Jun
2005-08-16 21:32 Ian Pratt
2005-08-17 19:35 ` Andrew Theurer
2005-08-17 7:41 Petersson, Mats
2005-08-17 11:59 ` Jerone Young
2005-08-17 17:13 ` Jerone Young
2005-08-17 19:39 Ian Pratt
2005-08-17 19:53 ` Andrew Theurer
2005-08-17 19:58 ` Chris Wright
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=1124229549.6363.1.camel@localhost.localdomain \
--to=dfbp@us.ibm.com \
--cc=habanero@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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.