I/O Does Not Work On Sles11 Sp1 With Xen (Cr 6965290 And Cr7110443); Rhel6 Kdump Runs Out Of Memory (Cr 7000993 And Cr 7000942) - Oracle Sun Fire X4800 Product Notes

I/O Does Not Work On SLES11 SP1 with XEN (CR 6965290
and CR7110443)
If the number of I/O devices exceeds XEN's number of interrupts, the I/O devices might not
work, and it might display corresponding error messages. For example:
Unable to allocate IRQ or map irq failed
Workaround
Add the following to the /boot/grub/menu.lst file:
extra_guest_irqs=64,2048 nr_irqs=2048
RHEL6 Kdump Runs Out of Memory (CR 7000993 and CR
7000942)
If Red Hat Linux 6 (RHEL6) calculates that the kdump size is too small, it displays a message:
"Your running kernel is using more than 70% of the amount of space you reserved
for kdump, you should consider increasing your crashkernel reservation"
One of two conditions might be present:
It might have enough memory, but post the messages anyway.
■
It might really not have enough kdump memory space. In this case, if the system crashes, it
■
might not produce a kdump file, and it might post messages similar to the following on the
console:
Out of memory: kill process 322 (insmod) score 21 or a child Killed process
322 (insmod) vsr:1352kB, anon-res: 244kB, file res: 122kB
Workaround
1. To make the messages stop and to ensure your system has enough kdump memory space,
change the following line in boot/grub/menu.lst:
Change:
crashkernel=auto
To:

I/O Does Not Work On SLES11 SP1 with XEN (CR 6965290 and CR7110443)

Linux Issues 53