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
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?Checking it out...looks like Xen is pretty screwed on Opteron machines at the moment (at least on my dual Opteron workstation). There seems to be some timer issue...takes forever fro the machine to boot up. Oh..AMD does not have an option for the NX bit...the cpu always can understand it.> > -Andrew > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >-- Jerone Young IBM Linux Technology Center jyoung5@us.ibm.com 512-838-1157 (T/L: 678-1157) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 16 Aug 2005, at 20:19, Andrew Theurer wrote:> 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?Probably getting stuck in a page-fault loop. We also have observed this probnlem but haven;t narrowed down what changeset causes the problem. We think it''s one from sometime last week though (before the weekend). If you can give info on the last changeset that works for you, that would be very useful. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser wrote:> > On 16 Aug 2005, at 20:19, Andrew Theurer wrote: > >> 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? > > > Probably getting stuck in a page-fault loop. We also have observed > this probnlem but haven;t narrowed down what changeset causes the > problem. We think it''s one from sometime last week though (before the > weekend). If you can give info on the last changeset that works for > you, that would be very useful.This is the first time I have tried domU''s for x86_64, but I''ll jump back a week and do a binary search. -Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
David F Barrera
2005-Aug-16 20:01 UTC
Re: [Xen-devel] domU can''t start, Non-priv warnings
I was able to boot domU on 3 EMT64T machines, SLES 9 SP2 based. 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 >-- 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@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, 2005-08-16 at 20:45 +0100, Keir Fraser wrote:> On 16 Aug 2005, at 20:19, Andrew Theurer wrote: > > > 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? > > Probably getting stuck in a page-fault loop. We also have observed this > probnlem but haven;t narrowed down what changeset causes the problem. > We think it''s one from sometime last week though (before the weekend). > If you can give info on the last changeset that works for you, that > would be very useful.I''ll take sometime tonight & go through the changesets & see if I can narrow it down further.> > -- Keir > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >-- Jerone Young IBM Linux Technology Center jyoung5@us.ibm.com 512-838-1157 (T/L: 678-1157) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Try to remove the network stuff. The warnings are harmless. I''ve got domU working at least yesterday, seeing the warnings. Jun --- Intel Open Source Technology Center Jerone Young wrote:> On Tue, 2005-08-16 at 20:45 +0100, Keir Fraser wrote: >> On 16 Aug 2005, at 20:19, Andrew Theurer wrote: >> >>> 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? >> >> Probably getting stuck in a page-fault loop. We also have observed >> this probnlem but haven;t narrowed down what changeset causes the >> problem. We think it''s one from sometime last week though (before >> the weekend). If you can give info on the last changeset that works >> for you, that would be very useful. > I''ll take sometime tonight & go through the changesets & see if I can > narrow it down further. >> >> -- Keir >> >> >> _______________________________________________ >> 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
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
Please could you lookup the symbols for the eip and maybe the first couple of text addresses on the stack. Thanks, Ian> -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of > Andrew Theurer > Sent: 16 August 2005 22:25 > To: David F Barrera > Cc: xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] domU can''t start, Non-priv warnings > > 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 >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 16 Aug 2005, at 22:53, David F Barrera wrote:> I see a lot of those messages, too, but domU seems stable. (running LTP > at the moment).We have verbose on by default now, probably just until things get more stabilised. Then we can turn it off again. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
David F Barrera
2005-Aug-16 21:53 UTC
Re: [Xen-devel] domU can''t start, Non-priv warnings
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@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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
David F Barrera
2005-Aug-16 21:59 UTC
Re: [Xen-devel] domU can''t start, Non-priv warnings
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 16 Aug 2005, at 22:59, David F Barrera wrote:> I am seeing these messages on the serial console; should I be concerned > about them. They don''t seem innocuous enough:They''re all innocuous, except the one in the middle which is a grant-reference unmap request failing. Not sure what''s going on there. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Petersson, Mats
2005-Aug-17 07:41 UTC
RE: [Xen-devel] domU can''t start, Non-priv warnings
> -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of > Jerone Young > Sent: 16 August 2005 20:33 > To: Andrew Theurer > Cc: xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] domU can''t start, Non-priv warnings > > 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? > > Checking it out...looks like Xen is pretty screwed on Opteron > machines at the moment (at least on my dual Opteron > workstation). There seems to be some timer issue...takes > forever fro the machine to boot up. > > Oh..AMD does not have an option for the NX bit...the cpu > always can understand it.That is incorrect. AMD''s 64-bit processors use NXE, bit 11, in EFER (MSR 0xC0000080) to determine if NX is "in use" or not. However, I''m not aware of any way to disable the ability to set this bit in the MSR, if that''s what you mean by "AMD does not have an option for the NX bit". -- Mats> > > > -Andrew > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > > -- > Jerone Young > IBM Linux Technology Center > jyoung5@us.ibm.com > 512-838-1157 (T/L: 678-1157) > > > _______________________________________________ > 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
On 8/17/05, Petersson, Mats <mats.petersson@amd.com> wrote:> > > > -----Original Message----- > > From: xen-devel-bounces@lists.xensource.com > > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of > > Jerone Young > > Sent: 16 August 2005 20:33 > > To: Andrew Theurer > > Cc: xen-devel@lists.xensource.com > > Subject: Re: [Xen-devel] domU can''t start, Non-priv warnings > > > > 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? > > > > Checking it out...looks like Xen is pretty screwed on Opteron > > machines at the moment (at least on my dual Opteron > > workstation). There seems to be some timer issue...takes > > forever fro the machine to boot up. > > > > Oh..AMD does not have an option for the NX bit...the cpu > > always can understand it. > > That is incorrect. AMD''s 64-bit processors use NXE, bit 11, in EFER (MSR > 0xC0000080) to determine if NX is "in use" or not.You apparently miss understand this. Intel CPUs have an option in the bios where if bit 11 is set it has no idea what to do with it. Where as on AMD 64-bit CPUs if bit 11 is set then it always does. My big complaint is why Intel made this possible in the first place.> However, I''m not aware of any way to disable the ability to set this bit > in the MSR, if that''s what you mean by "AMD does not have an option for > the NX bit". > > -- > Mats > > > > > > -Andrew > > > > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.xensource.com > > > http://lists.xensource.com/xen-devel > > > > > -- > > Jerone Young > > IBM Linux Technology Center > > jyoung5@us.ibm.com > > 512-838-1157 (T/L: 678-1157) > > > > > > _______________________________________________ > > 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 >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
David F Barrera
2005-Aug-17 16:54 UTC
Re: [Xen-devel] domU can''t start, Non-priv warnings
On Tue, 2005-08-16 at 23:14 +0100, Keir Fraser wrote:> On 16 Aug 2005, at 22:59, David F Barrera wrote: > > > I am seeing these messages on the serial console; should I be concerned > > about them. They don''t seem innocuous enough: > > They''re all innocuous, except the one in the middle which is a > grant-reference unmap request failing. Not sure what''s going on there.(XEN) (file=traps.c, line=880) Non-priv domain attempted RDMSR(00000000c0000080,00020000,00020000).Here''s a sampling from one box: (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 14a4067 for address ffffc20000019000 doesn''t match frame 14ad (XEN) (file=grant_table.c, line=1086) Grant unref rd(1) ld(0) frm(14a4) 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) Ouch! We are seriously BEHIND schedule! -107643964 (XEN) Ouch! We are seriously BEHIND schedule! -8145102 stop_this_cpu disable_local_APIC (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 10475067 for address ffffc20000019000 doesn''t match frame 1047e (XEN) (file=grant_table.c, line=1086) Grant unref rd(2) ld(0) frm(10475) 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).>From another box:(XEN) (file=traps.c, line=880) Non-priv domain attempted RDMSR (00000000c0000080,00008000,00008000). (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 device vif1.0 left promiscuous mode xen-br0: port 3(vif1.0) entering disabled state xen-br0: port 3(vif1.0) entering disabled state (XEN) (file=mm.c, line=2467) PTE entry 3b31067 for address ffffc20000369000 doesn''t match frame 3b3b (XEN) (file=grant_table.c, line=1086) Grant unref rd(1) ld(0) frm(3b31) flgs(0). device vif2.0 entered promiscuous mode xen-br0: port 3(vif2.0) entering learning state xen-br0: topology change detected, propagating xen-br0: port 3(vif2.0) entering forwarding state (XEN) (file=traps.c, line=880) Non-priv domain attempted RDMSR (00000000c0000080,00008000,00008000). (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) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 00000000 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 000000c0 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 0000009f (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 00000000 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 000000c0 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 0000009f (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 00000000 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 000000c0 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 0000009f (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 00000000 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 000000c0 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 0000009f Welcome to SUSE LINUX Enterprise Server 9 (x86_64) - Kernel 2.6.12-xen0 (ttyS0). bl2-2 login: ---- Yet another one: (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) (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) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 00000000 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 000000c0 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 0000009f (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 00000000 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 000000c0 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 0000009f (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 00000000 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 000000c0 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 0000009f (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 00000000 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 000000c0 (XEN) DOM2: (file=mm.c, line=461) Non-privileged attempt to map I/O space 0000009f Welcome to SUSE LINUX Enterprise Server 9 (x86_64) - Kernel 2.6.12-xen0 (ttyS0). bl2-1 login:> > -- Keir > >-- 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@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, 2005-08-17 at 06:59 -0500, Jerone Young wrote:> On 8/17/05, Petersson, Mats <mats.petersson@amd.com> wrote: > > > > > > > -----Original Message----- > > > From: xen-devel-bounces@lists.xensource.com > > > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of > > > Jerone Young > > > Sent: 16 August 2005 20:33 > > > To: Andrew Theurer > > > Cc: xen-devel@lists.xensource.com > > > Subject: Re: [Xen-devel] domU can''t start, Non-priv warnings > > > > > > 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? > > > > > > Checking it out...looks like Xen is pretty screwed on Opteron > > > machines at the moment (at least on my dual Opteron > > > workstation). There seems to be some timer issue...takes > > > forever fro the machine to boot up. > > > > > > Oh..AMD does not have an option for the NX bit...the cpu > > > always can understand it. > > > > That is incorrect. AMD''s 64-bit processors use NXE, bit 11, in EFER (MSR > > 0xC0000080) to determine if NX is "in use" or not. > > You apparently miss understand this. Intel CPUs have an option in the > bios where if bit 11 is set it has no idea what to do with it. Where > as on AMD 64-bit CPUs if bit 11 is set then it always does. My big > complaint is why Intel made this possible in the first place.Wow I just read this ...don''t write emails really early in the morning :-) Ok the problem is that in Xen x86-64 the NX bit is set on memory pages and your Intel EM64T CPU cannot understand this....xen go boom! So there is an option in the bios for Intel EM64T CPUs that is called "disable execute bit" (at least on IBM machines). This name is a bit misleading...it enables the NX feature on the CPU (does not activate it). So what this option does is allow the activation of NX bit enforcement on the CPU as well as allow the CPU to understand the NX bit set on memory pages. Where as on AMD K8 CPUs always have the ability to have the NX bit feature there used and understands the bit set on memory pages. Much better..> > > However, I''m not aware of any way to disable the ability to set this bit > > in the MSR, if that''s what you mean by "AMD does not have an option for > > the NX bit". > > > > -- > > Mats > > > > > > > > -Andrew > > > > > > > > _______________________________________________ > > > > Xen-devel mailing list > > > > Xen-devel@lists.xensource.com > > > > http://lists.xensource.com/xen-devel > > > > > > > -- > > > Jerone Young > > > IBM Linux Technology Center > > > jyoung5@us.ibm.com > > > 512-838-1157 (T/L: 678-1157) > > > > > > > > > _______________________________________________ > > > 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 > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >-- Jerone Young IBM Linux Technology Center jyoung5@us.ibm.com 512-838-1157 (T/L: 678-1157) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Pratt wrote:> 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 fbdbe4fc218de40d5176e0104908e05fb6e2c6ce 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_l1_entry_update __set_fixmap acpi_find_rsdp acpi_table_init acpi_boot_table_init setup_arch level3_kernel_pgt init_task start_kernel (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 Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Do you not get a couple of lines from Xen imediately preceeding the crash? Might be worth a debug=y build. Ian> > 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 > fbdbe4fc218de40d5176e0104908e05fb6e2c6ce > > 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_l1_entry_update > __set_fixmap > acpi_find_rsdp > acpi_table_init > acpi_boot_table_init > setup_arch > level3_kernel_pgt > init_task > start_kernel > > (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 Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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. -Andrew> > Ian > >>> 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 >> fbdbe4fc218de40d5176e0104908e05fb6e2c6ce >> >> 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_l1_entry_update >> __set_fixmap >> acpi_find_rsdp >> acpi_table_init >> acpi_boot_table_init >> setup_arch >> level3_kernel_pgt >> init_task >> start_kernel >> >> (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 Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
* Andrew Theurer (habanero@us.ibm.com) wrote:> 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.Yes, I tried that a long while back. There''s some mismatch in the CFI macros (ISTR it was actually head.S). Should be trivial to fixup. thanks, -chris _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel