Created attachment 327842 [details] Minicom-Capture After a few days of running the xen dom0 or xen panics. There is no message on the linux console however I set up a serial trace and there's two things: During boot there is a lot of warnings and at the end come this: (XEN) Xen call trace: (XEN) [<ffff82c48014f3bd>] get_page_sid+0x7d/0xb0 (XEN) [<ffff82c48014f622>] flask_mmu_normal_update+0xc2/0x120 (XEN) [<ffff82c48017ed0f>] do_mmu_update+0x32f/0x2130 (XEN) [<ffff82c48017432d>] get_page+0x2d/0x100 (XEN) [<ffff82c48020d4a6>] do_iret+0xb6/0x1a0 (XEN) [<ffff82c480208c08>] syscall_enter+0x88/0x8d (XEN) (XEN) (XEN) **************************************** (XEN) Panic on CPU 4: (XEN) GENERAL PROTECTION FAULT (XEN) [error_code=0000] (XEN) **************************************** (XEN) (XEN) Reboot in five seconds... Don't be confused that the boot messages with warnings are after the panic I forgot to turn on logging when i started minicom. The panicing can be provoked by using much memory so the box gets into swapping.
xen support in kernels has come a long way since October 2012 and the new kernel-3 versions long since suprseded
