Hi Mark, I ran the adjusted commands on our system here with the Intel CPU (which crashes in the same way as Jon's machine): [root@office64 boot]# /usr/lib64/xen/bin/xenctx -s System.map-2.6.27.9-159.fc10.x86_64 114 rip: ffffffff8100b8a2 set_page_prot+0x6d rsp: ffffffff81575f08 rax: ffffffea rbx: 000016e4 rcx: 00000055 rdx: 00000000 rsi: 800000010c2b3061 rdi: ffffffff816e4000 rbp: ffffffff81575f68 r8: 0000000f r9: ffffffff817ee350 r10: ffffffff817ee550 r11: 00000010 r12: ffffffff816e4000 r13: 800000010c2b3061 r14: 8000000000000161 r15: 00002c00 cs: 0000e033 ds: 00000000 fs: 00000000 gs: 00000000 Stack: 0000000000000055 0000000000000010 ffffffff8100b8a2 000000010000e030 0000000000010082 ffffffff81575f48 000000000000e02b ffffffff8100b89e 0000000000000200 ffffffff816e7000 0000000000000800 0000000000000016 ffffffff81575ff8 ffffffff815a5c60 0000000000002c00 0000000000000000 Code: df 54 1d 00 4c 89 e7 4c 89 ee 31 d2 e8 22 d9 ff ff 85 c0 74 04 <0f> 0b eb fe 5b 41 5c 41 5d 41 5e Call Trace: [<ffffffff8100b8a2>] set_page_prot+0x6d <-- [<ffffffff8100b8a2>] set_page_prot+0x6d [<ffffffff8100b89e>] set_page_prot+0x69 [<ffffffff815a5c60>] xen_start_kernel+0x5dd Cheers hope this helps Phill On Fri, 2009-01-16 at 10:33 +0000, Mark McLoughlin wrote: > Hi Jon, > > On Fri, 2009-01-16 at 18:02 +0900, Jon Swanson wrote: > > This is a cross post of the same subject on the Fedora Forums. If this > > is bad practice let me know and i'll never do it again. > > Mailing lists can often be a better way to get help from developers, so > posting here is no problem. > > Also, fedora-virt@xxxxxxxxxx might be a better place to post questions > these days - it's not clear whether the fedora-xen list has a future. > > > Additional log info is available at > > http://forums.fedoraforum.org/showthread.php?p=1149972&posted=1#post1149 > > 972 > > > > I have two machines running fresh installs of f8 with the xen. Kernel > > and all software versions are the same on both. > > You've seen this then, right? > > http://fedoraproject.org/wiki/Bugs/F10Common#Installing_Fedora_10_DomU_on_Fedora_8_Dom0_Fails > > > /var/log/xen/xend.log relevant output: > > > > [2009-01-16 14:45:32 4120] DEBUG (DevController:150) Waiting for devices > > vtpm. > > [2009-01-16 14:45:32 4120] INFO (XendDomain:1130) Domain f10testB (21) > > unpaused. > > [2009-01-16 14:45:32 4120] WARNING (XendDomainInfo:1203) Domain has > > crashed: name=f10testB id=21. > > [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1802) > > XendDomainInfo.destroy: domid=21 > > [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1821) > > XendDomainInfo.destroyDomain(21) > > I've also tried moving a functional guest from MachineA to MachineB to > > boot it there, with the same results. Guest will not boot on MachineB. > > > > f8 64bit guests will boot on MachineB with no problems. > > f10 32bit guests will boot on MachineB with no problems. > > > > Only 64bit machines seem to be borked. > > Okay, sounds like it might "just" be a F10 kernel bug. > > Try doing this to get a stack trace: > > 1) Set "on_crash=preserve" in your domain config > > 2) Copy the guest kernel's System.map to the host > > 2) Once the guest has crashed, run: > > /usr/lib/xen/bin/xenctx -s System.map <domid> > > Cheers, > Mark. > > -- > Fedora-xen mailing list > Fedora-xen@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-xen > -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
