I have been trying to install OVM Server on an IBM xSeries 336 server. OVM Server 2.2.1 was previously installed on this server.
Trying to install 3.2.1 now and I get to the splash screen booting from the CD. I press [Enter] to begin the installation. Once the process reaches the point of 'Loading SCSI driver', the server reboots. I have tested the media on other machines without issue. I have also tested the server with OVM Server 2.2.1 media and the install progresses normally to the end.
I suspect there are missing drivers causing the install to fail. Is there a way to load the missing drivers during the install process?
Thanks in advance,
UPDATE: I have successfully installed OVM Server 3.0.2... Not exactly what I wanted but....
If you are installing Oracle VM Server on a Sun Fire X4800, you must provide extra parameters when
booting from the installation media (CDROM or ISO file), or when using a kickstart installation. These
parameters allow the megaraid_sas driver to load correctly.
If booting from the installation media, press F2 when the initial boot screen is displayed and provide the
following additional parameters as part of the boot command:
mboot.c32 xen.gz extra_guest_irqs=64,2048 nr_irqs=2048 --- vmlinuz --- initrd.img
If using a kickstart installation, add the additional kernel parameters to the PXE configuration file.
No tape drives.
Curiously, while installing 3.0.2, I noted that the following scsi drivers were loaded... shpchp driver, mptbase driver, mptspi driver, ata_piix driver, qla2xxx driver.
During the install of 3.1.1 and 3.2.1, only the following scsi drivers are loaded before rebooting... sg driver and usb storage driver (no usb storage on server).
As was mentioned before, 3.x is entirely different than 2.x.
It's worth noting the only happy OVM customers I've heard of (and we've looked far and wide to find them) are running Oracle servers on Oracle storage to host Oracle applications. Everybody else (including us; we have an EMC storage array) run in to problems that take forever to resolve, if they're ever resolved.
I would be wary of running that setup in production.