This content has been marked as final. Show 6 replies
Add noreboot at the end of these two lines in /etc/grub.conf
kernel /xen.gz console=ttyS0,57600n8 console=ttyand you should get a better idea of what the problem is.
kernel /xen.gz console=ttyS0,57600n8 console=tty
Note that you will have to manually reboot the machine so don't do this on a machine if you don't have physical access!
It seems a hypervisor problem. but others cannot help unless you can provide further information.
The default 2.1 grub configuration has some problem for getting the hypervisor boot log. try creating a grub boot iterm:
title xen serial console
kernel /xen.gz com1=115200,8n1 console=com1,vga dom0_mem=512M
module /vmlinuz-2.6.18-184.108.40.206.18.el5xen ro root=LABEL=/1 console=tty0 console=ttyS0,115200n8
then boot with this item and connect a serial line to the server and capture the log in another host.
For detailed information, refer to Debugging Xen with Serial Console: http://os-drive.com/en/node/33
You may get some info if you prevent xen from rebooting when panic.
Follow these steps to get that:
There are two places to consider:
For xen hypervisor: appended "noreboot" to xen's command line.
For linux dom0: append "panic=0" to linux's comand line,
Then the grub boot item looks like:
title xen serial console
kernel /xen.gz com1=115200,8n1 console=com1,vga dom0_mem=512M noreboot
module /vmlinuz-2.6.18-220.127.116.11.18.el5xen ro root=LABEL=/1 console=tty0 console=ttyS0,115200n8 panic=0
refer to: http://os-drive.com/files/docbook/xen-faq.html#prevent_reboot
Thank-you Zhigang and D.im
i did try your (D.im) advice but it still rebooting. and i do not have a serial cable to trying Zhigang advice.
I think this is a hardware conflict with the xen.
this is a new HP Compaq dc7800p Convertible minitower with Intel vPro
Intel Core Duo CPU 3.0GHz and 4 Gb DDR2/800 RAM and it supports Vertualization Technology.
I've installed Oracle VM to a 2 or 3 year old computer and never have this reboot before.
Thanks for your helps!
Check if you see this just before your laptop reboots
Kernel panic - not syncing: cannot execute a PAE-enabled kernel on a PAE-less CPU!
It's described in metalink note 468994.1
In short it says that Oracle VM Server is NOT supported on CPUs without Physical Address Extension (PAE) feature.
I am also encountering the same error. One of my nodes on VMWare dies after surviving 10-15 seconds. First time node was rebooted automatically during installation of Oracle clusterware and once node was up but it was died again before I check any system logs. When I restart it and it dies in seconds.
Does anyone have any idea about this? Can I get any logs without my node is up?