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

[David F Barrera <dfbp@xxxxxxxxxx>]

I see a lot of those messages, too, but domU seems stable. (running LTP
at the moment).

(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).




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@xxxxxxxxxxxxxxxxxxxx
> >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@xxxxxxxxxxxxxxxxxxx
> >>http://lists.xensource.com/xen-devel
> >>
> >>    
> >>
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> 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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel