This is an archived copy of the Xen.org mailing list, which we have
preserved to ensure that existing links to archives are not broken.
The live archive, which contains the latest emails, can be found at
http://lists.xen.org/
Hello.
I got serial console working (still haven't figured out how to get VGA
console to work), so now I managed to capture the pv_ops dom0 kernel
crashes.
http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-1.txthttp://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-2.txt
Two logs.. they seem to be a bit different from each other.
Other one ends with "xen: disable pci device 0000:00:1f.1" and the other one
has "Disabling IRQ #12" in addition to that..
After the crash hitting ctrl-alt-del seems to reboot the box, so it's not
totally dead.
Hardware is some years old Supermicro P8SCI motherboard with Intel P4 3,2 GHz
CPU
and 2 GB of RAM. I have only one IDE HDD attached to onboard ICH6 IDE
controller,
although the motherboard also has ICH6 SATA (AHCI) controller, and also some
additional Promise IDE/SATA controllers, which are currently not used at all.
Xen hypervisor (3.3.0-2 from Fedora rawhide) is 32 bit PAE. Dom0 kernel is
32 bit PAE aswell. Same kernel works just fine on baremetal without Xen.
Is there something I should try to solve the problem? Need more information?
logs when the same kernel is booted on baremetal (without Xen):
http://pasik.reaktio.net/xen/pv_ops-dom0-debug/baremetal-dmesg.txthttp://pasik.reaktio.net/xen/pv_ops-dom0-debug/baremetal-lspci.txthttp://pasik.reaktio.net/xen/pv_ops-dom0-debug/baremetal-lspci-vv.txt
-- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel