I currently have several HP blades running Xen 3.1 on Suse 10.3 and they work fine.
I now have 2 new servers of a different brand and not blades. Both the new servers and old blades are all Intel dual quad-core 64bit servers. They are all running the same version of Suse 10.3 64bit, and the same version of Xen 3.1 (from zypper/yast). For some reason the new servers hang on boot when I try to boot the Xen kernel. The grub menu goes away after selecting Xen, then the menu.lst info is printed to the screen. Below that I get a blinking cursor. It sits like this until I hard reboot:
###################
root (hd0,0) Filesystem type is ext2fs, partition type is 0x83 kernel /xen.gz [Multiboot-elf, <0x1000000 :0xbd5c0>, shtab=0x20f078, entry=0x1000000] module /vmlinuz-2.6.22.17-0.1-xen root=/dev/vg00/dom0_root vga=0x314 resume=/dev/vg00/dom0_swap splash=silent showopts
[Multiboot-module @ 0x210000, 0x7342b8 bytes] module /initrd-2.6.22.17-0.1-xen [Multiboot-module @ 0x945000, 0x76d200 bytes]
_
###################
About the servers with the problem:
Dual Xeon 5420 2.5GHz (Intel VT is enabled) SuperMicro MBD-X7DBR-I +Motherboard - Intel 5000P (Blackford) Chipset 32GB DDR2
There are two hardware RAID-1's
RAID-1 2x500GB ext3 /boot 128MB 0x8E Linux LVM 499.9GB for vg00 LVM vg00/dom0_root ext3 8GB LVM vg00/dom0_swap 2GB
RAID-1 2x500GB 0x8E Linux LVM 500GB for vg01 LVM vg01 <unused at the moment>
I have tried both the Intel and Adaptec RAID controller codebase. I have tried turning off Intel VT. Both had no effect.
Suse works without issue until I try to boot the Xen kernel, then it hangs with what is posted above. Any idea what this could possibly be?
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|