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(a)redhat.com 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...
/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.