VMware Cloud Community
isgsb
Contributor
Contributor

warning message "Couldn't setup IRQ ... with vector"

Hi all,

since the upgrade from ESX 3.5.0 update 1 to update 3, a new warning is shown in red color at the F11-screen after each boot:

<boottimestamp> cpu0: <number>)Host: 2534: Couldn't setup IRQ 9 with vector 153

This appears on two systems with identical hardware (only <boottimestamp> and <number> differ) Thus, I guess hardware errors can be excluded. Both systems

seem to work as usual.

Is this message something I've to be worried about? Is there any hint, what it is, and how I may solve this, anyhow?

Regards,

Robert

0 Kudos
3 Replies
Troy_Clavell
Immortal
Immortal

see this KB

http://kb.vmware.com/kb/1003812

if you found this or any other answer useful, please consider marking it as "correct" or "helpful"

0 Kudos
isgsb
Contributor
Contributor

Thank you for the hint, but this is strange my system has only 4 devices with that IRQ number:

According to that KB article, 4 is ok, but five or more isn't. When I use that command:

# cat /proc/vmware/interrupts | grep 'irq *9'

0x79: 8918259 8784881 15233197 15306276 24332610 24280208 53349318 52707949 <COS irq 9 (PCI level)>, VMK vmnic0, VMK vmnic1

0x89: 1787 0 42974 3324 36210 4592 53806 28565 <COS irq 9 (PCI level)>, VMK vmnic3

0x91: 14203 28603 265968 313158 534365 533207 1039941 1269139 <COS irq 9 (PCI level)>, VMK ioc0

0x99: 45 0 0 0 0 0 0 0 <COS irq 9 (PCI level)>, VMK ioc1

#

The warning is about IRQ 9 with vector 153.

Robert

0 Kudos
isgsb
Contributor
Contributor

Since upgraded to VMware ESX 4.1, this problem never occurs. Thus, not interested in an answer anymore.

0 Kudos