I am having similar issues. I have tracked it down to the UEFI that the
newer IBM servers have. I was able to install sles11 sp1 but as soon as
I try to boot to the xen kernal it gets caught in a boot loop.[/color]
Dear engineers,
I have a look a like problem, installed SLES11 installed my raid
drivers and then installed the Xen Hypervisor tools. Did a reboot tried
to boot the Xen Kernel but no luck. Tried also SLES10 same problem,
changed out harddrives also no luck with the same problem.
I am having similar issues. I have tracked it down to the UEFI that the
newer IBM servers have. I was able to install sles11 sp1 but as soon as
I try to boot to the xen kernal it gets caught in a boot loop.[/color]
Dear engineers,
I have a look a like problem, installed SLES11 installed my raid
drivers and then installed the Xen Hypervisor tools. Did a reboot tried
to boot the Xen Kernel but no luck. Tried also SLES10 same problem,
changed out harddrives also no luck with the same problem.
Who has a hint to solve this?
[/color]
You said you installed the drivers for your raid. I assume that you have a
raid that is not supported in the kernel. If that is the case you actually
have to recompile the xen kernel with the drivers. I personally try to stick
with kernel supported drivers to save the hassle when do kernel updates
which always than break the kernel with 3rd party drivers.
You said you installed the drivers for your raid. I assume that you
have a
raid that is not supported in the kernel. If that is the case you
actually
have to recompile the xen kernel with the drivers. I personally try to
stick
with kernel supported drivers to save the hassle when do kernel
updates
which always than break the kernel with 3rd party drivers.
If I misunderstood the issue I apologize.[/color]
Hey thanks for the reply, that’s a good one sound logical. I’m going to
try out uninstall the raid and reinstall the XEN and see what it does.
I’m not quit a Linux guru, still learning so compiling drivers is not
yet one of the things that I master:-)
Hey, I have the same problem due to UEFI technology (I don’t have RAID issues).
There is a IBM doc that says to go to BIOS and select LEGACY ONLY boot device option
But what happens is that right after UEFI finds the XEN boot it reboots the server
My case is :
SLES11SP1 + XEN
IBM3400M3 with UEFI embedded tech
If you install the XEN kernel, everytime that the server finds the boot, it reboots the server
If you set LEGACY ONLY on BIOS, it tries to find the boot on the disk (and there is none or it is not pointed to), so it finds no boot, because the boot is not on the disk, but on UEFI
I am trying to install without that VFAT partition , forcing the boot to the disks on regular partitions , that belongs to that LEGACY ONLY BIOS option.
I will be reporting soon.
I did it. I installed the server IBM with UEFI with XEN.
But I “disabled” UEFI.
I followed a document on this forum that teaches to bypass UEFI and boot the server as “old times” finding the boot on a disk.
It will be necessary to know how to handle UEFI, but for this moment that I needed a server very fast, it is done.
Follow this :
=================================================================
Basically you need to go into the firmware at boot time:
F1 → Boot Manager → Add Boot Option → choose '“Legacy Only”
Then go back to the Boot Manager menu, and choose “Change Boot Order”.
Ensure that Legacy is on the top of the list.
Followed by “CD/DVD” followed by “Hard Disk 0” - and maybe “PXE
Network”.
You should remove all extraneous entries by returning to the Boot
Manager menu and choosing “Delete Boot Option”. (you will see an entry
entitled Suse Linux Enterprise Server 11.1: remove that too).
Basically it forces the boot into legacy BIOS mode, the DVD boots as an
legacy DVD, and installs as normal - and installs a visible GRUB boot
loader as we are accustomed to.
