My Fedora 17 3.3-rc4.git1 kernel boots on bare metal, but it dies very
early on in the boot process when loading on top of Xen. It's got
CONFIG_XEN_DOM0=y and all the other CONFIG_XEN* options are either "y"
or "m". Linux panics with

init[1] trap invalid opcode ip:7f99a072ff15 sp:7fffbf2a5088 error :0
in libc-2.15.so[7f99a05f8000+1ac000]
init used greatest stack depth: 2392 bytes left
Kernel panic - not syncing: Attempted to kill init!

The kernel itself seems able to execute on top of Xen because I see a
very normal-looking Xen init, then the screen blanks, then Linux
initializes and starts executing early boot, stuff like the USB stack
and SATA starts to come up, and then it tries to run the init process
in userspace and it all comes crashing down.

This is on Sandy Bridge hardware with all the CPU optional instruction
sets enabled.

Any ideas?


xen mailing list

Reply via email to