From: Andrew Theurer <habanero@us.ibm.com>
To: xen-devel@lists.xensource.com
Subject: domU can't start, Non-priv warnings
Date: Tue, 16 Aug 2005 14:19:58 -0500 [thread overview]
Message-ID: <43023C5E.4070602@us.ibm.com> (raw)
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
next reply other threads:[~2005-08-16 19:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 19:19 Andrew Theurer [this message]
2005-08-16 19:32 ` domU can't start, Non-priv warnings 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
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=43023C5E.4070602@us.ibm.com \
--to=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.